Incident sheet · /security

Filed
Read
4 min · 791 words
Severity
Routine

Optimizely Script Compromise Hit 178 Firms' Sites Without Breaching Them

Malicious JavaScript in Optimizely Web snippets hit 178 organizations' sites, skimming cards and stealing $7,000 in crypto — without breaching a single victim's own infrastructure.

Optimizely supply chain attack turns trusted scripts against 178 orgs
FeedOptimizely supply chain attack turns trusted scripts against 178 orgs — shuraki / pixabay

Event log

  1. Supply chain attack on Nov. 16 infected 188 Optimizely Web snippets across 178 organizations including Salesforce, HSBC and Equifax
  2. Attacker stole about $7,000 in cryptocurrency; payload also skimmed cards, stole cookies and delivered iOS exploit kits
  3. Malicious code ran roughly 17 hours, from about 4 a.m. to 9 p.m. UTC, before cleanup
  4. None of the victim organizations were directly breached — the vendor's script delivered the malware
  5. Most victims lacked a CSP or monitoring tool capable of detecting the attack

Malicious JavaScript embedded in Optimizely Web snippets served malware to visitors of 178 organizations' websites on November 16 — including Salesforce, Zoom, GitLab, Equifax, HSBC, CNN and Ikea — without attackers touching any of the victims' own infrastructure.

Web security vendor Report URI uncovered the campaign, which infected 188 Optimizely snippets across the 178 organizations. Optimizely Web is an experimentation and content-optimization tool that enterprises embed in their pages. By 21:52 UTC on the day of the attack, cleanup was nearly complete: only 1 of the 188 infected snippets still carried the malicious script. How the attacker obtained write access to unrelated customers' Optimizely projects remains unclear; Optimizely had not responded to inquiries as of publication. The malware arrived with a valid certificate from Optimizely's own content delivery network.

In short: a vendor script turned hostile, and trusted brand sites distributed it.

What did the payload actually do?

According to Report URI, the injected code:

  • Swapped cryptocurrency wallet addresses on pages
  • Skimmed payment card data
  • Stole cookies
  • Took screenshots
  • Delivered the Coruna and DarkSword iOS exploit kits to iPhones and iPads

By the evening of November 16, the attacker had stolen roughly $7,000 in cryptocurrency from the affected sites' users — a modest sum that understates the damage.

"The uncomfortable lesson is that none of the victims were breached," said Scott Helme, the researcher who discovered the campaign. "Their own infrastructure was untouched; a vendor's script turned hostile and their sites served it to every visitor."

Why the $7,000 figure understates the impact

"But money is only the part we can count," cautioned Peter Lowe, threat research lead at ZeroFox. "Non-HttpOnly cookies, card details typed into sites' own forms rather than a hosted payment frame, and the iOS exploit chains served to anyone on an unpatched iPhone are all impacts nobody can measure from the outside."

Lowe advised organizations to audit their code for JavaScript and other third-party assets, then set up monitoring. Optimizely customers should "check the Project JavaScript yourself and rotate everything that can write to it — users, tokens, integrations," he said.

The lesson for security leaders is that measured losses are the floor, not the ceiling.

Whose breach is it when a script turns hostile?

"When it runs on your page and skims your customer's card, it's your breach, not your vendor's," said George Gerchow, CSO at Bedrock Data and IANS faculty member. "This one ran for about 17 hours on some of the biggest sites in the world." The attack ran from roughly 4 a.m. UTC until most sites were cleaned around 9 p.m.

Gerchow argued every company running third-party scripts should know which scripts can execute on login and payment pages, lock down where that code sends data, and get alerted the moment a script changes.

Self-hosting the snippet did not help. Helme reported that some victims served Optimizely's file from their own domains and were still infected because they proxied the live file.

The accountability question lands squarely on the site owner, not the supplier.

What would have caught it?

"The practical starting point is a Content Security Policy in report-only mode," Lowe said. "It breaks nothing; it just has every visitor's browser tell you what loaded and where data went, and you end up with an inventory built from real traffic rather than a spreadsheet from 2023."

Helme said most affected organizations lacked a CSP or monitoring capable of detecting the attack. He and Lowe recommended alerts for unexpected new scripts, changes to trusted files, and data flowing to new destinations. CSP reporting can flag the fetch and sendBeacon requests the skimmer used to exfiltrate data.

Caveats matter. Report URI found a CSP blocked the external payload on HSBC's sites — but an inline copy embedded in the snippet still ran, because the policy allowed eval. Helme urged CISOs to push back on vendors that require unsafe-eval, or isolate them, and to strip unnecessary scripts from payment and login pages. "An A/B testing tool rarely needs to be on a checkout or account page at all," he said. "'Trusted' should mean 'allowed to do these specific things,' not 'allowed to do anything.'"

Lowe framed the real test: not whether you trust your third parties, but whether you would notice if one quietly changed overnight. "Speed is important here," he said. "A report on Friday wouldn't have been much good."

Gerchow predicted the next wave will target enterprise AI agents: "The plugin or MCP server you trusted yesterday is the delivery channel tomorrow, and an agent will run whatever it's handed. The true test is whether you'd know when what your vendor serves you changes."

via techtarget.com (Source)

Filed under

  • optimizely
  • third-party-risk
  • supply-chain-security
  • web-malware
  • content-security-policy
Share this article:

More from Amara Osei

Amara Osei

Show full bio

Correspondent covering regulation, policy and their impact on enterprise information technology and the leaders who run at CIO Monitor.

188 articles

The newsroom digest

One email a day with the stories that matter. No noise.

By subscribing you agree to the privacy policy.

Cross-references

‹ Previous articleNext article ›