Optimizely hack infected CNN, Fox News, BBC, Salesforce sites with malware
A software supply-chain attack targets a tool or provider used by other organizations, then reaches those organizations through their reliance on that service. It matters because one compromise can affect many websites and their visitors, rather than only the provider itself. In this case, Optimizely’s JavaScript files are added to customer webpages to support website testing and personalization. Attackers exploited a vulnerability in the Experimentation account signup flow to add malicious JavaScript to some customer projects. Websites loading those modified files could then load a further malicious script. Optimizely said it blocked access to the vulnerable path, fixed it, and removed injected code from affected projects. It also ended active sessions, revoked tokens, reset access for affected accounts, and blocked code delivery through Cloudflare. The company said it was continuing to investigate and had notified affected customers.
What is a software supply-chain attack, and how did this one spread through Optimizely?
A software supply-chain attack targets a tool or provider used by other organizations, then reaches those organizations through their reliance on that service. It matters because one compromise can affect many websites and their visitors, rather than only the provider itself.
In this case, Optimizely’s JavaScript files are added to customer webpages to support website testing and personalization. Attackers exploited a vulnerability in the Experimentation account signup flow to add malicious JavaScript to some customer projects. Websites loading those modified files could then load a further malicious script.
Optimizely said it blocked access to the vulnerable path, fixed it, and removed injected code from affected projects. It also ended active sessions, revoked tokens, reset access for affected accounts, and blocked code delivery through Cloudflare. The company said it was continuing to investigate and had notified affected customers.
How widespread was the attack, based on the number of infected scripts, organizations, and affected websites?
The reported figures show a broad incident: security researcher Scott Helme identified 188 infected Optimizely JavaScript files belonging to 178 organizations. His team reached that finding after analyzing 1,611 scripts used by the platform. These figures count scripts and organizations, not individual visitors or every affected webpage.
BleepingComputer separately confirmed that the malicious script loaded or attempted to load on many sites. Named examples include Zoom, KLM, GitLab, BBC, CNN, Scheels, Smartsheet, Stamps.com, and Salesforce. Other affected sites included Fox News, Air France, Change.org, HSBC Insurance, and UNICEF USA.
The article does not state a complete count of affected websites or visitors. Helme later reported that cleanup had reduced the number of infected files: as of 21:52 UTC on November 16, only one of the 188 previously compromised files still contained malicious code. The number of people exposed remains unclear.
What could the injected malware do to visitors’ cryptocurrency, payment-card details, and devices?
The injected JavaScript was designed to steal information and redirect cryptocurrency transfers. Its capabilities matter because the code could run when visitors opened affected webpages, exposing data entered or displayed there to attackers.
The additional script, called track.js, searched pages for cryptocurrency wallet addresses and replaced them with attacker-controlled addresses. It also sought credit-card numbers, expiration dates, and security codes, then attempted to send captured details to the attackers. The script could collect browser cookies, webpage URLs, and screenshots as well. It loaded further JavaScript targeting iPhones and iPads; Helme identified the Coruna and DarkSword exploit kits, which target different iOS versions.
These were documented capabilities, not proof that every visitor was compromised. Helme found that wallets embedded in track.js had received approximately $7,000 in transactions by November 16, but some wallets were active before the attack. That makes the amount stolen during this campaign difficult to determine.
How did a flaw in Optimizely’s account signup flow let attackers add malicious code to customer projects?
Optimizely confirmed that the entry point was a vulnerability in its Experimentation account signup flow. Attackers used that weakness to add malicious JavaScript to some customer projects. The incident mattered because those projects supplied scripts that customers’ websites used, allowing the injected code to reach visitors.
The article does not describe the flaw’s underlying technical cause, the exact steps attackers took, or what signup checks were bypassed. It does establish the outcome: unauthorized code was added to customer projects, and modified Optimizely JavaScript files loaded or attempted to load additional malware on affected sites.
Optimizely said it blocked access to the vulnerable path and deployed a fix. It also removed injected code, ended active sessions, revoked tokens, reset access for affected user accounts, and blocked code delivery through Cloudflare. The company said it was continuing to investigate and would publish relevant updates, but the article gives no further technical explanation of the vulnerability.
Why do organizations use Optimizely, and why does that mean its JavaScript can appear on many different websites?
Optimizely is a digital experience and experimentation platform. Organizations use it to test and personalize their websites. This can mean that a shared provider’s scripts appear across many customer sites, making the provider an important link between the platform and the websites that use it.
The article explains that Optimizely JavaScript files are loaded into customers’ webpages to deliver the platform’s functionality. In the attack, code injected into some customer projects was therefore present in modified scripts used by those websites. BleepingComputer confirmed loading attempts across sites including Zoom, CNN, BBC, Salesforce, GitLab, and others.
That shared use helps explain why the incident reached organizations in different sectors and countries. The article reports 188 infected scripts belonging to 178 organizations, but does not give a full count of affected websites. Optimizely said it removed injected code and blocked delivery through Cloudflare, while notifying affected customers and continuing its investigation.
What steps did Optimizely and affected site operators take to stop the malicious code, and what should exposed visitors check?
Optimizely said it blocked the vulnerable signup path, deployed a fix, and removed malicious code from affected customer projects. It also ended active sessions, revoked tokens, reset access for affected user accounts, and blocked code from being delivered through Cloudflare. These steps aimed to stop further access and prevent the injected scripts from reaching websites.
Affected site operators also responded. Salesforce said it was investigating malicious modifications to Optimizely scripts used on some of its websites. As a precaution, it confirmed that Optimizely scripts were disabled across preview and production instances. It said it would notify affected customers without undue delay if it identified unauthorized access to their data.
Visitors who accessed affected websites on November 16 should review cryptocurrency transfers made during that time and check their destinations. The article does not say how many visitors were exposed or how long the signup-flow vulnerability existed. Helme reported that only one of 188 previously compromised files still contained malicious code as of 21:52 UTC on November 16.
How does JavaScript loaded by a webpage run in a visitor’s browser and interact with that page?
In general, JavaScript is code a webpage can ask a browser to run. When a browser loads a page’s scripts, those scripts can interact with parts of that page, such as its displayed content and form fields. This helps websites provide interactive features, but it also means unsafe or malicious code can misuse access to page information. This general explanation draws on established technical knowledge; the article does not describe browser execution in detail.
The incident provides a concrete example. Optimizely scripts were included in customer webpages, and attackers injected code into some customer projects. The additional track.js payload searched webpages for wallet addresses and payment-card details, and the injected code could load that payload.
The article also reports that the malware could collect cookies, webpage URLs, and screenshots, and load further scripts targeting iPhones and iPads. Optimizely removed injected code and blocked its delivery through Cloudflare. The article does not establish how many visitors’ browsers actually executed the malicious code or how many were harmed.
This brief was written by AI from the original reporting and checked by other models. Names, figures and quotes come from the source; read it for full context.
Read more in the JupiteX app
Pulse is free. New stories every 4 hours, each one broken into the questions that explain it.
Or read more news on the web