Data breachesBreach alert
Optimizely data breach: what was exposed and what to do
An Optimizely security incident exposed website visitors to payment-card theft and malware. Here's what happened, who's affected, and what to do now.
Written with AI: researched and drafted by our automated newsroom, with every claim checked against the sources linked below and every quote checked word for word, and read by Oliver Madsen on 18 November 2026. How we work
In short: On November 16, 2026, an unauthorized party exploited a vulnerability in Optimizely's Experimentation platform and injected malicious JavaScript into projects run by 178 organizations, according to Report URI's investigation. The code targeted payment cards, cryptocurrency wallets and Apple devices on affected websites, not Optimizely's own customer database. Optimizely says it has fixed the vulnerability, removed the injected code and secured affected accounts, per its status page.
This was a supply-chain attack: the malicious code ran inside pages built by Optimizely's experimentation tool, which many large companies use to test versions of their websites. If you never visited an affected site, this breach doesn't touch you directly. If you did, here's what's known, what isn't, and what to do.
What was exposed in the Optimizely breach?
Malicious JavaScript was served to visitors of 178 organizations through the Optimizely Web platform on November 16, 2026, according to Report URI's analysis, which examined 1,611 Optimizely scripts and found 188 infected ones. The code was a "multi-purpose kit" that swapped cryptocurrency wallet addresses for the attacker's own, skimmed payment cards, stole cookies and screenshots, and on iPhones and iPads delivered the Coruna and DarkSword iOS exploit kits, per the same report. Report URI says crypto has already been stolen, with verified transactions to the attacker's wallets.
Cards typed directly into a site's own checkout form were vulnerable to the skimmer. Cards entered into hosted payment iframes, such as Stripe or Adyen, were "out of its reach," Report URI notes. SecurityWeek reports that a security firm cautioned the evidence shows a connection to exploit-kit delivery infrastructure, but does not establish that any iOS device was successfully exploited.
Who was affected by the Optimizely security incident?
Names on Report URI's list include Zoom, the BBC, CNN, Salesforce, GitLab, IKEA, HSBC, Equifax, Air France-KLM, Ledger and Peacock, per its writeup. SecurityWeek cites the same organizations. These are examples from a list of 178 affected organizations; we have not independently verified the full list.
As of 19:25 UTC on November 16, the attacker's wallets had received about $7,040 in stolen cryptocurrency, all within roughly nine hours that day, Report URI found. By 21:52 UTC the same day, only one of the 188 infected snippets was still infected, down from 169 at 20:56 UTC — meaning most sites had already been cleaned within hours.
Is Optimizely customer data compromised, or only visitors?
The attack targeted website visitors, not Optimizely's customer account database directly. Optimizely's own status page says "an unauthorized party exploited a vulnerability in Experimentation and used it to add malicious JavaScript to some customer projects," and that the company has "fixed the vulnerability and removed the injected code from affected projects," as well as taken steps to secure affected user accounts. SecurityWeek adds that Optimizely "has not said how many customers were impacted."
So there are three groups: people who visited an affected site and entered payment or wallet details, Optimizely customer accounts that may have been affected, and everyone else, who isn't implicated by this incident.
What should I do if I visited a site using Optimizely?
The risk is concentrated: card details typed into checkout forms, session cookies and screenshots from pages visitors were on, and crypto wallet transfers. Work through the list below in that order.
- Check recent bank and card statements for charges you don't recognize, especially on cards you typed directly into a checkout form on a major site in mid-November 2026. See our guide on what to do if your bank card details were leaked for the full process.
- If you entered card details on one of the named sites around November 16, contact your bank or card issuer to discuss a replacement card or fraud alert.
- Change passwords on any account tied to a site you used that day, particularly if you reused that password elsewhere.
- Watch for phishing emails or texts referencing the sites you visited or purchases you made — attacks like this often trigger a wave of follow-up scams. Our guide to spotting phishing after a data breach covers the common patterns.
- If you hold cryptocurrency and interacted with a wallet-connected site that day, check your transaction history for unauthorized transfers.
- Keep an eye on Optimizely's status page for updates, and on your iPhone or iPad, install any pending iOS security updates given the exploit kits involved.
- For a broader run-through of what to do after any breach, see our data breach checklist.
How did attackers compromise Optimizely?
This isn't known yet, and Optimizely hasn't said. Report URI, which investigated the incident, put it plainly: "We don't know how the attacker got write access to so many unrelated customer projects: a compromised Optimizely system, a compromised credential with cross-customer access, or something else. That's for Optimizely to explain," according to its report. The attacker's identity hasn't been confirmed. The exact number of compromised payment cards, crypto wallets or customer accounts also remains unknown.
SecurityWeek notes that Optimizely disclosed a separate, earlier incident in February 2026, when a threat actor accessed its systems through a voice-phishing attack. Whether that earlier incident is connected to this one hasn't been established in the available reporting.
This breach on the data breach tracker: every source, what changed and what to do →
Sources
- Report URI's investigation blog.report-uri.com
- status page status.optimizely.com
- SecurityWeek reports securityweek.com