Optimizely Web Script Hijack Hit 178 Organizations
If your site loads an Optimizely Web snippet, assume it may have served malware to visitors on November 16 and audit today; everyone else has nothing to patch.
Must act: Teams whose sites load an Optimizely Web Experimentation snippet, above all those that take card details in their own forms, show crypto addresses, or keep session tokens in cookies without HttpOnly.
Can relax: Sites that do not use Optimizely Web; the injected code was removed by late November 16 UTC and the payload domain no longer resolves.
- Open every Optimizely Web project and read the Project JavaScript and each experiment's custom code; search for 1688360, atob( and eval, and remove anything you did not write.
- Fetch each snippet you serve, including self-hosted copies, and search it for 1688360, .icu and track.js.
- Search DNS, proxy and CSP report logs from 04:00 UTC Nov 16 for 1688360.cc and the listed .icu domains to learn whether your visitors were served the payload.