If you browsed Zoom, CNN, the BBC, HSBC or IKEA on Sunday, November 16, the page you loaded may have carried more than ads and analytics. For most of that day, a script that big companies use to run A/B tests was quietly serving malware to their visitors. It tried to swap crypto wallet addresses, skim card numbers and, on iPhones and iPads, load two known iOS exploit kits.
The tool at the center of it is Optimizely Web, an experimentation platform that lets marketing teams test different versions of a page. Security researcher Scott Helme of Report URI spotted the malicious code and published a detailed breakdown of the attack. UNILAD Tech picked up the story with a warning for iPhone owners, and the details since then make it clear this one is worth a few minutes of your time.
The short version
- Attackers abused a flaw in Optimizely’s account signup flow to plant code inside customer projects.
- Report URI found 188 infected scripts belonging to 178 organizations, including Zoom, CNN, Fox News, the BBC, Salesforce, GitLab, HSBC and IKEA.
- The code swapped crypto addresses, skimmed card details, grabbed cookies and screenshots, and pushed iOS exploit kits to iPhones and iPads.
- You did not need to buy anything. Just loading a page on an iPhone was enough for the exploit code to run.
- Optimizely says the hole is fixed and the code is gone. That doesn’t undo any infection that already happened.
How a testing tool became a malware pipeline
Optimizely Web works by having every customer site load a small JavaScript “snippet” from Optimizely’s own servers. That snippet holds Optimizely’s code, the customer’s experiments and an optional field called Project JavaScript, which is custom code that runs on every page of the site.
That last field is what the attackers went after. They wrote their own loader into the Project JavaScript of customer projects and left the rest of each file alone. The poisoned file was still served from cdn.optimizely.com, with Optimizely’s certificate, from a domain every affected site already trusted. To the browser, nothing looked wrong.
Optimizely confirmed the cause to BleepingComputer: “an unauthorized party exploited a vulnerability in the Experimentation account signup flow” and used it to add malicious JavaScript to some customer projects. The company says it blocked the vulnerable path, removed the injected code, ended active sessions, revoked tokens and reset access for affected accounts.
How the attack reached your browser
1. A FLAW IN SIGNUP
Attackers abuse a bug in Optimizely’s account signup flow to get write access to customer projects.
2. ONE LINE OF CODE
They add a loader to each project’s custom JavaScript that pulls in a file called track.js.
3. TRUSTED DELIVERY
Optimizely’s CDN serves the poisoned snippet to every visitor of the affected sites.
4. FOUR ATTACKS AT ONCE
Crypto swapping, card skimming, cookie and screenshot theft, plus iOS exploits on Apple devices.
Helme saw three versions of the loader. Most pointed straight at a domain called 1688360.cc. Some hid that address in base64, so a simple search wouldn’t find it. A third carried a full inline copy of the payload, which would still run if the domain was blocked. Smartsheet’s snippet was cleaned at one point and then reinfected with the hidden version, which shows the attacker still had access while the cleanup was underway.
What the malicious script actually did
Every visitor got the same file, and every part of it was switched on at once. What happened to you depended on your device and what you did on the page. Report URI says the payload was rebuilt 26 times during the day as the attacker added features and wallets.
| Feature | What it did | Who was at risk |
|---|---|---|
| Crypto address swapping | Replaced BTC, ETH, Solana, TRON, TON and other wallet addresses in page text, forms and even your clipboard | Anyone who copied or sent crypto while a tab was open |
| Card skimming | Watched forms for a card number, expiry date and CVV, then sent all three to the attacker | People who typed a card into a site’s own form (not Stripe or Adyen iframes) |
| Cookie and screenshot theft | Grabbed readable cookies and a screenshot of the page when it found payment wording | Logged-in visitors on pages with wallet or payment content |
| iOS exploit kits | Loaded the Coruna and DarkSword kits in a hidden frame, picked by your iOS version | iPhone and iPad users on older iOS versions |
The crypto part was already making money. As of 19:25 UTC on November 16, the attacker’s wallets had received about $7,040, almost all within roughly nine hours. Report URI also found that one TRON wallet had been in use since March 2026, so this group was active long before this campaign. Nobody outside the attackers knows yet how many card numbers or cookies reached their server.
Why iPhone owners are being singled out
The part that made headlines is the iOS payload. On iPhones and iPads, the script read the device’s iOS version and loaded a matching exploit chain. Both kits are known. Coruna was disclosed by Google in March 2026 as a set of exploits aimed at older iOS releases, and DarkSword was reported shortly after as a full chain used by state-backed groups and spyware vendors.
The good news is that Apple has already patched what these kits go after. According to Report URI, the kit’s own code comments say iOS 18.7.3 and later, and iOS 26.3 and later, are patched. One telltale sign on vulnerable phones: pages on iOS 18.6 or earlier would reload every 60 seconds as the script retried the exploit.
Is your iOS version in the danger zone?
Based on Report URI’s analysis and public research on Coruna and DarkSword
High risk
iOS 18.6 or older, or any iOS 17 and earlier build that never got updated
Update now
iOS 18.7 to 18.7.2, or iOS 26 builds older than 26.3
Patched
iOS 18.7.3 or later, iOS 26.3 or later, or Lockdown Mode turned on
Researchers also say that phones with Lockdown Mode enabled were protected from both kits. Lockdown Mode is an optional setting that strips out risky web features, and it’s aimed at people who may be targeted by spyware. Most people don’t need it day to day, but it’s worth knowing it exists.
It’s important to keep this in proportion. Researchers finding exploit code on a page doesn’t mean every visitor was hacked. Reuters said it couldn’t confirm whether the code worked in each case. If your iPhone was up to date on November 16, the exploit chains had nothing to work with. We saw a similar pattern over the weekend, when Binance warned iPhone users about an iOS sandbox bug: the fix was already out, and the people at risk were the ones who hadn’t installed it.
Which sites were hit
Report URI checked 1,611 Optimizely snippets it could find and confirmed 188 were infected. BleepingComputer independently confirmed the script loaded, or tried to load, on Zoom, KLM, GitLab, the BBC, CNN, Smartsheet, Stamps.com, Salesforce and others. Fox News, Air France, HSBC Insurance, Bitly, Change.org, UNICEF USA, American Eagle and Optimizely’s own login page were also on the list.
1,611
snippets checked
188
infected snippets
178
organizations affected
$7,040
crypto stolen by 19:25 UTC
The real number of affected sites is probably higher, since researchers could only check snippets they found in time. Salesforce told BleepingComputer it disabled Optimizely scripts across its sites as a precaution. Equifax told Reuters it stopped using the platform and found no sign its own systems were compromised. IKEA said it was assessing the impact on customers.
The cleanup, hour by hour
The good news is that the cleanup moved fast once the alarm went up. Here’s how the number of still-infected snippets dropped on the evening of November 16, according to Report URI’s scans.
Infected Optimizely snippets still live (of 188)
Source: Report URI scans, November 16, 2026 (UTC)
20:56 UTC: 169 infected
21:52 UTC: 1 infected (TalkTalk)
Optimizely’s status page moved the incident to “monitoring” at 01:02 UTC on November 17, saying it had fixed the vulnerability and added protections to stop unauthorized code from being delivered. What the company hasn’t explained yet is how one signup bug gave someone write access to so many unrelated customer projects at once.
What to check if you visited an affected site on November 16
Your 5-minute checklist
- Update your iPhone or iPad. Go to Settings, General, Software Update. You want iOS 18.7.3 or later, or iOS 26.3 or later.
- Check any crypto transfers you made on November 16. Compare the destination address to the one you meant to use, character by character.
- Watch your card statements if you typed a card number into any site that day. Call your bank if anything looks off.
- Log out and back in to important accounts you used in the browser that day, and turn on two-factor authentication if it isn’t on.
- Watch for odd behavior on older iPhones, like pages that reload every minute. If you suspect a compromise, back up and consider a full reset.
One extra tip for crypto users: always check the first and last several characters of a wallet address after pasting it, and never trust the clipboard on a page you didn’t expect to be handling money. This attack swapped addresses on copy, so the wrong address would have looked like it came from you.
The bigger lesson
None of the 178 companies needed a bug in their own code to end up serving malware. They trusted a third-party script, and that script changed under them. This is the same supply chain problem we keep seeing in developer tools, like the recent case where a stolen API key let hackers backdoor a Claude Code extension in Cursor. One weak link upstream reaches everyone downstream.
Defenses exist. A strict Content Security Policy can block scripts from loading unknown domains like 1688360.cc, and monitoring tools can flag when a trusted file suddenly changes. For regular users, the advice is simpler and less exciting: keep your phone updated, double-check where your money is going, and keep an eye on your card statements for the next few weeks.
About this article: GeekBlog covers U.S. technology news, AI, phones, smartwatches and gaming. Every story is written and checked under our Editorial Policy. Spotted a mistake or have a story tip? Contact our editors.

