Supply chain attack on Optimizely exposed CNN, BBC and Fox News visitors
A flaw in Optimizely let attackers push malicious JavaScript to CNN, Fox News, BBC and Salesforce sites, putting visitors at risk of card theft and crypto fraud.
Key points
- Attackers exploited a flaw in Optimizely's account signup flow to inject malicious JavaScript into files loaded by CNN, Fox News, BBC, Salesforce, and dozens of other websites.
- The malicious code could swap cryptocurrency wallet addresses, skim payment card data, and deliver exploit kits targeting iPhones and iPads running older iOS versions.
- Security researcher Scott Helme found 188 compromised JavaScript files across 178 organizations, and Optimizely patched the flaw and removed the malicious code on the same day.
- Most of the affected sites either lacked a content security policy entirely or had one too loosely configured to block the attack, with 68 of 178 organizations having no CSP at all.
Visitors to some of the web's most recognized news and business sites were exposed to harmful code on Monday after a supply chain attack on Optimizely, a website personalization platform trusted by hundreds of brands. Sites including CNN, Fox News, BBC, Zoom, Salesforce, GitLab, and KLM were among those confirmed as having loaded malicious scripts, according to BleepingComputer's reporting.
The compromise worked by exploiting a weakness in how Optimizely handles new account signups for its Experimentation service. That allowed attackers to push harmful JavaScript into customer project files, which those websites then loaded automatically for every visitor who came to the page. Optimizely markets itself as a digital experience and experimentation platform that organizations use to test and personalize their websites.
How the Optimizely supply chain attack unfolded
Optimizely confirmed the breach in a statement to BleepingComputer and said it had identified the problem the same day it occurred. The company closed the vulnerable signup path, deployed a fix, removed injected code from affected customer projects, ended active user sessions, revoked access tokens, and reset credentials for compromised accounts. It also said it blocked any further code delivery through Cloudflare as an added safeguard.
"We have blocked access to the vulnerable path and deployed a fix," Optimizely told BleepingComputer. The company added that it has notified all affected customers and will post continuing updates at status.optimizely.com.
Security researcher Scott Helme was the first to identify the problem. His team analyzed 1,611 JavaScript files used by Optimizely customers and found that 188 of them had been modified, belonging to 178 separate organizations. BleepingComputer separately confirmed the infections using web scan records from urlscan.io, verifying that the malicious script had loaded or tried to load on a range of well-known sites.
The earliest injection Helme's investigation found happened in the early morning hours of November 16. By that evening, Optimizely's cleanup effort had brought the count of still-infected files down to one out of the original 188, as of 21:52 UTC.
Three ways the malware put visitors at risk
The tampered JavaScript files were built to pull in a second-stage script from an external server operated by the attackers. That script carried three distinct threats, any of which could affect ordinary visitors who did nothing wrong and had no way to detect what was happening in their browser.
The first was cryptocurrency address swapping. When a browser displayed a page containing a crypto wallet address, the malware replaced it with one controlled by the attackers. Anyone who sent a transfer to what they thought was a legitimate address may have directed funds to the attacker instead.
The second threat was payment card skimming. The script watched for credit card numbers, expiration dates, and security codes typed into page forms. When it found them, it attempted to transmit that data to an attacker-controlled server. This kind of attack is especially dangerous because it is invisible to the user and happens before any payment is submitted or confirmed.
Third, the malware loaded additional payloads aimed at iPhones and iPads. Helme identified those secondary tools as the Coruna and DarkSword exploit kits, which are designed to take advantage of vulnerabilities in older versions of iOS and iPadOS. The malicious script could also collect browser cookies, page addresses, and screenshots, sending that information back to the attacker's infrastructure.
Cryptocurrency wallets tied to the attack had collected approximately $7,000 in transactions as of November 16, BleepingComputer reported. Some of those wallets had seen activity before the attack began, which makes it difficult to determine exactly how much money was stolen during the campaign itself.
What Salesforce and other companies said
Salesforce told BleepingComputer it found modified Optimizely scripts on some of its websites and moved quickly to shut them down. As a precaution, the company said it had disabled Optimizely scripts across both preview and production environments while its investigation continues. Salesforce said it would notify affected customers if it found evidence of unauthorized access to their data.
Other organizations confirmed as having loaded the malicious script include Zoom, GitLab, KLM, Scheels, American Girl, Smartsheet, and Stamps.com. That list spans aviation, retail, software development, and consumer goods, showing how broadly Optimizely's platform is used and how quickly a single compromised third-party tool can spread harm across unrelated industries.
The security gap that made the damage worse
A content security policy, or CSP, is a browser-level rule set that tells a site which outside servers it is allowed to load code from. Without one, a browser will run any script a page requests, including injected malicious ones.
Another 50 of those organizations did have a CSP, but their rules were written broadly enough that the attack slipped through anyway. That means the large majority of affected organizations had either no protection or protection that failed in practice. CSP has been a recognized web standard since 2014, and security experts have long called on payment processors to require it before allowing websites to handle card data directly on their pages.
This gap extends well beyond Optimizely. Any website that loads third-party JavaScript, whether from analytics tools, advertising networks, or personalization platforms, faces the same kind of exposure. A strict CSP that explicitly names only the servers a site actually uses is one of the more effective defenses available, yet adoption across the web remains uneven.
What to watch next
Optimizely said it will continue to publish updates at its status page and has already reached out to customers it believes were affected. How many site visitors were exposed before cleanup is still unclear. The company has not disclosed a visitor count, and it may be some time before the full scope emerges from the ongoing investigation.
Watch for statements from other organizations whose sites appeared in the scan results. Several, including Salesforce, have confirmed they are investigating. Others had not issued public statements as of the time of BleepingComputer's reporting. If you use a service or employer whose site runs on Optimizely, it is worth checking their security advisories or status pages for updates.
Steps to take if you visited an affected site
Start with any cryptocurrency transactions you made that day. Check the wallet addresses you sent funds to and confirm they match what you intended. If the destination looked different from what you expected, that may be a sign the malware altered the address before you sent the transfer.
If you entered payment card details on any of these sites, review your credit card and bank statements for charges you do not recognize. Contact your card issuer if you spot anything unusual. It is also reasonable to ask for a new card number as a precaution, because skimmed card data can be used for fraud weeks or months after the original theft.
iPhone and iPad users should check that their devices are running the most recent version of iOS or iPadOS. The exploit kits bundled in this attack were built to target older software versions, so keeping devices updated is the simplest defense. If you were signed into any accounts while browsing an affected site, review those accounts for logins or activity you do not recognize, and change your password if anything looks off.
Sources
More from the network
Junious Media Network ↗Yellowjackets Season 4 Is the Show's Final Chapter
Showtime's survival drama Yellowjackets concludes after four seasons, with creators Ashley Lyle and Bart Nickerson saying the story is complete and no spinoff is planned.
junidaily.media ↗S&P 500 Drops Into Correction as AI Stocks Fuel Worst Week in 18 Months
AI-stock losses pushed the S&P 500 down 3.7% Friday, dragging the index into correction territory for the first time since March 2025.
junidaily.media ↗Macy's 100th parade will open with a 10-minute Broadway medley
NBC and Macy's will open the 100th Thanksgiving Day Parade on Nov. 26 at 8:30 a.m. with a 10-minute all-star Broadway medley introduced by Julianne Hough.
junidaily.media ↗Army Delays Iowa Lead Azide Blast After Toxic Plume Concerns
The U.S. Army postponed a controlled detonation of degraded lead azide in Iowa after residents and lawmakers raised safety concerns about a toxic lead plume.
junidaily.media ↗