What happened
The change came from the experimentation layer
Optimizely says an unauthorized party exploited a vulnerability in Experimentation and added malicious JavaScript to some customer projects. The company says it fixed the vulnerability and removed the injected code. Its incident notice was still in monitoring when this article was prepared.
Scott Helme examined 1,611 distinct Optimizely snippets and found malicious code in 188 snippets belonging to 178 organizations. That is a count from his sample, not a count of infected visitors or confirmed stolen records. The payload he analyzed attempted several things, including wallet-address substitution, payment-card collection and delivery of iOS exploit loaders. The presence of that code does not establish that each attempt succeeded on each site.
The trusted source is the point
Defender workflow
Check the page that visitors actually received
- 1
Find the dependent pages. Inventory pages loading Optimizely Web Experimentation, especially checkout, sign-in and account pages. Confirm which projects and snippets were active on 16 November.
- 2
Review the script and its history. Compare the project JavaScript and saved snippet copies with expected versions. Preserve suspect responses, timestamps and relevant browser telemetry before rotating or deleting evidence.
- 3
Look for browser-side effects. Review content-security-policy reports, unexpected outbound destinations and payment-page monitoring. Follow Optimizely's customer guidance for the affected projects.
Defender note
Treat third-party code as a changing dependency
Script inventory should record what a browser executed, not just which URL it requested. A restrictive policy and change monitoring can make an injected dependency easier to spot, but the response here starts with reconstructing the pages, visitors and transactions that may have encountered the altered snippet.