
A website does not necessarily have to be compromised for its visitors to become victims of a cyberattack.
The November 2026 security incident involving Optimizely demonstrates exactly how this can happen.
Optimizely, a digital experience and web experimentation platform, experienced a security incident in which attackers injected malicious JavaScript into customer projects. These scripts were subsequently delivered to visitors through legitimate Optimizely infrastructure.
Security researcher Scott Helme identified 188 infected JavaScript snippets associated with 178 organisations during his investigation.
The affected websites included those associated with BBC, CNN, Zoom, Salesforce, GitLab, IKEA, HSBC, Equifax and Air France-KLM.
Importantly, the presence of malicious scripts on these websites does not establish that their underlying infrastructure was compromised.
How the attack happened
Optimizely Web Experimentation enables organisations to modify website experiences and conduct experiments through embedded JavaScript snippets.
Attackers exploited a vulnerability in Optimizely’s Experimentation account signup flow, gaining unauthorised access that allowed malicious JavaScript to be injected into customer projects.
The compromised scripts were then served through Optimizely’s legitimate delivery infrastructure.
This meant that visitors accessing affected websites could unknowingly execute attacker-controlled code within their browsers.
The attack did not require the attackers to independently compromise every customer website.
What could the malicious code do?
The investigation identified several malicious capabilities within the injected JavaScript.
Cryptocurrency theft: The code could replace legitimate cryptocurrency wallet addresses with attacker-controlled addresses, potentially redirecting transactions.
Payment card skimming: It contained functionality to capture payment card information entered into affected website forms.
Browser information theft: The malware attempted to collect cookies accessible to JavaScript and capture screenshots of webpages.
iOS exploitation: Researchers identified attempts to deliver the Coruna and DarkSword exploit kits targeting Apple devices.
These capabilities indicate the potential exposure of financial information, browser sessions and end-user devices. However, successful compromise of every visitor has not been established.
Scale and financial impact
Scott Helme’s investigation identified 188 infected snippets across 178 organisations after examining 1,611 scripts.
The investigation also identified approximately US$7,000 in cryptocurrency transactions reaching attacker-controlled wallets.
These figures provide an indication of the observed activity, not the complete financial impact or the number of successfully compromised users.
Optimizely’s response
Optimizely acknowledged the incident and reported that it had:
- Fixed the vulnerable signup flow.
- Removed malicious code from affected customer projects.
- Secured affected accounts and access.
- Introduced additional protections against unauthorised code injection.
The incident highlights the importance of validating customer project integrity following a vendor-side security compromise.
What enterprises should do
Organisations using Optimizely and similar third-party JavaScript platforms should prioritise the following actions:
- Identify all applications and websites integrating the affected scripts.
- Validate project-level JavaScript and experiment configurations against known-good versions.
- Review browser telemetry, proxy logs and outbound connections for indicators of compromise.
- Assess potential exposure of payment information, cookies and active sessions.
- Revoke potentially exposed tokens and invalidate affected sessions.
- Review Content Security Policy and Subresource Integrity controls where applicable.
- Establish an immediate mechanism to disable compromised third-party integrations.
The bigger security lesson
Enterprise security programmes traditionally concentrate on protecting infrastructure, endpoints, applications and cloud environments. However, third-party code executing within customer browsers can introduce an equally significant exposure.
A vendor may operate outside the enterprise’s infrastructure, but its services can become deeply embedded within the enterprise’s digital environment.
This is where third-party risk management needs to mature. Vendor assessments and contractual security commitments are not sufficient without continuous validation of the software components and services integrated into enterprise applications.
The Optimizely incident reinforces a fundamental security principle:
You do not always need to breach an organisation’s infrastructure to compromise its customers. Sometimes, compromising a trusted service is enough.


