On Monday, November 16, some of the most visited websites on the internet started serving malware to their own visitors. The BBC, Zoom, CNN, Salesforce, IKEA, HSBC and more than 170 other organizations were affected, and none of them had been hacked directly. The attacker got in through a single third party tool that all of them load on every page, and from there the malicious code reached everyone who visited.
That is the scale of the Optimizely supply chain attack, and if you visited any of those sites on Monday, there are two things you should do today: update your iPhone, and check your card and crypto transactions from November 15 onward.
How one vendor’s script reached 178 websites
Optimizely Web Experimentation is a tool companies use to test different versions of their web pages. A customer embeds a small Optimizely script, called a snippet, and that script runs in the browser of every visitor. The attacker exploited a vulnerability in Optimizely’s account sign up flow, impersonated administrator users, and injected malicious JavaScript into customer projects. Because the code was served from Optimizely’s own servers, with Optimizely’s certificate, every affected site treated it as trusted and served it to its visitors.
Security firm Report URI checked 1,611 Optimizely snippets and found malicious code in 188 of them, belonging to 178 organizations. The first injection was spotted in the BBC’s snippet at 04:21 UTC on November 16. Optimizely’s own preliminary report says the malicious code was live in customer projects from 07:51 to 22:24 UTC that day. The company says it detected the activity at 13:34 UTC, closed the flaw at 16:10 UTC, and removed the injected code from all affected projects by 22:24 UTC. It posted a notice on its service status page at 01:02 UTC on November 17, saying the vulnerable path was blocked and customers had been contacted directly.
The affected list, published by Report URI, includes Zoom, the BBC, CNN, Salesforce, GitLab, IKEA, HSBC, Equifax, Air France-KLM, Ledger and Peacock, plus Fox News, NPR, the ASPCA and Invisalign. Optimizely’s own website and login page carried the code too. An investigation with Mandiant is still running, and Optimizely says its root cause findings are preliminary.
What the malicious code actually did
Every affected visitor received the same payload, a script called track.js served from an attacker controlled domain. It did four things.
| Payload | What it targeted |
|---|---|
| Crypto address swapping | Wallet addresses on the page, in forms, links, images and the clipboard, covering Bitcoin, Ethereum, TRON, Solana, TON, Litecoin, Bitcoin Cash and Dogecoin |
| Payment card skimming | Card details typed into site forms |
| Data theft | Cookies and screenshots of the page sent to the attacker |
| iPhone exploit kits | Coruna for iOS 13 to 17.2.1, DarkSword for iOS 18.4 to 18.7; iOS 26 devices were only fingerprinted |
The crypto theft is the only part anyone can count. Report URI says the attacker’s wallets received about $7,040 within roughly nine hours on November 16, and the wallets were emptied early on November 17. That is the public ledger trail, not the extent of the loss. Optimizely says it has not yet confirmed whether any card data was captured.
The iPhone angle deserves a careful reading. Between 12:13 and 12:57 p.m. ET on November 16, delivery of the exploit kits expanded to every visit from iOS 18.6 or earlier. But the kits’ own comments mark iOS 18.7.3 or later, and iOS 26.3 or later, as already patched. If your iPhone is on a current version of iOS, researchers say you were not in the firing line for those particular exploit chains, and no public confirmation of a successful takeover of a real iPhone has been reported.
Check your iPhone now
That caveat is not a reason to relax. Here is what to do, in order.
1. Update iOS. The current release is iOS 27.2.1, released on November 9. It is a genuine security update, and you should install it if your phone supports it. On older models that cannot take iOS 27, install the latest 26.x or 18.x build offered, and make sure it is at least iOS 26.3 or iOS 18.7.3, the versions that close the Coruna and DarkSword chains used in this attack. Go to Settings, General, Software Update. Our iOS 27.2.1 update guide walks through what it fixes.
2. Check your cards. If you entered card details on any affected site on November 15 or 16, review those statements for charges you do not recognize, and keep watching for the next few weeks. Skimmed card data is often used slowly. If anything looks wrong, call your bank first, then dispute the charge.
3. Check your crypto. If you copied a wallet address from, or pasted one into, an affected site on November 16, check the transaction history for that wallet. The address swapping worked by replacing the address on the page or in your clipboard, so a payment sent that day may have gone to the attacker. Verify the destination address on any transaction you made that day.
4. Consider Lockdown Mode only if you are a target. Apple’s Lockdown Mode is built for people at high risk of targeted attacks, and Apple says it protects against the specific out of date iOS web attacks described in its April 2026 guidance. For most people, being on current iOS is enough. Turning on Lockdown Mode trades away features most people use daily.
The bigger lesson: your browser trusts too much
This attack worked because of a design choice, not a bug in your phone. Modern websites load dozens of third party scripts, analytics, testing tools, chat widgets, ad code, and your browser runs them all with the same trust as the site’s own code. One compromised vendor becomes 178 compromised websites, and the visitor has no way to tell.
That is why the practical advice is so short: keep your software current, and check your money after an incident like this. The attack itself lasted about a day, and Optimizely says the code is gone. But the window it opened, for card data typed into forms and crypto addresses copied from pages, stays open until the people who visited those sites check what happened.
If you visited the BBC, Zoom, CNN or any of the other affected sites on November 16, do the checks today. It takes five minutes, and it is the only way to know whether the attack reached you.
Sources: Report URI analysis, November 16; Optimizely preliminary incident report and status page; McAfee; Jscrambler; The Hacker News. See also our Chrome 157 security update and the latest on the iOS 27 kernel exploit research.
