Optimizely Malware Incident Highlights the Hidden Risks of Third-Party Website Scripts

Third-party tools help businesses test website changes, understand visitor behavior and improve conversions. But the scripts powering those tools can also introduce security risks beyond a company’s own website code.

According to a recent analysis published by conversion optimization agency Wavesy, a November 16, 2026 incident involving Optimizely illustrates how malicious code can reach websites through a trusted technology provider.

Drawing on research from Report URI and Optimizely’s public response, the article reports that 188 snippets across 178 organizations were identified as infected. Optimizely said it fixed the vulnerability, removed the injected code, secured affected accounts and notified affected customers.

The incident offers a broader lesson for businesses using third-party website tools: trusting a provider does not eliminate the need to monitor what its scripts do.

How Trusted Scripts Become a Security Risk

The malicious JavaScript was delivered through Optimizely’s own content delivery network. Because affected websites already permitted scripts from that source, the code could run through an established, trusted connection.

Reported capabilities included capturing payment card information entered into website forms, stealing cookies accessible to JavaScript and replacing cryptocurrency wallet addresses. Report URI’s findings indicated that payment fields inside hosted payment iframes were not affected by the card skimmer.

The exposure extends beyond experimentation software. Analytics platforms, chat widgets, review apps and tag managers also introduce code into visitors’ browsers.

What Website Owners Can Do

Wavesy’s analysis highlights several practical priorities for reducing third-party script risk:

  • Know what runs on your website. Maintain an inventory of scripts, their purpose and the pages where they load.
  • Limit access and publishing rights. Review users, integrations and API tokens, remove outdated access and enable strong authentication.
  • Reduce exposure on sensitive pages. Review whether testing and marketing scripts need to run on checkout and account pages.
  • Control outgoing connections. Configure a Content Security Policy that restricts where scripts can send data, alongside controls on what can load.
  • Monitor changes and prepare a response. Assign responsibility for investigating alerts and removing compromised scripts quickly.

Growth and Security Need Shared Oversight

The takeaway is not that businesses should abandon A/B testing. It is that website experimentation needs clear ownership, controlled access and ongoing monitoring.

For marketing, development and security teams, this incident is a reason to review the tools supporting the customer journey and the safeguards surrounding them.

Read Wavesy’s full analysis, including the incident timeline and seven recommended safeguards: Optimizely Malware Incident: How to Protect Your Website From Third-Party Scripts.