Security researchers blew the whistle this week on a blunt, smart attack that hit at least 178 major websites through a trusted vendor. The hit came not by breaking into each company’s servers, but by slipping malicious code into a popular web‑experiment tool. If you run a business website or carry a phone, you should care — and your tech team should stop pretending “trusted CDN” equals “safe.”
What researchers found
Scott Helme and the team at Report URI published a technical disclosure showing attackers injected malicious JavaScript into Optimizely Web Experimentation projects. The infected snippets were served from Optimizely’s CDN and reached sites like CNN, BBC, Zoom, Salesforce, IKEA, HSBC, Ledger and many more. The code did classic and ugly things: it tried to swap crypto wallet addresses, skim credit‑card details from non‑hosted forms, steal cookies and screenshots, and even attempt to load iOS exploit kits to attack unpatched iPhones and iPads.
How the supply‑chain trick worked
This was a textbook supply‑chain compromise. Optimizely lets customers add custom Project JavaScript that runs on every page the snippet touches. Attackers found a weakness in the Experimentation signup/account flow and injected malicious ProjectJS into many customer projects. Because the files were still served from cdn.optimizely.com, the code looked legitimate to browsers and basic checks — which is exactly why this is so dangerous.
Why this matters — and who’s responsible
The attack shows a hard truth: when you put a lot of trust in a single SaaS provider, one flaw becomes everyone’s problem. Report URI’s telemetry even showed the attackers cashed out roughly seven thousand dollars in small crypto transfers during the observed sweep. That’s small change to cybercriminals, but big trouble for victims. Optimizely has removed the injected code and says it fixed the signup‑flow vulnerability, but cleaning up is not the same as preventing the next nightmare. Companies that outsource critical JavaScript and blindly trust CDNs share the blame for lax controls.
What companies and users must do now
Site operators should act like this attack was personal — because it was. Audit every Optimizely ProjectJS field and any third‑party experiment code now, search for the attacker domains and unknown snippets, rotate passwords and API tokens, and consider hosting critical scripts locally or enforcing a strict Content Security Policy. For users: update iPhones and iPads to the latest patched iOS, clear browser data if you visited affected sites, enable Lockdown Mode if you can’t patch immediately, and check crypto and card activity if you made payments while a suspect tab was open. Regulators and corporate boards should also stop treating vendor security as optional. If your business trusts “trusted CDNs” without verification, you’re just waiting for the next headline.

