720-891-1663

Is Your Web Site Using Third Party Javascript?

Trying to figure out a catchy title here. Not sure I did that, but maybe since you are reading this, it worked.

Here is the problem. When you, as a web site developer/operator, load code from a third party repository, you are trusting that code. That might not be a great idea.

This week a backend service for presenting different versions of a web site for different users, often called A/B testing, was compromised. The result was those websites that use the service, called Optimizely, were compromised and when developers from places like CNN and Zoom, among more than 150 other sites, got a user to visit their website, they infected that visitor with malware.

Tags like CSP and SRI help with this, but only in a limited way. If you are a developer and want to understand the problem better, check out the links below.

This turned into a ZERO-CLICK attack as the Javascript was loaded and ran when the page was loaded.

While this particular instantiation of the attack happened this week, apparently it has been being quietly tested for a while on other unsuspecting web sites.

Since the code is dynamic and located at a third party, no testing that you can do would detect it.

There is a paid service that can help detect these anomalies, but, of course, you have to pay for it, set it up, and, more importantly. monitor it in real time to be useful.

Here are some of the sites that were infected. You can find a more complete list here.

  • HSBC, Paychex, Equifax, Zoom, Bitly, Salesforce
  • IKEA, Mattel, American Eagle, Peacock, CNN
  • BBC, Fox News, NPR, Alaska Airlines, Air France-KLM
  • Mutual of Omaha, ASPCA,
  • And many, many others

While it was detected relatively quickly and fixed soon after, it is unclear what the plan is to deal with the potentially millions of users whose credit cards were stolen, who were tricked into installing malware or whose crypto wallets were drained.

It also may be difficult to trace it back to which website you visited that caused the malware to be downloaded and your data stolen. I assume the class actions, at least in this case, will be against the third party, which is hard by itself.

Credit cards are easy to fix. Debit cards a bit harder and crypto, well, to be impolite, you are pretty much screwed.

Credit: Brian Krebs, Scott Helme and Report URI

Facebooktwitterredditlinkedinmailby feather

Leave a Reply

Your email address will not be published. Required fields are marked *