If you visited BBC, CNN, Zoom, HSBC, Equifax, IKEA, Ledger or another major site on Nov. 16, the first question is whether you entered card details, copied a crypto address or used an unpatched iPhone. Attackers abused Optimizely Web Experimentation to place malicious JavaScript in 188 snippets across at least 178 organisations between 04:21 and 23:11 UTC. Optimizely said it had fixed the vulnerability and removed the injected code in its status update on Nov. 17.
Related: Directly relevant to iOS exploit kit mitigation.
For context, see Relevant: Third-party Salesforce integration breach & phishing.
Related: coverage from giganectar.
Visitors to websites run by 178 organisations, including Zoom, BBC, CNN, HSBC, Equifax, Salesforce, IKEA and Ledger, were served malicious JavaScript through Optimizely Web Experimentation on November 16, 2026. While the affected Optimizely snippets are now clean, people who entered card numbers into native site forms after 13:43 UTC, copied crypto addresses, or used iPhones below iOS 18.7.3 or iOS 26.3 should take protective action.
For context, see Relevant: Major enterprise credential & data harvesting.
## Were you affected? Four checks for cards, crypto and iPhones
For context, see Relevant: Supply chain firmware/code compromise.
The script could replace a copied cryptocurrency address with one controlled by an attacker. Researchers reported that the attacker’s wallets received roughly $7,000 to $7,150 in crypto, and that those wallets were emptied early on Nov. 17. That is a reported on-chain estimate, not a complete measure of losses. It also added a card skimmer to native checkout forms after 13:43 UTC. Payment fields run by a separate provider in a cross-origin frame were out of the skimmer’s reach, because a script on the surrounding page cannot read a payment frame from another domain.
| If this happened | Main risk | What to do |
| — | — | — |
| You copied a crypto address | Address substitution | Check wallet history and recipient addresses |
| You typed a card into a native form after 13:43 UTC | Card-data capture | Contact the issuer and review transactions |
| You used an iPhone below iOS 18.7.3 or 26.3 | Exploit-kit targeting | Update iOS immediately |
| You only read a page | Lower, not zero, exposure | Update software and monitor accounts |
The iPhone portion targeted iOS 13 to 17 through Coruna and iOS 18 through DarkSword. Pages on iOS 18.6 or earlier could reload every 60 seconds as the exploit retried. According to Report URI’s analysis, the kit’s own comments list iOS 18.7.3 and later, and iOS 26.3 and later, as patched.
## How the attack reached so many websites
Optimizely lets customers add Project JavaScript that runs across their pages. The attacker inserted code into that field while leaving the rest of the snippet intact. The injected loader pulled a script from the domain 1688360.cc. At HSBC, a backup copy of the malicious code ran through JavaScript’s `eval()` function, which the site’s security settings allowed.
This is why people should not assume a familiar brand means a page was safe on that day. Salesforce disabled Optimizely scripts as a precaution. Website operators should audit Project JavaScript, review logs back to the start of the exposure window, and consider rotating relevant credentials as a precaution.
**Which websites and iPhone versions were affected by the Optimizely malware attack?**
The incident affected 188 Optimizely snippets across 178 organisations, including Zoom, BBC, CNN, HSBC, Equifax, Salesforce, GitLab, IKEA, Ledger and Peacock. The iPhone exploit kits targeted iOS 13 to 17 (Coruna) and iOS 18 (DarkSword); the kit’s own comments list iOS 18.7.3 and later, and iOS 26.3 and later, as patched.
Watch for breach notices from affected services and for Optimizely’s root-cause report. If you made a purchase or crypto transfer during the window, keep transaction records before contacting your bank, card issuer or wallet provider.
—