Malware News CNN, BBC, Zoom, and other sites served malicious code in supply-chain attack

Brownie2019

Level 23
Verified
Well-known
Forum Veteran
Visiting a familiar website should not mean exposing your payment details to criminals. But attackers found a way to put malicious code on websites belonging to some of the world’s best-known organizations by compromising a service those sites trusted.

On November 16, security researcher Scott Helme and his team at Report URI identified malicious JavaScript in Optimizely files associated with 178 organizations, including the BBC, CNN, Zoom, Salesforce, and GitLab. The code could redirect cryptocurrency payments, skim payment card details, and deliver exploit kits targeting vulnerable iPhones and iPads. Check Report URI’s full list to see which websites were affected.

Optimizely provides software that helps businesses test and personalize their websites. To accomplish this, a website adds a small piece of JavaScript called a snippet. This loads Optimizely’s code into visitors’ browsers, where it can change their experience and measure the results. In this incident, it also provided a way for unauthorized changes to reach visitors through an otherwise legitimate website.

Optimizely is widely used. Website technology tracker BuiltWith currently reports detecting it on roughly 190,000 live websites. That is its overall usage, not the number affected by this incident. This qualifies as a supply-chain attack because, instead of breaking into every website separately, criminals abused a shared service those websites relied on.

The BBC provides a prominent example of how the attack unfolded. Report URI’s timeline records a clean capture of its Optimizely snippet at 02:21 UTC on November 16, followed by an injected version at 04:21 UTC. By 08:28 UTC, the researchers observed the main malicious payload being loaded on bbc.com.

This does not establish that the BBC’s own servers were breached, or that every BBC visitor was infected. It shows how a third-party script used by a trusted website can become the route through which malicious code reaches a visitor’s browser.

Optimizely confirmed the incident and says it fixed the vulnerability and removed the injected code from affected projects. Report URI also said all the infected Optimizely files it was monitoring were clean by 23:11 UTC on November 16 and had remained clean since.

How to stay safe​

Visitors cannot reasonably be expected to inspect every script a website loads, and disabling JavaScript can make many websites unusable. The most useful steps are to keep devices updated and check any potentially affected transactions.

  • Update your iPhone or iPad. Install the latest iOS or iPadOS version available for your device. This is particularly important if you visited an affected website on November 16, because the attack included exploit delivery aimed at older, vulnerable versions.
  • Use an up-to-date real-time anti-malware solution. This can help detect and block malware on your devices.
  • Review cryptocurrency transfers made during the incident. Check the actual destination address against the intended recipient’s address, confirming it directly with the recipient through a trusted channel. The attack was specifically designed to change payment destinations.
  • Check payment card activity. If you entered card details on an affected page on November 16, monitor your account and contact your card issuer promptly about suspicious transactions. Enable transaction alerts where available. You could also consider identity theft protection with credit monitoring to help spot signs of identity misuse, such as new credit accounts opened in your name.
  • Watch for unusual account activity. Investigate unexpected account changes or unfamiliar sessions, particularly for services you were using on affected pages. The code could steal some cookies, which can contain information used to keep you signed in.
The main responsibility rests with the organizations delivering code to visitors. The incident shows why website operators also need to monitor what third-party scripts do and restrict the other scripts and data connections they can introduce. Consumers shouldn’t have to audit a website’s software supply chain before reading the news or making a purchase.
 
Hi Brownie2019, this is a genuine and unusually broad supply-chain compromise. The distinction in the post is important: an organization appearing on the list means malicious code was found in an associated Optimizely snippet—not that its own servers were necessarily breached or that every visitor was compromised.

A couple of useful clarifications:

  • 178 organizations and 188 infected snippets are not conflicting figures. Some organizations had more than one affected project/snippet.
  • The payload changed during November 16. According to Report URI’s timeline, the cryptocurrency clipper appeared before the card skimmer, which was added at 13:43 UTC. Therefore, not every visitor was exposed to every capability.
  • The cryptocurrency theft was not merely hypothetical: Report URI identified roughly $7,040 in receipts to attacker wallets by 19:25 UTC. Conversely, it could not determine how many cards or cookies were stolen or how many iOS devices were successfully compromised.
  • Cookie theft was limited to cookies accessible through document.cookie; cookies marked HttpOnly cannot be read that way. That reduces—but does not eliminate—the session-theft risk.

At the time of writing, Optimizely’s incident remains in “Monitoring”, although the company says the vulnerability was fixed, injected code removed and affected accounts secured. Report URI says all infected snippets it was tracking were clean by 23:11 UTC on November 16. That suggests the active delivery was contained, but it is not the same as a completed forensic investigation or postmortem.

Sensible response for visitors​


There is no need for everyone who read a BBC or CNN page to reinstall their device. Response should match the exposure:

  • Only visited an affected page on an updated desktop: keep the browser and operating system updated and run the normal security scan. A clean scan is useful, but it is not a time machine and cannot rule out data exposed inside the browser.
  • Entered card details: enable transaction alerts, review activity and contact the issuer promptly if anything is questionable. Paid identity monitoring is secondary; it neither prevents card fraud nor substitutes for speaking to the issuer.
  • Made a cryptocurrency transfer: verify the destination address against a trusted copy or directly with the recipient. Do not rely on the address still present in browser history or the clipboard.
  • Saw unfamiliar account sessions or changes: revoke existing sessions, sign back in, change the password if appropriate and ensure MFA and recovery details remain correct.
  • Used an outdated iPhone or iPad: install the newest version offered for that device. Apple currently lists iOS/iPadOS 27.2.1 as the latest mainstream release, while older hardware may receive another supported branch. Conventional iOS “antivirus” apps cannot perform a full system scan because of Apple’s sandboxing.

For site operators, merely trusting cdn.optimizely.com was plainly insufficient. A carefully enforced Content Security Policy restricting secondary scripts, connections and frames could have blocked parts of the chain, while integrity/change monitoring could have exposed the modified project code. “Trusted third party” is an administrative relationship, not a cryptographic guarantee—this incident demonstrated that rather efficiently.

Sources
 

MalwareTips community

Join the discussion

Create a free account to reply to this thread, ask your own questions and get help from the community.

  • Reply and ask questions
  • Get alerts when someone answers
  • Free malware removal help

Join 75,660 members who help each other for free, since 2010.

Create free account
or continue with

Recently browsing

Members and guests who viewed this thread in the last 5 minutes

Back
Top