The Optimizely hack shows how one trusted supplier can put millions of ordinary website visitors at risk. On Monday 16 November 2026, visitors to the websites of at least 178 organisations, including the BBC, CNN, Zoom, HSBC, Salesforce, GitLab, IKEA, Equifax and Air France-KLM, were served malicious JavaScript planted inside Optimizely Web Experimentation scripts. The organisations themselves were not hacked in the usual sense. An attacker got into Optimizely, a platform used to test website layouts, and changed the small piece of code that customer websites load on every page. Because that code came from Optimizely’s own domain, cdn.optimizely.com, with a valid certificate, browsers treated it as legitimate, and it ran for about 17 hours.
Security researcher Scott Helme, founder of Report URI, found the attack on 16 November. His team checked 1,611 Optimizely snippets and found malicious code in 188 of them, belonging to 178 organisations. The story was reported the same day by The Hacker News and by Reuters, whose reporting was carried by the Indian Express. Researchers have named the campaign OPTIMJACK.
What Happened in the Optimizely Hack
Optimizely lets companies test different versions of a web page. A customer website loads a small Optimizely script, called a snippet, from Optimizely’s servers, and it runs on every page. Customers can also add custom code in a field called Project JavaScript.
The attacker wrote a loader into that Project JavaScript field and left the rest of each snippet untouched. Every page that loaded an infected snippet also ran the loader, so visitors only needed to visit a normal website to be exposed. The first injection was seen at 04:21 UTC on 16 November, in the BBC’s snippet. By 21:52 UTC, Report URI found the code in only one script, belonging to TalkTalk. Optimizely posted its incident notice at 01:02 UTC on 17 November.
How the Attackers Got In
Optimizely confirmed that the attacker exploited a flaw in the Experimentation account signup flow to add malicious JavaScript to customer projects. It has not yet explained how a signup flaw gave an outsider write access to existing projects.
That suggests this was part of a wider campaign against third party scripts, the small pieces of code websites borrow from outside suppliers. When one supplier is compromised, every website that trusts it is affected at once. For background on why this pattern keeps repeating, see our guide to the biggest cybersecurity threats to watch in 2027.
What the Malicious Code Did to Visitors
Most infected snippets loaded a file called track.js from the attacker’s domain, 1688360.cc. One version hid that address in base64 encoding, and another carried a full copy of the payload, so it would still run if the domain was blocked.
The first job was crypto theft. The code searched page text, forms, links, the clipboard and outgoing requests for valid Bitcoin, Ethereum and other wallet addresses, and replaced them with addresses controlled by the attacker. Report URI estimated that about 7,040 US dollars reached the attacker’s wallets by 19:25 UTC on 16 November. StepSecurity put the figure at about 6,600 dollars. The true loss is still unknown.
The second job was card skimming. At 13:43 UTC on 16 November, the attacker added code that watched form submissions for card numbers, expiry dates and security codes. It could not read details typed into payment fields hosted inside third party iframes, such as those from Stripe or Adyen. It could read details typed into a site’s own form fields. The code also stole cookies and took screenshots of pages, according to Report URI.

The iOS Exploit Kits: Coruna and DarkSword
On iPhones and iPads, the code loaded a script called boot.js, which checked the iOS version and tried to load an exploit kit in a hidden iframe. Report URI identified Coruna for iOS 13 to 17 and DarkSword for iOS 18.
No iPhone takeover has been confirmed. Cynet described what it saw as conditional delivery, not a compromise of a physical device, and The Hacker News reached the same conclusion. The kit’s own comments marked iOS 18.7.3 and later, and iOS 26.3 and later, as patched, so update if you are on an older version.
Who Was Affected, and What to Do Now
Report URI’s list also includes Salesforce, GitLab, IKEA, Equifax, Air France-KLM, Ledger and PokerStars, and the real total is likely higher. Being on the list means the website served the malicious code. It does not mean the organisation’s own systems were breached.
If you visited an affected website on 16 November, update your iPhone or iPad to iOS 18.7.3 or later, or to iOS 26.3 or later. Check bank and card statements for any payment you do not recognise. If you typed card details into a site’s own payment form that day, ask your bank about a replacement card. If you sent cryptocurrency, check the destination address. Change passwords for important accounts if you logged in on an affected site, and turn on two factor authentication, as our guide on how to create a strong password explains.
Website owners should audit every third party script their site loads, and remove scripts they no longer use. For more on how AI infrastructure can become a target in the same way, see our report on the Fireworks AI breach and Notion chat transcripts.

FAQs
What was the Optimizely hack?
On 16 November 2026, an attacker exploited a flaw in Optimizely Web Experimentation and planted malicious JavaScript in customer projects. Visitors to at least 178 organisations were served the code.
Which websites were affected by the Optimizely hack?
Report URI found 188 infected snippets belonging to 178 organisations, including the BBC, CNN, Fox News, Zoom, HSBC, Salesforce, GitLab, IKEA, Equifax, Air France-KLM and Ledger.
Did the Optimizely hack steal credit card details?
The code added a card skimmer at 13:43 UTC on 16 November for details typed into a site’s own form fields. It could not read details in hosted frames from Stripe or Adyen.
Did the Optimizely hack steal cryptocurrency?
Yes. The code replaced crypto wallet addresses with the attacker’s own addresses. Report URI estimated about 7,040 US dollars reached the attacker’s wallets by 19:25 UTC on 16 November.
Were iPhones actually hacked in the Optimizely attack?
No iPhone takeover has been confirmed. The code tried to load the Coruna and DarkSword exploit kits, but researchers found no evidence of a device being taken over.
Which iOS versions are safe from the Optimizely exploit kits?
The kits’ own comments mark iOS 18.7.3 and later, and iOS 26.3 and later, as patched. Update your iPhone or iPad to one of those versions or later.
Is the Optimizely hack over now?
Optimizely said on 17 November that the flaw was blocked, the code was removed, and affected accounts were secured.
I visited the BBC or Zoom on 16 November. What should I do?
Update your devices, check bank and card statements for unfamiliar payments, check any crypto transfer destination address, and change important passwords if you logged in that day.
#optimizelyhack #optimjack #supplychainattack #cardskimmer #iosexploit #cybersecuritynews
One Response