Back to all lessons
Awareness Lessons
4 days ago

Third-Party Script Injection via Optimizely Compromises 178 Organizations

Written by AI from the linked story. Not reviewed by an editor. How this works

An attacker exploited a vulnerability in Optimizely's web experimentation platform to inject malicious JavaScript into the websites of 178 customer organizations, including major media and financial firms. Because these organizations trusted and loaded Optimizely's scripts directly into their pages, a single compromised platform became a force-multiplier for credential theft, payment card skimming, and crypto theft. This is a classic supply chain attack: the victims did not introduce the vulnerability themselves, but their users paid the price. Organizations that rely on third-party JavaScript must treat those dependencies as a potential attack surface and monitor them accordingly.

Tactical Insight

Immediate actions

  • Audit all third-party JavaScript dependencies currently loaded on customer-facing web properties and remove any that are not strictly necessary.
  • Implement Subresource Integrity (SRI) hashes for all externally hosted scripts so browsers reject tampered versions.
  • Deploy a Content Security Policy (CSP) that restricts which scripts and domains are permitted to execute on your pages.

Long-term improvements

  • Establish a formal third-party vendor risk management process that includes security assessments and contractual breach-notification requirements.
  • Continuously monitor external scripts loaded on your sites for unexpected changes using automated diffing or client-side security tooling.
  • Maintain a real-time software inventory (including third-party SaaS dependencies) so affected assets can be identified immediately when a vendor incident is disclosed.

Detection measures

  • Enable browser-side telemetry and anomaly alerting to detect unexpected outbound data flows (e.g., to unknown cryptocurrency or exfiltration endpoints).
  • Subscribe to threat intelligence feeds and vendor security advisories so your team is alerted to compromise events affecting suppliers without delay.
  • Review web application firewall and CDN logs regularly for signs of unauthorized script modifications or suspicious payload delivery.

Back this up with a control

All controls and vendors

Training helps people spot this. These controls make the attack fail even on the day someone does not.