Key Takeaways
- Infected Website Scripts: On Nov. 16, 2026, the Optimizely hack spread malicious code through a website testing tool used by 178 organizations, including Zoom, the BBC, CNN, and HSBC. The code could skim cards, capture cookies and screenshots, and swap crypto wallet addresses.
- Which Devices Faced Risk: During the Optimizely hack, a page visit could trigger Coruna or DarkSword on vulnerable versions of iOS 13 through 18. The iOS 26 code only collected device details, iOS 27 was outside the reported targets, and successful device takeovers remain unconfirmed.
- Updates and Payment Checks: After the Optimizely hack, install the newest update your iPhone or iPad offers, such as 27.2.1, 26.7.3, or 18.7.12. Check your statement if you used an affected site’s own checkout form, and verify any crypto transfers you made on Nov. 16.
If you opened Zoom, checked the BBC or CNN, or visited HSBC on Monday, Nov. 16, the page could have quietly loaded code aimed at your iPhone or iPad. During the Optimizely hack, attackers used a website testing tool to slip malicious JavaScript onto sites belonging to 178 organizations over the course of the day. If your iPhone or iPad already runs the latest software your model offers, it has the fixes for the known exploits used in the attack.
For devices covered by Apple’s Nov. 9 releases, that means version 27.2.1, 26.7.3, or 18.7.12, depending on your model. If you typed your card number into an affected site’s own checkout form that day, keep an eye on your statement even if your iPhone was up to date. The card skimmer ran in the webpage and could collect payment details on other devices too.
| Key Fact | What We Know |
|---|---|
| What happened | Attackers inserted malicious code into Optimizely Web customer projects |
| When it happened | Nov. 16, 2026, from about 0421 to 2311 UTC, with most infected files clean by 2152 UTC |
| Organizations affected | 178 identified, with 188 infected scripts out of 1,611 checked |
| Sites you might recognize | Zoom, BBC, CNN, Fox News, HSBC, Salesforce, IKEA, and GitLab |
| What the code could do | Run iPhone exploits, skim payment cards, capture browser cookies and screenshots, and swap crypto wallet addresses |
| iPhone exploit kits | Coruna for iOS 13 through 17 and DarkSword for iOS 18, with narrower vulnerable ranges |
| Which iOS to use | The newest version your device offers. The kit treated iOS 18.7.3 and later and iOS 26.3 and later as patched |
| Who found it | Security researcher Scott Helme of Report URI |
| What Optimizely says | It fixed the signup flaw, removed the injected code, and notified affected customers |
Sourced from Report URI, BleepingComputer, Apple’s security releases, and Optimizely’s incident notice.
How the Optimizely Hack Reached Your Browser
Companies use Optimizely to test different versions of a webpage and customize what you see. To do that, their pages load a JavaScript file tied to their Optimizely project. The file gave the attackers a way into your browser, and the place to start is with what they changed inside it.
How Attackers Altered the Script
Optimizely lets customers add their own code in a field called Project JavaScript. The attackers put their code there, leaving the rest of each file alone. Your browser could still download the file from Optimizely’s usual domain over a connection with a valid certificate. As Helme explained, Optimizely’s delivery network simply served the file it had been given.
That’s how the same attack could reach you on sites run by several unrelated companies. The changes happened in Optimizely’s customer projects, with the brands’ own servers untouched. When you opened an affected page, it loaded the script as part of the site.
Optimizely told BleepingComputer that the attackers got in through a flaw in the signup process for its Experimentation accounts. The company says it blocked that path and removed the added code. How the attackers went from exploiting one signup flaw to editing so many unrelated projects is still unclear.
Which Sites Loaded the Infected Script
Report URI identified 178 organizations, and the total could be higher because researchers could check only the files they found. Even sites that hosted their own copies of the Optimizely script were affected, including Scheels and Vodafone Australia. If you’re trying to remember where you went that Monday, start with these examples.
| Sector | Examples Report URI Identified |
|---|---|
| News and Media | BBC, CNN, Fox News |
| Banking and Finance | HSBC, Equifax, ABN AMRO |
| Retail and Fashion | IKEA, American Eagle, Levi’s, ASOS |
| Airlines and Travel | Air France-KLM, Alaska Airlines and Hawaiian Airlines, Transavia |
| Telecom | Virgin Media, Vodafone Australia, O2, TalkTalk |
| Technology | Zoom, Salesforce, GitLab, Smartsheet |
Sourced from Report URI’s list of affected organizations.
ASOS appears on the list for this attack. You may also remember the earlier ASOS data breach, which was a separate incident.
What the Code Could Do on Your Device
What you did on the page mattered just as much as the device you used. Some of the code watched for things like a card payment or a crypto transfer, while the part aimed at older iPhones and iPads could start as soon as the page loaded. Here’s what that meant for your device and the information you entered.
On iPhones and iPads
- Exploit attempts. The script checked your software version and loaded Coruna or DarkSword in a hidden part of the page. Visiting the page alone could trigger an attempt. Whether any iPhone or iPad was successfully compromised in this attack remains unclear.
- Device fingerprinting. On iOS 26, the code researchers found appeared limited to collecting details about your device.
On Any Device
- Card skimming. The code could read your card number, expiration date, and security code if you entered them into the site’s own payment fields. Payment boxes hosted separately by Stripe or Adyen were out of its reach. Report URI first saw the card skimmer at 1343 UTC.
- Cookies and screenshots. When the script swapped a wallet address near payment text, it could send a screenshot of the page and any browser cookies it was able to read.
- Crypto address swaps. The script could replace a wallet address you copied with one the attackers controlled. About $7,000 went into the wallets linked to the code on Nov. 16, though the amount stolen in this attack is unclear.
Which iOS Versions Have the Fixes
Your iPhone’s version number tells you more than the age of the phone. Apple issued Coruna fixes for devices that still run iOS 15 or 16, and it made DarkSword protections available to more devices through iOS 18.7.7. Find your current version below to see which update to look for.
| Your iOS Version | What Targeted It | Protection Against This Attack | What to Install |
|---|---|---|---|
| iOS 13 or 14 | Coruna | Vulnerable | Move to iOS 15.8.8 or the newest version your device offers |
| iOS 15 or 16 on older devices | Coruna | Fixes in iOS 15.8.7 and 16.7.15 or later on the respective versions | iOS 15.8.8 or 16.7.16 |
| iOS 17 | Coruna through iOS 17.2.1 | Patched from iOS 17.3 | The newest version available for your device |
| iOS 18.0 through 18.7.x | DarkSword was reported on iOS 18.4 through 18.7 | The kit treated 18.7.3 and later as patched. iVerify advised 18.7.6 or later. Apple included protections in 18.7.7 | iOS 18.7.12 for iPhone XS, XS Max, and XR, or iOS 26 or 27 if offered |
| iOS 26 | Device fingerprinting observed | The kit treated iOS 26.3 and later as patched | iOS 26.7.3 or the latest iOS 27 release if offered |
| iOS 27 | Outside the reported targets | No iOS 27 exploit reported in this attack | iOS 27.2.1 |
Sourced from Apple’s security releases and advisories, Report URI, 9to5Mac, and SecurityWeek.
Why do you see three different numbers for iOS 18? The 18.7.3 threshold came from the attack kit’s own code, 18.7.6 was iVerify’s recommendation, and 18.7.7 was the update Apple made available to more devices with DarkSword protections. For an iPhone XS, XS Max, or XR, Apple’s Nov. 9 release was already ahead of all three at iOS 18.7.12.
Install the newest version your device offers. If you have an older iPad, look for the corresponding iPadOS release. If the download stalls, here’s how to update your iPhone and fix a stuck update.
How to Tell If You Were Exposed
A visit to an affected site during the Optimizely hack means your browser may have loaded the script. Researchers still don’t know how many visitors were exposed or whether the code successfully took over an iPhone or iPad. Start with when you visited, then think about what you did on the page.
- You visited an affected site. The first infected file appeared around 11.21 p.m. ET on Nov. 15, and the last known infected file was clean by 6.11 p.m. ET on Nov. 16. The timing varied by site, so treat that as the overall window.
- A page kept reloading on your iPhone or iPad. On version 18.6 or earlier, the malicious script could reload the page every 60 seconds to retry the exploit. A repeating reload fits that behavior, though it can’t tell you whether an attempt worked.
- You entered card details. If you paid through the site’s own checkout fields after the skimmer was added at 8.43 a.m. ET on Nov. 16, the script could have read your card details. Payment boxes hosted by Stripe or Adyen were out of reach.
- You copied or pasted a crypto wallet address. The script could replace the address on the page or in your clipboard, so the address you pasted could have belonged to the attackers.
What You Can Do Right Now
Start with the software update, then check what you entered or sent on an affected site. If you made a payment, signed in, or sent crypto, the steps below show you what to check for each.
- Update your iPhone and iPad. Tap General > Software Update and install the newest version your device offers. Then open Automatic Updates and turn on automatic installation. You can check which releases apply to your model on Apple’s security releases page.
- Turn on Lockdown Mode if you can’t update yet. If your device offers the feature, open Privacy & Security > Lockdown Mode and tap Turn On Lockdown Mode. Apple says it blocks the web attacks covered by its spring advisory even on older software.
- Keep Safari’s Safe Browsing on. Apple enables it by default and says it blocks the malicious domains the company identified in those spring attacks.
- Review your card activity from Nov. 16 onward. Call your card issuer if you see a charge you don’t recognize. If you paid through an affected site’s own form, ask whether you should replace the card. You can also follow the card checks we covered after the Revolve data breach.
- Check sensitive accounts you used that day. Sign out of any sensitive account you used on an affected site, then sign back in. Review recent activity and change your password if you spot anything unusual.
- Verify any crypto transfer you made on Nov. 16. Compare the destination in your transaction history with the wallet address you intended to pay.
How Optimizely and Salesforce Responded
Optimizely says it fixed the signup flaw and removed the code from affected projects. Salesforce took action on its own sites too. If you’re waiting to hear whether your data was accessed, here’s what the companies have confirmed so far.
Optimizely says it ended ongoing sessions, invalidated tokens, and reset access to the accounts involved. The company says it contacted affected customers and will share relevant developments on its status page, where you can follow the investigation.
Salesforce told BleepingComputer it was making sure Optimizely scripts were disabled on both preview and live sites. It said it would notify affected customers if it found anyone had accessed their data without permission. How the attackers gained access to unrelated projects, how many visitors encountered the code, and how many cards the script captured are still open questions.
Why the Attack Was Hard to Spot
You could type the right web address and land on the page you meant to visit. The page could still load a tampered file from a domain it already trusted. Whether the attack code could run from there depended in part on the rules each site gave your browser.
Report URI examined 256 of the affected organizations’ web hosts and found 24 where site rules blocked the malicious code. At HSBC, the rules blocked the external file, yet a copy embedded in the script could still run. The details of what the browser was allowed to load and run mattered even after a site blocked the attacker’s domain.
The Bottom Line
If you visited an affected site, install the newest update your iPhone or iPad offers. If you typed your card into the site’s own checkout form, watch your statement too. That payment check still matters when your device already has the fixes for the known iPhone exploits.
The Optimizely hack shows how a site you trust can load code you never expected. Here, opening the page was enough to trigger an exploit attempt on vulnerable versions. If you ran a command after a page asked you to verify you were human, follow our guide on what to do after a fake CAPTCHA scam.
FAQs
The attackers gained access through Optimizely, and the brands’ own servers were untouched. The affected pages pulled in the malicious code through a script they already used for website testing.
Yes, a page visit alone could trigger an exploit attempt on a vulnerable iOS version. The script loaded in a hidden part of the page, so you could encounter it without tapping anything. Whether any of those attempts succeeded in the Nov. 16 attack is still unknown.
Install the newest version your device offers. Apple’s Nov. 9 releases were iOS 27.2.1, iOS 26.7.3, and iOS 18.7.12, depending on your model. If your device still runs iOS 15 or 16, look for iOS 15.8.8 or 16.7.16, respectively.
Researchers observed only device fingerprinting on iOS 26, and iOS 27 was outside the reported targets. The attack kit treated iOS 26.3 and later as patched, so install iOS 26.7.3 or the latest iOS 27 release your device offers.
Check your statement and ask your issuer about a replacement if you paid through the site’s own checkout fields. Call your issuer if you spot an unfamiliar charge. The script could read card details from fields run by the site, while payment boxes hosted by Stripe or Adyen were beyond its reach.
Check the address in your browsing history against the domains Report URI and BleepingComputer identified. Report URI could check only the scripts it found, so a missing name gives you limited information. If you’re unsure about a site where you shopped or signed in that day, review your card or account activity.

