Security AlertsThu, 19 Nov 2026
Optimizely website script compromise: investigate payment pages and third-party code
Malicious JavaScript was inserted into some Optimizely Web Experimentation projects. Identify affected pages, preserve evidence and assess visitor exposure.
Article
On 16 November 2026, an attacker exploited a signup-flow flaw in Optimizely Web Experimentation to impersonate customer administrators and modify Project JavaScript in some projects. Visitors loading an affected snippet could execute malicious code in their browsers. This alone does not establish compromise of a website server or visitor device.
Optimizely says it fixed the flaw at 16:10 UTC and removed the injected code from affected projects by 22:24 UTC on 16 November. Its investigation continues. Feature Experimentation, SDKs and legacy Full Stack show no indication of impact. The vendor has not found evidence that customer passwords were used or exposed.
The recovered script targeted payment card details entered directly into on-page forms and cryptocurrency transfers. Hosted third-party payment iframes were outside its reach under the same-origin policy. Actual data theft remains subject to investigation. A second stage attempted to target older iOS and iPadOS versions; an attempt is not proof of device infection.
- 01
Exploit signup flow
- 02
Impersonate user and edit project
- 03
Deliver altered vendor script
- 04
Expose payment and transfer activity
Action: investigate from the external edge to internal assets
- 01
Inventory third-party scripts
Inventory scripts and tag managers across internal and outsourced sites, containers and embedded components; identify pages that actually load them.
See what to doResources: 1
TWISA member solutions
Inventory third-party scripts
Inventory scripts and tag managers across internal and outsourced sites, containers and embedded components; identify pages that actually load them.
- 02
Confirm exposure and preserve evidence
Ask the vendor to confirm affected projects and times; preserve project changes, CDN, WAF, CSP, proxy and payment records.
- 03
Investigate payment and visitor risk
Review on-page forms, wallet substitutions and suspicious requests during the exposure window; assess notification and payment response based on findings.
See what to doResources: 1
TWISA member solutions
Investigate payment and visitor risk
Review on-page forms, wallet substitutions and suspicious requests during the exposure window; assess notification and payment response based on findings.
- 04
Restore and monitor
Restore replaced legitimate code, monitor script changes, enforce an appropriate CSP and retest.
See what to doResources: 1
TWISA member solutions
Restore and monitor
Restore replaced legitimate code, monitor script changes, enforce an appropriate CSP and retest.
Within an authorized scope, perform asset discovery, vulnerability scanning, penetration testing, API testing, attack simulation and retesting. Verify WAF requests, alerts, actual blocking and backend results. Separately validate browser-side script execution with CSP, integrity monitoring and network records; a WAF does not replace the vendor fix or browser-side controls.
Inventory scripts and tag managers across internal and outsourced sites, containers and embedded components; identify pages that actually load them.
Allow authorized traffic and apply controls at each layer.
- 01
Entry and dependencies
Inventory third-party pages
Entry and dependenciesInventory third-party pages
- 02
Browser scripts
Restrict sources and monitor changes
Browser scriptsRestrict sources and monitor changes
- 03
Payments and data
Isolate sensitive inputs and retain evidence
Payments and dataIsolate sensitive inputs and retain evidence
Feed logs and traffic data from each layer into monitoring and response.
- Restore and monitorCorrelate CDN, CSP, payment and website records; investigate and restore.
Inventory third-party scripts
Inventory scripts and tag managers across internal and outsourced sites, containers and embedded components; identify pages that actually load them.
Investigate payment and visitor risk
Review on-page forms, wallet substitutions and suspicious requests during the exposure window; assess notification and payment response based on findings.
Restore and monitor
Restore replaced legitimate code, monitor script changes, enforce an appropriate CSP and retest.
Contact TWISA members for more information about their products and services.
Alert updated: 2026/11/19. Refer to the vendor for current product support and remediation status.