READ. SCROLL. LISTEN.

Unbiased headlines. Facts, not spin.

Unbiased Headlines is an independently owned news organization. We bring you the facts, not opinions, written fresh from 110+ named sources. Sources linked so you can verify it yourself.

← Back to headlines

Hijacked Optimizely scripts served card-skimming code and iOS exploit kits to visitors of at least 178 organizations, including CNN, BBC and Zoom

Hijacked Optimizely scripts served card-skimming code and iOS exploit kits to visitors of at least 178 organizations, including CNN, BBC and Zoom
Attackers exploited a flaw in Optimizely's account signup flow on Monday, Nov. 16 and planted malicious JavaScript in customer projects. Visitors to sites run by at least 178 organizations were served code built to swap crypto wallet addresses, skim cards and deliver iOS exploit kits. The damage so far looks small, about $7,000 in crypto, but Optimizely has not explained how one signup flaw reached so many unrelated customers.

A single vulnerability at a website-testing vendor put malicious code in front of visitors to some of the biggest sites on the internet on Monday, Nov. 16.

Optimizely, which sells experimentation and personalization tools, confirmed that "an unauthorized party exploited a vulnerability in the Experimentation account signup flow" and "used it to add malicious JavaScript to some customer projects." The company said it has blocked the vulnerable path, deployed a fix, removed the injected code, ended active sessions, revoked tokens and reset access for affected accounts. It also said it has notified all affected customers.

What the code did

Security researcher Scott Helme of Report URI said his team checked 1,611 Optimizely scripts and found malicious code in 188 of them, belonging to 178 organizations. He said the real number is likely higher.

Affected sites include Zoom, the BBC, CNN, Fox News, Salesforce, GitLab, KLM, Air France, Smartsheet, Bitly and American Eagle. Helme's list also includes IKEA, HSBC, Equifax and Peacock. BleepingComputer independently confirmed through urlscan.io records that the malicious script loaded, or tried to load, on many of them.

The mechanism was simple. Optimizely customers load a script from the vendor's content delivery network, and that script runs a customer-editable field called Project JavaScript. The attacker wrote a loader into that field. The rest of each file was untouched and still came from cdn.optimizely.com with the vendor's own certificate, so the affected sites' own code and servers were never touched.

The loader pulled a second script from 1688360[.]cc/track.js. Some versions hid that address in Base64. Another carried a full embedded copy of the payload to run if the domain was blocked.

Helme's analysis found the payload replaced cryptocurrency wallet addresses on a page with the attacker's, captured card numbers, expiration dates and security codes typed into a site's own forms, and collected cookies, page URLs and screenshots. Cards entered in hosted payment forms, such as Stripe's, were out of its reach.

The iPhone angle

On iPhones and iPads, the script was set up to load the Coruna and DarkSword iOS exploit kits. Per the kits' own code, iOS 18.7.3 and later, and iOS 26.3 and later, are patched.

No researcher has reported a device takeover. Security firm Cynet retrieved the iOS stage using an emulated browser and described it as conditional delivery, "not a successful compromise" of a real device.

The money, and the timeline

The attacker's wallets received about $7,000 in cryptocurrency on Monday, according to Helme. Security firm StepSecurity put the figure at about $6,600 and noted that two of the addresses were already in use before the attack. Neither firm can see how many cards or cookies were taken.

The first injection appeared at 04:21 UTC Monday, on the BBC's script. By 21:52 UTC, Report URI found malicious code in only one of the 188 files, down from 169 at 20:56 UTC. Report URI later said every infected file was clean by 23:11 UTC, and the attacker's main server no longer resolves.

The cleanup was not tidy. Report URI said Smartsheet's script was cleaned once and then re-infected with a hidden version of the code, which it said indicates the attacker still had access at that point.

Salesforce said it is confirming Optimizely scripts are disabled across its preview and production instances. It said it is investigating and will notify affected customers "without undue delay" if it finds unauthorized access to their data.

The open question: how one flaw reached so many customers

Optimizely's incident notice, posted at 01:02 UTC Tuesday, points to the signup flow. Before that notice appeared, Helme wrote that Report URI did not know how the attacker got write access to so many unrelated customer projects, whether through a compromised Optimizely system, a credential with cross-customer access or something else. "That's for Optimizely to explain," he said.

Optimizely has not said how the signup flaw worked, how many projects were altered, when the fix went in or whether the attacker retains any access. It has not told customers publicly what to do. It says it is still investigating and will post updates at status.optimizely.com.

Report URI argues this attack was detectable and partly preventable. Helme's firm says tools that flag unexpected changes to trusted scripts would have exposed it, and that a Content Security Policy in enforcement mode could have blocked key parts of the attack. Report URI sells exactly those kinds of detection tools, and its write-up promotes them.

Helme's broader point stands apart from the sales pitch: "trusted JavaScript doesn't always remain trustworthy." A site can be compromised through a third-party dependency without its own infrastructure being breached. Cynet's researchers make a similar point, saying a site that delivered the code has not necessarily had its own systems compromised.

For anyone who visited an affected site on Nov. 16 and typed in a card number or sent crypto, the practical step is to check that day's transactions. The larger unresolved question is Optimizely's: which customer projects were altered, and how a flaw in account signup gave an outsider write access to them.

Sources used for this briefing

7 links from 7 independent newsrooms (syndicated copies of the same report count once)

These are the sources it draws on, linked so you can verify.

center
The Hacker NewsHijacked Optimizely Scripts Served Card Skimmer and iOS Exploit Kits to CNN, BBC and Zoom Visitors
unknown
blog.report-uriWorld's Largest Brands Infected With Malware Via Optimizely
unknown
The Next Web‘We have blocked access to the vulnerable path,’ says Optimizely
unknown
BleepingComputerOptimizely hack infected CNN, Fox News, BBC, Salesforce sites with malware
unknown
daily.devMalicious code served through Optimizely hit nearly 190 sites, including CNN, the BBC and Zoom
unknown
TechBytesOptimizely hack infected CNN, Fox News, BBC, Salesforce sites with malware
unknown
Mezha.netSuspected Optimizely supply-chain attack loads malware on major websites | Межа