178 Big-Name Sites Got Hit by a Hijacked Script — Here's What Went Wrong

·
Listen to this article~4 min
178 Big-Name Sites Got Hit by a Hijacked Script — Here's What Went Wrong

A flaw in Optimizely let attackers inject malicious code into scripts loaded by CNN, the BBC, Zoom, and 175 other sites — skimming cards and targeting iOS devices.

So here's something that should make you sit up a little straighter. An attacker found a flaw in Optimizely Web Experimentation and used it to slip malicious code into the very scripts that customer websites load from the service. Optimizely confirmed it early today. That's not a small thing. When you load a script from a third party, you're basically trusting that script to behave. Most of the time, it does. This time, it didn't. ### Who got caught in the crossfire According to Report URI — a firm that keeps an eye on the scripts websites actually run — visitors to sites operated by at least 178 organizations received the malicious code yesterday. The list reads like a who's who: CNN, the BBC, Zoom. Household names. Sites you'd never expect to hand you something nasty. And that's the uncomfortable part. You don't have to visit a sketchy corner of the internet to run into trouble. Sometimes trouble comes to you, riding along on a script your favorite site trusts. ### What the code was actually doing The planted code was built to do two things, depending on who was visiting: - **Skim card data** — harvest payment information on checkout pages where shoppers least suspect it - **Serve iOS exploit kits** — attempt to compromise visitors browsing on Apple devices So you've got two very different threats sharing the same delivery vehicle. One goes after your wallet. The other goes after your device. Neither is the kind of thing you want quietly loading in the background while you're reading the news or joining a work call. ### Why this matters even if you're not a developer Here's the thing people miss. Third-party scripts are everywhere. Analytics, A/B testing, chat widgets, ad trackers — your average site is practically held together with them. Each one is a small act of trust. > "You can lock your own front door perfectly and still get robbed if the building's maintenance crew leaves the master key lying around." That's essentially what happened here. The organizations on that list didn't do anything reckless. They used a legitimate tool the way it was designed to be used. The flaw was upstream. ### What you can actually do about it A few practical moves, whether you run a website or just browse them: - If you manage a site, audit your third-party scripts regularly and remove anything you're not actively using - Keep an eye on vendor security advisories — Optimizely customers should check for updates and guidance directly - Use a browser that isolates or blocks scripts you don't need - Be extra cautious entering card details on sites that lean heavily on external scripts, especially if something feels off ### The bigger takeaway Supply chain attacks like this aren't going away. They're efficient. Instead of breaking into 178 companies one by one, an attacker compromises a single service and inherits all of its customers overnight. The lesson isn't "avoid the internet." It's that trust has to be earned continuously, not granted once and forgotten. Check your scripts. Question the defaults. And when a story like this drops, pay attention — because next time, it might be a site you use every single day.