Optimizely Web Experimentation Supply Chain Attack Affecting 178 Organizations Worldwide
Components Affected
- Websites and web applications using Optimizely Web Experimentation with affected Project JavaScript configurations.
- Public-facing websites and online portals loading compromised Optimizely JavaScript snippets.
- Web pages containing payment forms, cryptocurrency transactions, authentication sessions or sensitive information.
- Visitors accessing affected websites during the malicious script exposure window.
- Potentially vulnerable iPhone and iPad devices exposed to malicious exploit-kit delivery attempts.
Overview
On 16 November 2026, a significant software supply chain security incident was identified involving the Optimizely Web Experimentation platform, a service widely used for website optimization, personalization and A/B testing.
According to independent research by Report URI, malicious JavaScript was identified in 188 Optimizely scripts associated with 178 organizations worldwide, including major financial, technology, media and other service providers.
Optimizely confirmed that an unauthorized party exploited a vulnerability in its Web Experimentation account signup process to impersonate customer users and modify Project JavaScript in certain customer projects.
The malicious code was subsequently distributed through otherwise legitimate Optimizely website scripts, potentially exposing visitors to unauthorized browser activity and information theft without requiring direct compromise of the affected organizations' web servers.
Optimizely confirmed that the vulnerability was fixed and the injected code removed from affected projects by 22:24 UTC on 16 November 2026.
Important: There is currently no verified evidence in the reviewed reporting establishing that a Sri Lankan Government institution was compromised through this incident. Nevertheless, organizations using affected third-party JavaScript services should conduct precautionary investigations.
Description
The attack exploited a weakness in Optimizely's Web Experimentation account signup workflow. This allowed the attacker to impersonate authorized customer users and insert unauthorized JavaScript into customer project configurations.
When users visited websites loading the affected Optimizely scripts, their browsers could execute the injected malicious code as part of the website's normal functionality.
Security researchers identified the following malicious capabilities:
- Payment Card Skimming: Malicious JavaScript could attempt to collect payment card numbers, expiration dates and security codes entered into accessible payment forms.
- Cryptocurrency Wallet Substitution: The payload could replace legitimate cryptocurrency wallet addresses with attacker-controlled addresses, potentially redirecting payments.
- Browser Information Collection: Under certain conditions, the malicious script could access browser-readable cookies, page content and screenshots, creating potential information disclosure risks.
- iOS Exploit Delivery: Researchers identified attempts to deliver additional exploit-kit content to potentially vulnerable iPhone and iPad devices.
- Trusted Script Abuse: The malicious JavaScript was distributed through a legitimate third-party service, allowing it to appear as trusted website functionality.
The presence of these malicious capabilities does not confirm that every visitor was infected or that all affected organizations experienced successful data theft.
Impact
Successful execution of the malicious JavaScript could result in:
- Unauthorized disclosure of sensitive information.
- Payment card information theft.
- Cryptocurrency transaction manipulation.
- Exposure of browser-readable session information.
- Potential compromise of vulnerable mobile devices.
- Financial losses and fraudulent transactions.
- Reputational damage to affected organizations.
- Compromise of confidentiality and integrity of user data.
Solution / Workarounds
Sri Lanka CERT strongly recommends that organizations implement the following preventive and detective measures.
- Identify Affected Services: Review public-facing websites and web applications to identify the use of Optimizely Web Experimentation and other externally hosted JavaScript services.
- Verify Optimizely Project Integrity: Contact Optimizely to confirm whether organizational accounts or projects were affected. Review Project JavaScript, experiment configurations and historical changes for unauthorized modifications.
- Investigate Security Logs: Examine DNS, proxy, firewall, secure web gateway, EDR and browser security logs for suspicious communications associated with the reported malicious infrastructure.
- Review Sensitive Web Pages: Prioritize websites processing payments, financial transactions, authentication information or other sensitive data.
- Implement Content Security Policy: Configure and regularly review restrictive CSP controls, including script-src, connect-src and frame-src directives. Enable CSP reporting where appropriate.
- Monitor Third-Party JavaScript: Maintain an inventory of external scripts and implement integrity or change monitoring to identify unexpected modifications.
- Update Mobile Devices: Ensure supported iOS and iPadOS devices receive the latest available security updates, particularly where exposure to affected websites is suspected.
- Review Account Security: Investigate suspicious authentication activity. Invalidate affected sessions and rotate credentials where actual exposure is established.
- Preserve Evidence: Retain relevant logs, suspicious script samples, browser artifacts and other forensic evidence before remediation.
- Report Suspected Compromise: Immediately report suspicious activity, validated indicators of compromise, financial fraud or significant exposure to Sri Lanka CERT.
Important: Do not indiscriminately block cdn.optimizely.com, as it is a legitimate service. Its presence alone does not indicate compromise. Security teams should investigate unexpected code and communications with confirmed malicious destinations.
Indicators of Compromise (IOCs)
The following indicators were reported in connection with the campaign. They are provided in defanged format for safe publication and should be validated before use in blocking or detection controls.
Reported Malicious Domains:
1688360[.]ccpay-cloud[.]onlinepay.pay-cloud[.]onlinepay-relay.wordpressadmin001.workers[.]dev5vobauua3ojpklx[.]icueil786npto9u5bq[.]icul7bcsnwc7nzr3uo[.]icuwebshell[.]lollinkforge[.]cc
Suspicious URLs:
hxxps://1688360[.]cc/track.jshxxps://1688360[.]cc/card.phphxxps://1688360[.]cc/hit.phphxxps://5vobauua3ojpklx[.]icu/boot.jshxxps://eil786npto9u5bq[.]icu/boot.jshxxps://webshell[.]lol/get.js
Reported JavaScript Indicators:
window._k7window.__k7bdata-channel-code="02111110"
Additional indicators, including historical infrastructure IP addresses and SHA-256 hashes, are available in Annex A of the Sri Lanka CERT advisory dated 18 November 2026.
Historical IOC matches require further investigation and should not automatically be treated as evidence of successful compromise.
Reference
- Optimizely - Security Incident Initial Report (17 November 2026)
- BleepingComputer - Optimizely Supply Chain Attack
- TechTarget - Optimizely Supply Chain Attack Affecting 178 Organizations
- Reuters - Optimizely Website Supply Chain Incident
Incident Reporting
Organizations identifying suspicious activity, indicators of compromise or evidence of unauthorized access are requested to report the incident to Sri Lanka CERT.
Incident Reporting Portal: https://www.cert.gov.lk/report_incident
Advisory Email: advisory@ncsoc.gov.lk
Sri Lanka CERT Hotline: 101
Telephone: +94 11 269 1692
Disclaimer
The information provided herein is on an "as is" basis, without warranty of any kind. This advisory is based on information available from the vendor, independent security researchers and publicly available sources at the time of publication. The information may be updated as additional findings become available. Organizations should consult official vendor communications and assess the applicability of the recommendations to their respective environments before implementation.