A new supply‑chain cyberattack has hit some of the biggest websites on the internet. Hackers quietly injected malicious JavaScript into Optimizely Web Experimentation projects. The result: wallet‑swapping code, card‑skimmers, cookie theft and even iPhone exploit loaders ran from domains people trusted. This is not a small breach — researchers found the code in Optimizely snippets tied to roughly 178 organizations, including major brands visitors think are safe.
What the hackers did — and why it matters
Security researchers found malicious scripts added to Optimizely “Project JavaScript” fields. The payloads included a wallet‑swapper that replaced real cryptocurrency addresses with attacker addresses, a card‑skimmer that grabbed numbers typed into standard payment forms, and a hidden iOS exploit loader that tried to infect phones. Because the code was served by Optimizely’s trusted CDN, it ran in visitors’ browsers as if it were legitimate. That trust trick is what made this supply‑chain attack so dangerous.
Technical fallout: scope and damage
Researchers measured millions of page loads where the injected code could have executed. On‑chain receipts linked to attacker wallets show some small crypto flows, but that number doesn’t count stolen card data, screenshots, or compromised cookies. Optimizely says it removed the code, fixed the vulnerability and brought in an outside forensics team. That’s the cleanup. The real problem is many companies still rely on one vendor’s script to run critical website functions — and the moment that vendor is breached, every customer pays the price.
Who’s responsible — and what should change
Blame belongs everywhere and nowhere: the attackers, sure, but also the vendor that let a writable project code path exist, and the big companies that didn’t harden their setups. Relying on third‑party JavaScript without strict review and least‑privilege controls is asking for trouble. Corporate boards and CISOs need to stop treating security like a checkbox. If you host customer payments or wallet addresses on pages that run external scripts, you must validate every line of code that can touch users’ data. Period.
How users and companies should respond
If you visited an affected site and entered payment or crypto details, check your bank and double‑check any crypto address before sending funds. Companies should rotate API tokens, audit project JavaScript, and tighten Content Security Policies to block unknown script hosts. Lawmakers and regulators can watch closely, but the first move must be private‑sector accountability: better vendor controls, transparent incident reports, and enforcement by boards and shareholders — not more broadband‑style handwringing.
Supply‑chain attacks like this one show the internet’s trust model can be weaponized in an instant. We should demand clearer vendor responsibility, smarter corporate defenses, and simple user practices that reduce harm. Otherwise, expect more headlines saying the biggest brands were “subverted” and shrugging that “it was complicated.” It isn’t — it’s preventable, if people in charge actually act like they’re in charge.

