Check these three things.
-
Application owner: list sensitive payment and account pages that loaded Optimizely Web Experimentation.
What to confirm
- Include checkout, payment, login and account pages, with the Optimizely project ID each page loads.
- Check tag managers and page templates as well as direct script tags.
- The vendor reports remediation. That does not show which projects were changed earlier.
-
Provider: confirm whether our project IDs and time windows were in scope.
When the risk applies
- The risk applies if a project we use was altered while visitors loaded it on any of our pages. Payment and account pages are the priority for triage. The vendor says only some customer projects were affected.
- Preserve project History and compare it with historical snippets and vendor-confirmed windows. History can be filtered by Type, Date and Source (REST API or UI). Each change record shows its time and collaborator. A missing History entry does not prove no impact.
-
Security owner: review records for unauthorized visitor-side activity and note the gaps.
What the records can show
- Review enforced CSP reports, page-script change records, payment-fraud and chargeback signals, customer reports and relevant web logs for the vendor-confirmed windows.
- A clean response today does not rule out earlier activity. Browser-side activity may leave no server log, so record each gap.
If any of our pages loaded Optimizely, preserve the evidence and get project and time scope confirmed before treating the question as closed.
Do Now
- Security owner: preserve current and historical Optimizely snippets, project History and relevant logs.
What to ask
Keep copies before anyone edits or cleans up projects. Record the date, source and person for each item.
- Provider: ask Optimizely to confirm whether our listed project IDs were affected, and in which time windows.
What to ask
Send the project IDs from the page inventory. Ask for written scope and for any account activity on those projects. Keep the reply as evidence.
- Application owner: decide whether to disable Optimizely on sensitive surfaces until scope is verified.
What to ask
Weigh the loss of experiments against the uncertainty. Coordinate the change with the Security owner and record the decision and date.
Do Next
- Security owner: review whether sensitive pages use an enforced Content Security Policy, not report-only.
What to ask
Blocking one external host alone is not complete protection, because the source describes an embedded payload fallback. Review the whole policy for script sources and where pages can send data.
Check your own records.
- Use your approved AI tool.
- Require evidence. Flag unknowns.
Read the prompt
The reported incident
Malicious JavaScript added to some Optimizely projects
Vendor status →- Required conditions
- Our project must be among those altered. The altered code must have run in a visitor's browser during the affected period.
- Reported outcome
- The vendor says an unauthorized party exploited a vulnerability in Experimentation and added malicious JavaScript to some customer projects. Report URI says it checked 1,611 snippets and found 188 altered, tied to 178 organizations. It reports card-skimming and crypto-address-substitution capabilities. Its earliest archived observation was Nov 16 at 04:21 UTC; that is the earliest observed capture, not a proven start. Report URI says one of the 188 snippets still matched at 21:52 UTC on Nov 16, before the vendor statement. These records do not show which of our visitors ran affected code or suffered loss.
Fix guidance
- Vendor update: monitoring, statement dated 2026-11-17 01:02 UTC (Nov 16, 20:02 Toronto). The vendor reports the vulnerability fixed, injected code removed, affected user accounts secured and added protections.
- No assigned CVE, numeric CVSS, or affected or fixed software version was verified.
- Vendor cleanup and a clean response today do not establish that there was no historical impact.
What IntegrityLab.ai can check
- This brief and public dependency information cannot determine historical customer impact.
- Internal records and vendor confirmation are required. We do not claim that the existing assessor tests for this incident.
- Seeing Optimizely on a page shows only that the dependency is present. It does not show that a project was altered or that visitors were affected.