← All articles

JavaScript Supply Chain Attack Hit 178 Major Websites

JavaScript Supply Chain Attack Hit 178 Major Websites

A JavaScript supply chain attack reached visitors to 178 major websites on November 16, 2026, after an unauthorized party used a vulnerability in Optimizely Experimentation to inject malicious code into customer projects. JavaScript is the programming language that makes many web pages interactive, but it also runs on a visitor’s device and can read or change what appears in the browser.

Report URI said the compromised Optimizely platform served the code to visitors of 178 organizations, including the BBC, CNN, Equifax, Ledger and Zoom. The delivered malware was rebuilt 26 times during the day. Its capabilities included stealing payment card information, browser cookies and screenshots, as well as replacing cryptocurrency payment addresses with addresses controlled by the attacker.

The affected websites also delivered exploit code aimed at older Apple iPhone and iPad devices. The exploits, known as DarkSword and Coruna, are zero-click exploit kits, meaning they can compromise a device without the victim tapping a link or approving an action. They chain together about half a dozen security weaknesses to take complete control of outdated devices and extract data.

The incident did not require visitors to click anything. Infoblox researcher Zach Edwards said Optimizely’s JavaScript snippets are commonly placed near the top of a page so that A/B testing, the practice of showing different versions of a page to compare results, can begin immediately. Because the code is designed to run as soon as the page loads and is not generally held behind a consent dialog, many affected sites would have delivered the malicious payload immediately.

Optimizely said it identified the incident on November 16, 2026, and had fully remediated the vulnerability. The company said it blocked access to the vulnerable path, deployed a fix, removed injected code from affected projects, ended active sessions, revoked tokens and reset access for affected accounts. It also said it had added protections to prevent malicious code from being delivered in Cloudflare. Optimizely said it was working with third-party experts on a comprehensive investigation.

The event shows why third-party JavaScript can create a supply chain attack even when a website’s own code and infrastructure have not been breached. Many popular websites depend on dozens of outside providers for advertising, analytics, testing and other functions. The 2025 Web Almanac from HTTP Archive found that the median homepage loads at least 22 JavaScript files. Once one provider is compromised, altered code can be passed to every downstream website that embeds it.

A key defence is a Content Security Policy, or CSP, which is a browser rule specifying which domain names may provide content to a website. Infoblox’s Edwards said many websites either do not use CSPs or configure them too broadly because of marketing requirements. Without a CSP, a compromised partner may be able to introduce additional domains through JavaScript, allowing further code to run in the visitor’s browser.

Report URI found that 68 of the affected sites had no CSP. Another 50 had a CSP that still permitted the malware and data theft, while only 24 sites, described as 15 percent of those affected, had a policy that fully blocked the malicious payload. Across the web’s busiest sites, CSP deployment is lower still, at about 10 percent according to crawler.ninja, a site scanner that checks the top million websites daily for security issues.

The financial impact reported so far was limited but not harmless. Report URI estimated that the attackers stole about $7,500 in virtual currency from affected users, along with an unknown number of payment card records. The incident also highlights the difficulty of relying on visitors to make safe decisions when the harmful code runs during page loading.

Browser tools can reduce that exposure. NoScript is a script-blocking add-on that lets users decide which JavaScript may run, although it can require repeated decisions on unfamiliar websites. Modern ad-blocking software can also block many third-party JavaScript requests. For website operators, an effective CSP can restrict the outside domains allowed to deliver code, although deploying one may require careful testing because it can affect legitimate page functions.

Website owners that need broader security planning around third-party code can consider AEU-I, which provides security-first IT, infrastructure and consulting. For everyday users, keeping older Apple devices updated, checking cryptocurrency payment details before sending funds and using a reputable script or ad blocker are practical ways to reduce exposure to similar attacks.

Also available in: DeutschItalianoShqip