← Back to news
Krebs on Security19 Nov 2026 · 2 min read

Optimizely Incident Exposes Risks of Third-Party JavaScript Supply Chains

A security incident involving Optimizely's experimentation platform reportedly led to malicious JavaScript being delivered through websites operated by at least 178 organizations, including major medi...

A security incident involving Optimizely's experimentation platform reportedly led to malicious JavaScript being delivered through websites operated by at least 178 organizations, including major media, financial, technology and cryptocurrency-related brands.

According to research published by Report URI, attackers exploited a vulnerability in Optimizely Experimentation on November 16 to insert code into certain customer projects. The injected script was reportedly modified repeatedly during the incident and delivered a malware toolkit designed to collect browser cookies, payment-card information and screenshots. It also attempted to replace cryptocurrency wallet addresses displayed on affected pages with attacker-controlled addresses.

Researchers said some visitors were also served code targeting known flaws in older Apple iPhone and iPad devices. The reported exploits were aimed at outdated devices and could potentially enable extensive access to data when successfully executed.

Optimizely said it identified unauthorized use of a vulnerability affecting its Experimentation product and took steps to contain the issue. Those actions included restricting access to the affected path, deploying a fix, removing injected scripts, ending active sessions, revoking tokens and resetting access for affected accounts. The company said it had remediated the vulnerability and was continuing its investigation with outside specialists.

Third-party code exposure

The event highlights the security implications of third-party JavaScript, which is commonly used for analytics, advertising, personalization and A/B testing. Such code generally executes in a visitor's browser and can alter page content or access information available within the webpage context.

Report URI found that many of the affected sites lacked protections capable of limiting the malicious script. Of the sites it examined, 68 had no Content Security Policy (CSP), while another 50 had policies that did not block the payload. Only 24 sites had CSP configurations that fully prevented it, the firm said.

  • Organizations can use restrictive CSPs to limit which domains may provide scripts and other resources.
  • Web operators should inventory third-party dependencies and review their permissions and loading order.
  • Users can reduce exposure to unnecessary third-party scripts with reputable content or ad-blocking tools, although these may affect site functionality.

Researchers estimated that the attackers obtained roughly $7,500 in cryptocurrency, along with an unknown quantity of payment-card data. The broader impact remains under investigation.

Share this article:TwitterLinkedIn