What the Optimizely hack means for the marketing tags on your website

178 sites served malware without deploying anything: the figures, your UK GDPR duty and what to ask tag vendors

On 16 November 2026 attackers exploited a flaw in Optimizely, a website testing service, and added malicious JavaScript to scripts it hosts. The code ran on 178 organisations' sites, including the BBC, HSBC and IKEA, for up to about 19 hours, trying to steal cards, cryptocurrency and cookies.

In short

  • Report URI found malicious code in 188 of 1,611 Optimizely snippets it checked, belonging to 178 organisations, and expects the true number to be higher.
  • The affected sites deployed nothing: the code was added inside Optimizely, so a tag audit or a cookie consent banner would not have caught it.
  • About $7,000 in cryptocurrency was traced to the attacker, but nobody can yet measure stolen cards, cookies or infected iPhones.
  • Under UK GDPR the website owner remains the controller, so a breach affecting visitors may need reporting to the ICO within 72 hours of becoming aware.
  • Only 24 of the affected organisations had a Content Security Policy that blocked the payload, which makes CSP reporting the cheapest defence to ask for.
Closeup of rows of tiny round white electrical connectors and long thin blue wires in data center
Photo: Brett Sayles on Pexels

The Optimizely hack on 16 November 2026 put malicious code on the websites of 178 organisations, including the BBC, HSBC, IKEA and Zoom, and none of them deployed anything. Attackers wrote it into scripts hosted by Optimizely, a service companies use to test versions of their web pages, and it tried to steal card details, cryptocurrency and cookies from visitors.1

If you run marketing for a UK B2B firm, the lesson is sitting in your own marketing stack, because a tag served from a vendor's servers can change without anyone on your side touching it, while the data protection duty stays with you.

What happened in the Optimizely hack?

Every Optimizely Web customer's site loads a small file, called a snippet, from Optimizely's servers, and it carries that customer's experiments along with an optional box for custom code that runs on every page. On 16 November an attacker wrote a loader into that box across unrelated customer projects, so the file still arrived from Optimizely's own address with its own security certificate.1 Optimizely's status page says an unauthorised party "exploited a vulnerability in Experimentation" and that the flaw is fixed and the code removed.2 The Register reports the hole was in the sign-up process.3

Security people call this a supply chain attack, because breaking into one supplier gets you into all of its customers at once. Nobody at the BBC or Zoom published a change, so if you'd audited your tags that morning you'd have found exactly the tags you found the day before.

Scott Helme of Report URI fetched 1,611 Optimizely snippets and found malicious code in 188 of them, belonging to 178 organisations.1 That's roughly one file in nine, and Helme expects the true count to be higher. StepSecurity, working independently, found the payload itself in public scan records for 17 domains, including the BBC and Zoom.4 The UK names on the list include ASOS, TalkTalk, Funding Circle, the law firm Freshfields and the consultancy Baringa.5

How long was the malicious code live?

It depends who you ask, though the answers aren't far apart. Report URI logged the first injection, on the BBC's snippet, at 04:21 UTC on 16 November, and every file was clean by 23:11.1 That's where the "approximately 19 hours" in Reuters-based coverage comes from.6 StepSecurity puts most sites' exposure at about 16 hours, because it counts from the first public scan that caught a request to the attacker's server.4

Is it still running? According to Report URI, the attacker's main server was suspended by its domain registry at 00:37 UTC on 17 November, and Optimizely's status page lists the incident as "Monitoring".12 What should worry you more, if you look after a marketing stack, is that between 13 and 16 November the same actor's code also went out through three other marketing and content scripts, Kissmetrics, StorifyMe and Minute Media.1

About $7,000 stolen, which is the least useful number

Report URI traced about $7,040 into the attacker's wallets by 19:25 UTC on the 16th, which is the figure Newsweek used.15 Coverage citing the crypto outlet Coinspeaker gives about $7,150.6 The gap is just timing, since Helme's updated table on 17 November adds one more Bitcoin payment and also reaches roughly $7,150.1 Crypto payments are public, so you can trust that number, but it says nothing about cards, cookies or iPhones, which Helme says he can't measure.1

For a B2B site the triggers matter far more than the total. The skimmer read cards typed into a site's own form fields but not those entered in a payment provider's hosted frame, such as Stripe's, and the cookie and screenshot theft only fired when the script swapped a wallet address near payment wording. The iPhone exploit kits were less fussy and went to every visitor on an older version of iOS.1 So a lead generation site with only a contact form had less to lose than ASOS, though its visitors on old iPhones were still targets. If you visited an affected site, update to iOS 18.7.3 or 26.3 or later and keep an eye on your card statements, although simply opening a page doesn't mean anything was stolen.15

Does UK GDPR make you responsible for a vendor's script?

For your visitors' data, yes. The ICO says the controller, meaning the organisation that decides why and how personal data is used, carries the highest level of responsibility and answers for its processors' compliance too.7 You have to report a personal data breach to the ICO without undue delay and, where feasible, within 72 hours.8 That clock starts once you're reasonably certain personal data has been compromised, and you needn't report a breach that's unlikely to put people at risk.9 Processors must tell the controller without undue delay.10 Optimizely says it has notified affected customers.3

If our site were on the list, we'd open a breach log entry today, noting the hours the code was live, which forms and cookies it could read, and whether we take card details in our own fields. That record is how you make the reporting decision, and it's how you defend it later if anyone asks. If your login cookies were readable by page scripts, you've more to think about than most, because Report URI advises treating those session tokens as exposed.1

Your cookie banner wouldn't have helped either. On a GitLab page, StepSecurity found that the consent manager was the very thing that loaded the Optimizely file, which shows it "controls when the script runs, not what the script contains".4 PECR consent gives you permission to set cookies, and it says nothing about what a script does once you've let it in.

Would a Content Security Policy have stopped it?

Content Security Policy, usually shortened to CSP, is a list your site hands the browser naming the servers your pages may load scripts from and send data to. Of the affected organisations Report URI checked, 68 had no CSP at all and only 24, or 15%, blocked the payload.1 Listing Optimizely as trusted did nothing, since the loader came from Optimizely, so what the 24 had in common was a short, specific list of permitted script sources. HSBC's policy stopped the main payload, yet an inline copy still ran because the policy allowed a setting that Optimizely's own documentation tells customers to switch on.1

CSP also has a report-only mode, which breaks nothing and tells you when a page starts loading something new, and that's the kind of monitoring Report URI says would have exposed this attack. Of everything here it's the cheapest thing to ask your developer for, and it's where we'd start.

Subresource Integrity, or SRI, gives the browser a fingerprint of a script and tells it to refuse any version that doesn't match.11 The trouble is that a testing snippet changes whenever your team publishes an experiment, so you can't pin it to one fingerprint.4 Hosting the file on your own domain didn't help either. Scheels and Vodafone Australia did exactly that and were infected anyway, because the content still came from the Optimizely project.1

Questions for every analytics, testing and visitor identification vendor

Equifax has stopped using Optimizely and Salesforce disabled the altered scripts.12 IKEA says it's investigating.6 Most firms won't drop a tool over this, and you probably don't need to, but we'd want these answered in writing by any vendor whose script sits on your pages:

  1. Where is your script served from, and can its content change on our site without anyone here publishing it?
  2. Who can add custom code to it, on your side and ours, and how is that access controlled?
  3. Is there a fixed, versioned build we can fingerprint, and if not, how would we see a change?
  4. Which domains does it load from and send data to, so our CSP can name them?
  5. How quickly would you tell us about a breach, and where does our contract say so?

Scout's tag is a third-party script on your site too, so do ask us the same. Someone on your side has to own the answers, which is why a tag manager needs an owner.

Who was on your website during those hours

When a script goes wrong, GA4 tells you how many sessions landed in the window. Scout connects to GA4 and Search Console and shows you which companies those visits came from, with a confidence score on every match, so you know which clients might want a quiet word. It identifies organisations, never the person. Start a 14-day free trial, no card needed.

Frequently asked questions

Was my website affected by the Optimizely hack?

Only sites using Optimizely Web Experimentation were exposed. Report URI has published the 178 organisations it found, but says the real number is likely higher. If you use Optimizely Web, check every project's custom code box, review who has access to your account and ask Optimizely which of your projects were modified and when.

Do I need to change my card or passwords after the Optimizely hack?

Simply opening an affected page on 16 November doesn't mean anything was stolen. If you typed card details into an affected site that day, watch your statements and contact your bank about any payment you don't recognise. If you use an iPhone or iPad, update to iOS 18.7.3 or 26.3 or later.

Is the Optimizely attack still active?

Report URI found every infected Optimizely file clean by 23:11 UTC on 16 November, and the attacker's main server was suspended early on 17 November. Optimizely says it has fixed the vulnerability and removed the injected code, and its status page lists the incident as being monitored.

Do I have to report the Optimizely hack to the ICO?

If your site was affected and visitors' personal data may have been compromised, you're the controller and must report to the ICO without undue delay and, where feasible, within 72 hours of becoming aware. You needn't report a breach that's unlikely to put people at risk, but you should log your reasoning.

No. StepSecurity found that on one affected GitLab page the consent manager was what loaded the Optimizely file. Consent controls when a script runs, not what the script contains, so the malicious code ran for any visitor who accepted cookies.

Sources

  1. Report URI: World's Largest Brands Infected With Malware Via Optimizely blog.report-uri.com
  2. Optimizely Service Status: Web Experimentation Security Incident status.optimizely.com
  3. The Register: Optimizely hack turns world's biggest websites into malware dispensers theregister.com
  4. StepSecurity: OPTIMJACK, Optimizely-hosted scripts loaded a crypto clipper and card skimmer on 178 organizations stepsecurity.io
  5. Newsweek: Cyber attack hits 178 major websites, full list of organizations newsweek.com
  6. Yahoo News (Mediaite, citing Reuters): CNN, Zoom and IKEA among 178 websites hit by cyberattack yahoo.com
  7. ICO: A guide to controllers and processors ico.org.uk
  8. ICO: Report a breach (all controllers) ico.org.uk
  9. Law Society of Scotland: Reporting personal data breaches lawscot.org.uk
  10. ICO: What does it mean if you are a processor? ico.org.uk
  11. MDN Web Docs: Subresource Integrity developer.mozilla.org
  12. Cybernews: Zoom, IKEA, HSBC among 178 websites infected with hidden malware cybernews.com