CVEHit Business Advisory by IntegrityLab.ai
What’s the evidence?
Optimizely Web Experimentation JavaScript incident: Business Triage
The reported incident
- 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.
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.
Sources and vendor guidance
← Back to article questions