One compromised testing tool put 178 major websites in attackers’ hands

Your bank, your news site and your video call app all trust the same third-party script. When that script goes bad, no amount of careful browsing on your end helps. That’s the lesson from Monday’s attack on 178 websites, including CNN, the BBC, Zoom, Salesforce, HSBC and IKEA.

According to Android Headlines, security researcher Scott Helme of Report URI spotted the malicious code. It was pushed through Optimizely, a tool companies use to A/B test different versions of their sites. Optimizely says it has removed the code.

What the code actually did

Analysis showed three separate jobs. First, it could swap cryptocurrency wallet addresses. If you copied an address to send someone crypto, the script quietly replaced it with the attacker’s. Second, it worked as a card skimmer, grabbing payment details typed into forms. Third, on iPhones and iPads, it loaded an exploit kit.

An exploit kit is a bundle of tools that tries known security holes in older software. Note the word known. The reporting says these flaws are ones Apple has already patched. So the people most at risk are those who haven’t updated.

The Apple outage was a coincidence, apparently

On Tuesday, iCloud, the App Store, Apple Pay and Apple Music went down. The timing looked ugly. But Apple told MacRumors that “an internal update caused some outages,” and Bloomberg’s Mark Gurman reported Apple said it wasn’t a cyberattack. There’s no evidence Apple accounts were compromised.

That’s Apple’s account, and it’s a plausible one. Still, it’s a company statement about its own failure, and outside verification is thin. Treat it as likely, not proven.

Why this matters beyond one incident

Companies spend heavily on securing their own infrastructure, then paste in third-party code that runs with full access to every page their customers see. Testing and analytics scripts can read form fields and clipboard activity. One vendor compromise reaches 178 brands at once, and none of those brands’ users agreed to that risk.

It’s also worth asking how long the code ran before anyone caught it. The report points to around November 16 as the relevant date, but doesn’t say how many people were exposed. Nobody has given a number for affected cards or wallets.

What you should do

  • Update your iPhone or iPad now: Settings > General > Software Update.
  • If you entered card details on any affected site around November 16, watch your statements closely.
  • If you sent crypto recently, check that the funds went to the intended address. Transactions can’t be reversed.

Updating is the one thing in your control, and it blunts the exploit kit. But the bigger fix belongs to the sites. Until they treat third-party scripts as an attack surface, expect a repeat.