The Optimizely Supply Chain Attack: What UK Businesses Should Do Now
Malicious JavaScript reached visitors of 178 organisations through a trusted third party. What the Optimizely supply chain attack means for UK businesses.
The Optimizely supply chain attack is the most significant web security incident of November 2026: on 16 November, malicious JavaScript was served to visitors of 178 organisations through Optimizely's Web experimentation platform, including the BBC, CNN, Zoom, HSBC, Salesforce and Equifax (Report URI, Newsweek). The code skimmed payment cards, swapped cryptocurrency wallet addresses, stole cookies and screenshots, and sent older iPhones and iPads to an exploit kit. If your website, store or internal software loads scripts from a third party, this is a direct lesson in how you buy and manage that risk.
What happened in the Optimizely supply chain attack?
Optimizely Web works by having each customer load a JavaScript "snippet" from Optimizely's content delivery network. That snippet contains a field called Project JavaScript, where customers add their own code. An unauthorised party exploited a vulnerability in the Experimentation platform to write their own code into customer projects (Newsweek).
The file was still served from Optimizely's own domain, over its certificate, from a host every affected site already trusted. Report URI found 186 of 1,611 Optimizely snippets infected in its sweep at 19:24 UTC, with the payload rebuilt 26 times during the day (Report URI).
Optimizely said it fixed the vulnerability and removed the injected code, and that it had blocked the vulnerable path, ended active sessions and revoked tokens. It also said it had added protections to stop malicious code being delivered through Cloudflare (Newsweek).
Why does this matter to UK businesses that rely on websites and software?
Because none of the affected organisations did anything obviously wrong. Their own code was not breached. Their own hosting was not breached. A vendor they trusted was, and that vendor's code ran on every page of their site at once. As the researcher who found it put it: compromise one trusted vendor and its code runs on every customer's website simultaneously (Newsweek).
The same pattern applies to any small business running a marketing tag, a chat widget, an analytics tool, an A/B testing script or a booking embed. Every script you add is a piece of software you have effectively outsourced to someone else and agreed to run on every visit. Few UK SMEs keep a list of those scripts, let alone review them.
There is also a regulatory dimension. If malicious code on your site captures a customer's card details or personal data, you are likely dealing with a personal data breach under UK GDPR, which means assessing it and, where the threshold is met, reporting it to the ICO within 72 hours of becoming aware. Whether the failure sits with you or a supplier, the customer relationship and the notification duty sit with you.
The bigger point is governance. A website is not a finished product. It is a running system with suppliers attached, and it needs the same oversight as any other system in the business. That is what our website and software management service is for: watching what changes, testing that it still works, and keeping patches and third parties under review.
How would you have known?
Most affected organisations found out from a security researcher's blog post. That is not a detection strategy.
Report URI points out that the signals were detectable: unexpected changes to trusted JavaScript, new scripts loading from unfamiliar domains, and suspicious connections to external destinations would have exposed the activity even though the original file came from a trusted domain. A Content Security Policy in enforcement mode could have blocked key parts of the attack before they succeeded (Report URI).
For a UK SME, a realistic version of that looks like this:
- A written inventory of every third-party script on your site, who owns it and what it does.
- A Content Security Policy that restricts where scripts can load from and reports violations.
- Alerting on unexpected changes to the pages and scripts you serve.
- A named person who reviews the inventory at least quarterly and removes anything unused.
None of this is exotic. It is basic hygiene applied to the web layer, and it is the same discipline that sits behind our security monitoring and testing and QA work.
Does Cyber Essentials cover this?
Partly. Cyber Essentials focuses on five technical controls: firewalls, secure configuration, user access control, malware protection and patch management. It asks you to keep software up to date and to remove unnecessary accounts and services, which covers some of the ground here.
What it does not do is guarantee that a trusted supplier will not be compromised, and no certification can. As we have said before, certification shows you have put sensible controls in place; it is not a promise of safety. Varsuite is Cyber Essentials certified, and we still treat every third-party script as a risk to be reviewed rather than trusted.

What should you do now?
If you used Optimizely Web, check your projects today and confirm the injected code has gone. If you did not, this is still a prompt to look at your own dependency chain.
| Action | Who can do it | Why it matters |
|---|---|---|
| List every third-party script on your site | Whoever manages your site | You cannot manage what you have not listed |
| Remove tags nobody uses | Marketing or web owner | Fewer scripts, smaller attack surface |
| Check your Content Security Policy | Your developer or host | Blocks and reports unexpected script loads |
| Review supplier security terms | Operations lead | Confirms who does what if a vendor is breached |
| Record a breach process | Whoever owns data protection | UK GDPR notification is time-bound |
The order matters less than starting. Most UK SMEs will find at least three scripts nobody remembers adding.
Where Varsuite fits
We build websites, stores, custom software and AI agents, and we run a care and management service for the systems we build and for those we inherit. That means a named route for changes to go through, a review of what third parties are doing on your site, and someone to call when a script starts behaving oddly.
We are not the right fit if you have a capable in-house developer who already owns this, or if you are looking for a cheap plugin that promises to scan everything automatically. Care and monitoring work is genuinely ongoing, and we price it that way.
For brochure websites, care starts from £100 per month, and for online stores from £150 per month. A full review of a third-party script estate is best scoped after a short conversation, because the work depends on how much you have and who owns each piece. You can see how we structure this on our pricing page or read more about bespoke business systems if the risk sits in internal tools rather than the public site.
The sensible next step
If you cannot say which third-party scripts run on your website and who put them there, book a short call and we will help you build that list and close the obvious gaps. It is a few hours of work that puts you in a far better position the next time a vendor you rely on has a bad day. Start with our management service or get in touch and tell us what your site runs on.
Frequently asked questions
Was my website affected by the Optimizely supply chain attack?
Only if your site loaded Optimizely Web snippets or scripts that pulled from the same projects. Report URI found 188 infected snippets across 178 organisations (Report URI). If you do not use Optimizely, you were not caught by this specific attack, but the underlying lesson about third-party scripts still applies.
Do I have to report this to the ICO?
Only if personal data was compromised and the breach is likely to result in a risk to people's rights and freedoms. Under UK GDPR, notifiable breaches must be reported to the ICO within 72 hours of becoming aware. Get advice quickly if card data or customer details may have been captured.
How do I stop this happening to my site?
Keep a list of every third-party script, remove the ones you do not use, add a Content Security Policy, and monitor for unexpected changes. No approach removes the risk entirely, because you are still trusting suppliers, but you can detect and often block the damage.
Is Cyber Essentials enough to protect against supply chain attacks?
No. Cyber Essentials covers useful baseline controls around firewalls, configuration, access, malware and patching, but it cannot stop a trusted vendor being compromised. Treat it as a floor, not a ceiling.
Images from Pixabay
Jamie is Technical Director at Varsuite and leads the technical development team, setting how we design and build everything we ship. He builds the AI models that power our agents and manages the AI s...
More from Jamie WoodruffGet The Signal
Practical notes on AI, websites and automation for UK businesses. One useful email at a time, unsubscribe whenever.
Varsuite is an AI-accelerated, human-perfected digital production company based in Rishton, Lancashire. Agents build, people perfect: websites, stores, software and AI automation.
Ready to put AI to work?
Let our agents design, build and manage it for you.