HomeTech NewsCybersecurityOptimizely Confirms Web Experimentation Was Hijacked

Optimizely Confirms Web Experimentation Was Hijacked

Optimizely has said that an unauthorised party exploited a vulnerability in its Web Experimentation product and used it to add malicious JavaScript to some customer projects. In a 17 November status-page update at 01:02 GMT, the company said it had fixed the vulnerability, removed the injected code from affected projects, taken steps to secure affected user accounts, and added further protections to stop unauthorised code being delivered. Optimizely did not name any customers, and it did not say how many projects or sites were involved.

A fuller picture of who was reached, and what the injected code did, comes from Report URI, in a 16 November post by Scott Helme. Report URI said that on 16 November “malicious JavaScript was served to visitors of 178 organisations through the Optimizely Web experimentation platform,” and that the list included Zoom, the BBC, CNN, Salesforce, GitLab, IKEA, HSBC, Equifax, Air France-KLM, Ledger and Peacock. Those names and totals are Report URI’s findings, not Optimizely’s.

In brief

  • Optimizely says a vulnerability in Experimentation was used to inject malicious JavaScript into some customer projects, and that the code has now been removed.
  • Report URI says 178 organisations were affected, including major news, finance, retail and crypto sites, and that “crypto has already been stolen.”
  • Optimizely has not named customers or published its own count.

What Report URI says was served to visitors

Report URI described a multi-purpose kit that, it said, swapped cryptocurrency wallet addresses for the attacker’s, skimmed payment cards, stole cookies and screenshots, and on iPhones and iPads delivered the Coruna and DarkSword iOS exploit kits. “Crypto has already been stolen, with verified transactions to the attackers,” the post said. In a tally of wallets Report URI attributed to the attackers, it put receipts at about $7,040 as of 19:25 GMT on 16 November. That figure is Report URI’s, from on-chain amounts it associated with those wallets, and it is not a complete measure of card or cookie theft, which the post said it could not see.

The firm said it fetched 1,611 distinct Optimizely snippets and found the malicious code in 188 snippets belonging to 178 organisations, and that the true number is likely higher because it could only check snippets it could find in time. At 20:56 GMT it found the code in 169 of those infected snippets; by 21:52 GMT it was in only 1 of 188. Optimizely’s later status note, just after 01:00 GMT on 17 November, said the injected code had been removed from affected projects. Report URI also said Optimizely’s own public and login sites carried the code, and that some customers serve the same project snippet from their own domains. Those points, too, are Report URI’s observations.

Report URI said the attacker wrote their own code into the Project JavaScript field of customer projects, so the file was still served from Optimizely’s infrastructure, with Optimizely’s certificate, from a host the affected sites already trusted. It said it does not know how write access was obtained across so many unrelated projects, and that this is for Optimizely to explain. Optimizely’s own account is shorter: an unauthorised party exploited a vulnerability in Experimentation. The company has not, in the status-page note, described that vulnerability or published a customer list.

The pattern will be familiar to readers of TSN’s earlier supply-chain cases. SlowMist has urged sites to pull a tampered Udesk script that swapped deposit addresses, a closer cousin of the wallet-swap behaviour Report URI describes here. Polymarket halted trading after saying a third-party provider was compromised, and JFrog has described an npm worm campaign that armed dozens of GitHub repositories. In each case, the trusted third party was the path in.

A cleaned snippet is not proof that nothing was taken

Optimizely’s status note and Report URI’s sweep should be read as two different kinds of document. The company has confirmed a security incident, a vulnerability, and a clean-up. It has not, in that note, confirmed Report URI’s 178 organisations, the named brands, the iOS kits, or the claim that cryptocurrency has already been stolen. The absence of a customer list from Optimizely is not, by itself, a contradiction of Report URI’s findings, and Report URI’s findings are not a substitute for a company or regulator’s completed incident report.

The snippet counts make the same point in a narrower way. A fall from 169 infected snippets at 20:56 GMT to one at 21:52 GMT, and Optimizely’s later statement that the injected code had been removed, are evidence that the live payload was being taken out. They are not evidence that visitors who loaded those pages earlier escaped the kit Report URI describes, or that wallet-swaps, card data or cookies from that window have been recovered. Report URI’s own wallet tally is a snapshot of what it says it could see on-chain by mid-evening on 16 November, not a final loss figure.

For UK readers, the named set in Report URI’s post includes the BBC and HSBC, among other organisations that operate here. That is still Report URI’s list. Until Optimizely, those organisations, or a formal authority publishes their own account, the documented event is a confirmed product incident plus an independent researcher’s count, victim list and theft claims — including the claim, which is why this also belongs with crypto-theft reporting, that crypto has already been stolen.

Sources

Related stories

Follow @tsnmediahub on X for breaking AI news as it happens.

Follow on X

Share this story

Latest stories

More in this category

Latest stories

Explore the TSN Atlas: Every topic we cover, mapped. Click a bubble to dive in.