There are lessons to be learned from government websites serving cryptocurrency miners

Posted by   Martijn Grooten on   Feb 12, 2018

This was awkward. On Sunday, the Information Commissioner's Office (ICO), the UK's data protection regulator and thus the public body that issues fines for data breaches, was found to be serving a JavaScript-based cryptocurrency miner on its website.

The issue was first reported by security researcher Scott Helme, who discovered that the ICO wasn't the only organisation affected: thousands of sites, including many government sites in a number of countries, were serving the same JavaScript code. The source of the issue was quickly determined to be a piece of third-party code used to improve a website's accessibility for the visually impaired.

The technique used wasn't particularly advanced: some mildly obfuscated code had been added that loaded the miner from Coinhive, a site used in many such attacks. In fact, the same Coinhive account had been used against some other websites a few days earlier. TextHelp, the company that was serving the code, took the affected web server offline after about four hours.

icocoinminer.png

The current value of most cryptocurrencies makes this an attractive way for cybercriminals to make money, but as attacks go, it is barely more harmful than inserting a silly YouTube video into the web page. But while we consider all the other things that could have happened (such as form data being stolen, or an exploit kit being served) it is worth noting that there are important lessons to be learned from this hack.

The first is that there are actually ways in which content can be loaded from third-party sites that significantly reduce the harm. In particular, by setting the Content Security Policy (CSP) header, a site can inform a browser that only content from specific domains is allowed to be included. Using Subresource Integrity (SRI) can even allow only JavaScript code with a specific cryptographic hash to be included, though that is probably most useful in cases where the third-party site is controlled by the same organisation.

The second lesson is that a company like TextHelp can make it easy for researchers to find a security contact to report issues like these. This is where the recently introduced security.txt standard becomes very useful: it is a simple text file hosted at a predictable location on a website, where the site owner can put their security contacts, as well as various security policies. Both Facebook and Google have adopted the standard, but it is probably most useful for smaller companies and organisations that don't have a large and visible security team.

This morning, Virus Bulletin added a security.txt file to its website.

twitter.png
fb.png
linkedin.png
hackernews.png
reddit.png

 

Latest posts:

VB2021 call for papers - now open, to all!

The call for papers for VB2021 is now open and we want to hear from you - we're planning for flexible presentation formats, so everyone is encouraged to submit, regardless of whether or not you know at this stage whether you'll be able to travel to…

In memoriam: Yonathan Klijnsma

We were very sorry to learn of the passing of researcher Yonathan Klijnsma last week. Here, former VB Editor Martijn Grooten shares his memories of a talented researcher and a very kind person: this month, infosec lost a really good one.

VB2020 localhost videos available on YouTube

VB has made all VB2020 localhost presentations available on the VB YouTube channel, so you can now watch - and share - any part of the conference freely and without registration.

VB2020 presentation & paper: 2030: backcasting the potential rise and fall of cyber threat intelligence

At VB2020 localhost, threat intelligence consultant Jamie Collier used the analytical technique of backcasting to look at the rise and fall of the cyber threat intelligence industry.

VB2020 presentation: Behind the Black Mirror: simulating attacks with mock C2 servers

At VB2020 localhost, Carbon Black's Scott Knight presented an approach he and his colleagues have taken to more realistically simulate malware attacks.

We have placed cookies on your device in order to improve the functionality of this site, as outlined in our cookies policy. However, you may delete and block all cookies from this site and your use of the site will be unaffected. By continuing to browse this site, you are agreeing to Virus Bulletin's use of data as outlined in our privacy policy.