Cookie Consent by Free Privacy Policy Generator

The Optimizely Supply Chain Attack: Lessons for UK Web Operations

Krebs on Security reports that at least 178 high-profile websites — including the BBC, CNN, Equifax, Ledger, and Zoom — served malware to visitors over a 24-hour period following a security compromise involving Optimizely, a widely used platform for website personalisation and A/B testing. Attackers exploited a vulnerability in Optimizely to inject data-stealing malicious code into scripts that were then loaded automatically by any website using the service. The incident is described as a supply chain attack, in which a trusted third-party tool becomes the vehicle for delivering malicious content to end users at scale, without the affected websites themselves being directly compromised.

Why this matters for UK organisations

This type of attack — sometimes referred to as web skimming or a Magecart-style compromise — is particularly difficult to detect and defend against because the malicious code originates from a trusted, legitimate third-party source. Many UK businesses embed a range of third-party JavaScript tools into their websites for analytics, personalisation, advertising, and customer experience purposes, often with limited ongoing visibility into what those scripts are doing or what data they are accessing. When one of those providers is compromised, every website loading their scripts becomes an unwitting participant in the attack. The BBC's inclusion in the list of affected sites underlines that this is not a risk confined to smaller or less security-conscious organisations — it affects any business that relies on third-party web tooling without enforcing strict controls on script behaviour. For UK businesses handling customer data, payment information, or sensitive personal details through their websites, the potential regulatory and reputational consequences of this type of incident are significant.

What to review

Organisations should conduct an audit of the third-party scripts currently loaded on their customer-facing websites, assessing which are necessary, who manages them, and what access they have to page content and user data. Implementing or strengthening a Content Security Policy is one of the most effective technical controls available to limit the damage from this type of compromise, as it can restrict which sources are permitted to execute scripts on your pages. Organisations using Optimizely should review vendor communications regarding the incident and assess whether their site was affected during the compromise window. More broadly, this incident is a prompt to ensure that third-party web supply chain risk is included in your organisation's security review processes and vendor risk assessments.

Source: Krebs on Security

News and blog posts
Five critical vulnerabilities have been identified in NGINX, the open-source...
The maintainers of the PHP programming language issued a security advisory this...
Krebs on Security reports that at least 178 high-profile websites — including...
The National Cyber Security Centre published a blog post on 17 November 2026...