Optimizely Supply Chain Attack Hits 178 Organisations Through Malicious JavaScript
Nov 18, 2026
Overview
A major software supply chain attack targeting Optimizely Web Experimentation exposed visitors of websites belonging to 178 organisations to malicious JavaScript on November 16, 2026. The attack affected websites associated with prominent global brands, including BBC, CNN, Zoom, Salesforce, HSBC, IKEA, GitLab and Equifax.
Attackers exploited a vulnerability in Optimizely's Web Experimentation account signup process to inject malicious JavaScript into customer projects. The compromised code was then distributed through Optimizely's legitimate content delivery infrastructure, allowing it to execute in visitors' browsers without requiring attackers to directly breach each affected organisation's internal network.
The malicious scripts were designed to steal cryptocurrency by replacing legitimate wallet addresses, capture payment card information, collect browser cookies and screenshots, and deliver iOS exploit kits targeting Apple devices. Security researchers also confirmed that cryptocurrency transactions had been redirected to attacker-controlled wallets.
Optimizely has since fixed the vulnerability, removed the injected code from affected projects and implemented additional security protections. However, the incident highlights the growing risks associated with third-party JavaScript integrations and the security challenges organisations face when relying on external software providers.
Key Facts of the Incident
Category | Details |
|---|---|
Threat Type | Software supply chain attack and malicious JavaScript injection |
Affected Platform | Optimizely Web Experimentation |
Attack Date | November 16, 2026 |
Organisations Affected | 178 organisations identified |
Infected Scripts | 188 infected snippets identified among 1,611 analysed |
Attack Vector | Exploitation of an account signup vulnerability to inject malicious JavaScript |
Targeted Information | Payment card details, cryptocurrency transactions, browser cookies and screenshots |
Malware Capabilities | Cryptocurrency wallet replacement, payment card skimming and iOS exploit delivery |
Notable Organisations | BBC, CNN, Zoom, Salesforce, HSBC, IKEA, GitLab and Equifax |
Vendor Response | Vulnerability fixed, malicious code removed, sessions terminated and access tokens revoked |
Current Status | Contained and remediated; forensic investigation ongoing |
What Happened?
On November 16, 2026, attackers exploited a security vulnerability in Optimizely Web Experimentation, a platform that businesses use to experiment with website layouts, personalise content and optimise digital experiences.
The platform works by allowing customers to integrate JavaScript snippets into their websites. These snippets are delivered through Optimizely's content delivery network (CDN) and can include an optional feature called Project JavaScript, which allows customers to insert custom scripts through the Optimizely dashboard.
Attackers exploited a vulnerability in the platform's account signup flow to impersonate users and gain access to customer projects. They then inserted malicious JavaScript into the Project JavaScript sections of multiple accounts.
The modified snippets continued to operate through Optimizely's legitimate CDN and security certificate. Consequently, browsers continued to load the scripts from a trusted source, making the malicious activity difficult to distinguish from normal website operations.
An investigation identified 188 infected JavaScript snippets associated with 178 organisations out of 1,611 snippets examined.
The affected websites included several major international organisations:
Media: BBC and CNN.
Technology: Zoom, Salesforce and GitLab.
Financial Services: HSBC and Equifax.
Retail and Consumer Services: IKEA.
Travel and Other Services: Air France-KLM, Ledger and Peacock.
The incident did not mean that all 178 organisations had their internal networks breached. Instead, malicious code was introduced through a shared third-party platform and executed in the browsers of visitors accessing affected webpages.
How the Malicious JavaScript Worked
The injected JavaScript acted as a multi-purpose malicious payload, carrying out several activities designed to steal financial information and compromise website visitors.
1. Cryptocurrency Wallet Replacement
One of the primary functions of the malicious script was to interfere with cryptocurrency transactions.
When visitors attempted to make cryptocurrency payments or transfers, the script attempted to replace legitimate wallet addresses with addresses controlled by the attackers.
As a result, users could unknowingly transfer their cryptocurrency directly to attacker-controlled wallets instead of the intended recipients.
Security researchers reported confirmed cryptocurrency theft associated with the campaign.
2. Payment Card Information Theft
The malicious JavaScript was also designed to capture payment card information entered by visitors on affected websites.
The script targeted card details entered directly into websites' own payment forms. This created a potential risk for users making purchases or submitting payment information while visiting compromised pages.
However, payment fields hosted inside separate payment provider frames, including Stripe and Adyen, were not accessible to the malicious script.
3. Browser Cookie and Screenshot Collection
The attack also involved code designed to collect website cookies and capture screenshots of visitors' browser activity.
Stolen cookies can potentially expose information associated with active website sessions, depending on their security attributes and the level of access available to attackers.
Screenshots could provide additional visibility into the information displayed on a victim's screen, potentially exposing sensitive details entered or viewed during a browsing session.
4. iOS Exploit Kit Deployment
Another concerning aspect was the attempted delivery of two iOS exploit kits, known as Coruna and DarkSword.
These exploit frameworks targeted Apple devices, including iPhones and iPads, potentially exposing visitors running vulnerable software to additional exploitation.
Apple stated that the underlying vulnerabilities targeted by these tools had already been fixed in previous software updates. Users running updated versions of iOS were therefore protected against the known vulnerabilities.
Optimizely's Response to the Incident
Optimizely acknowledged the security incident and confirmed that an unauthorised third party had exploited a vulnerability in its Web Experimentation account signup flow.
The company clarified that the incident did not result from a compromised administrator account or the theft of customer passwords. Instead, attackers exploited a flaw that allowed them to impersonate users and modify customer projects.
According to the company's initial incident report, the response included several actions:
Vulnerability Remediation: The security flaw was addressed on November 16, 2026.
Session Termination: Active sessions associated with impersonated accounts were terminated.
Token Revocation: Access tokens were revoked to prevent continued unauthorised access.
Malicious Code Removal: Injected JavaScript was removed from all affected customer projects by 22:24 UTC on November 16.
Additional Security Protections: Measures were implemented to prevent unauthorised code from being delivered through the platform.
Optimizely also engaged Mandiant, a third-party cybersecurity investigation firm, to examine the incident and assist with its forensic investigation.
The company confirmed that only Web Experimentation was involved. Other products, including Feature Experimentation, SDKs and legacy Full Stack, were not affected based on its initial findings.
Affected customers were also advised to review their website activity during the exposure window and contact their respective customer success representatives for details about their individual exposure.
Immediate Impact and Risks
The incident demonstrates how a vulnerability in a single third-party service can create security risks across hundreds of organisations.
Some of the key concerns include:
Third-Party Supply Chain Exposure: Organisations relying on Optimizely's JavaScript integrations unknowingly delivered malicious code to website visitors.
Financial Fraud: Cryptocurrency wallet replacement and payment card skimming created opportunities for direct financial theft.
Customer Data Exposure: Browser cookies and screenshots could expose sensitive information associated with website visitors.
Mobile Device Security: Attempts to deploy iOS exploit kits introduced additional risks for users operating vulnerable Apple devices.
Detection Challenges: Malicious scripts were delivered through Optimizely's legitimate infrastructure, making traditional domain-based security controls less effective.
Several affected organisations initiated investigations and disabled their Optimizely integrations as a precaution. Salesforce and Zoom temporarily disabled the platform's scripts, while Equifax stopped using the service. Equifax and Zoom stated that they had not identified evidence of compromise affecting their internal systems or customer data. HSBC also stated that unauthorised scripts were not active on its websites.
Although the malicious code was removed, the exact number of affected website visitors and the total amount of information potentially exposed have not been publicly established.
What Organisations Should Do
The Optimizely incident highlights the importance of monitoring third-party scripts and identifying suspicious changes to website components.
Organisations should consider the following security measures:
1. Audit Third-Party JavaScript Integrations
Maintain an inventory of all external scripts running on company websites. Regularly review integrations used for analytics, marketing, personalisation, payment processing and customer engagement.
Remove unnecessary integrations and ensure every third-party script has a clearly defined business purpose.
2. Implement Content Security Policies
Deploy a strong Content Security Policy (CSP) to control which scripts can execute and where browser data can be transmitted.
CSP configurations should be regularly reviewed and tested to identify unauthorised script execution and unexpected external connections.
3. Monitor Changes to Website Scripts
Implement continuous monitoring to detect unexpected modifications to trusted JavaScript files.
Security teams should investigate unusual changes to third-party scripts, newly introduced external connections and suspicious browser activity.
4. Restrict Access to Third-Party Platforms
Limit administrative access to platforms that allow external code execution.
Implement role-based access controls, regularly review user permissions and require additional approval before custom JavaScript is deployed to production websites.
5. Review Payment and Website Activity
Organisations that may have been affected should review website logs, payment activity, cryptocurrency transactions and browser security reports from the exposure period.
They should also assess whether sensitive payment information or customer sessions may have been exposed and take appropriate incident response measures.
6. Strengthen Security Awareness
Employees responsible for website management, marketing integrations and digital operations should understand the security implications of third-party services.
Regular cybersecurity awareness initiatives can help teams recognise suspicious platform activity, unauthorised changes and potential supply chain threats before they develop into larger incidents.
Why This Matters?
The Optimizely supply chain attack highlights an important weakness in modern website security: protecting an organisation's own infrastructure is not enough when its websites depend on external services.
Businesses increasingly rely on third-party platforms for website personalisation, analytics, advertising, customer engagement and payment processing. While these integrations improve functionality and operational efficiency, they also introduce additional security dependencies.
In this incident, attackers did not need to independently compromise the internal networks of 178 organisations. By exploiting a vulnerability in a shared platform, they were able to introduce malicious code into customer websites through an already trusted delivery mechanism.
The incident reinforces the need for continuous third-party risk assessments, strict access controls, JavaScript integrity monitoring and effective browser security policies.
For organisations, cybersecurity must extend beyond internal systems to every external service and integration that interacts with customers and sensitive business information. A trusted third-party script can quickly become a security threat when its integrity is compromised.
Disclaimer: ClearPhish maintains a strict policy of not participating in the theft, distribution or handling of stolen data or files. The platform does not engage in exfiltration, downloading, hosting or reposting any illegally obtained information. Any responsibility or legal inquiries regarding the incident should be directed to the relevant organisations and authorities.






