Optimizely CVE-2026-132224 Malware Hits 178 Websites

Attackers exploited a vulnerability in Optimizely Web Experimentation on Nov. 16, injecting malicious JavaScript into customer projects and causing trusted websites to serve malware to visitors at 178 organizations. Optimizely said it fixed the vulnerability, removed injected code and secured affected accounts in its incident notice. The affected organizations were not necessarily breached directly; the campaign abused a shared third-party service used to deliver website experiments.

Researchers at Report URI examined 1,611 Optimizely snippets and found malicious code in 188 associated with the 178 organizations, including widely known brands such as CNN, the BBC, Zoom, Salesforce, GitLab, IKEA, Equifax and HSBC. The poisoned snippets continued to load from Optimizely’s legitimate content-delivery infrastructure, meaning browsers treated the code as a trusted dependency. The incident therefore created a supply-chain exposure across otherwise unrelated websites rather than evidence that attackers penetrated each company’s own network.

The vulnerability is tracked as CVE-2026-132224. The National Vulnerability Database describes an account-signup flaw that allowed attacker-controlled content into the projectJS, or Project JavaScript, field of certain cdn.optimizely.com assets. NVD lists Optimizely Web Experimentation versions before Nov. 17, 2026, as affected and records CWE-642, External Control of Critical State Data. NVD has not assigned a CVSS score, and its entry does not provide an exploit-status designation or public proof-of-concept link.

The injected payload had several objectives. Reporting from Report URI and Optimizely indicates that it could replace cryptocurrency wallet addresses, capture payment-card numbers, expiration dates and CVVs from page forms, steal cookies that lacked the HttpOnly attribute and collect page screenshots. On iPhones and iPads, the code also loaded additional infrastructure associated by researchers with Coruna and DarkSword exploit kits. The Media Trust has tracked the broader malware as Hydra-Cart, but no reliable public attribution to a named threat actor has been established.

Optimizely’s status update says the vulnerability was fixed and the injected code removed, while the vendor’s incident report provides additional response details. Organizations using Web Experimentation should review Project JavaScript changes and access logs, update or rotate credentials and tokens tied to affected projects, inspect content-security and browser telemetry for suspicious domains, and determine whether payment or session data was entered while compromised snippets were active. Website owners should also inventory every externally hosted script and consider strict content-security policies, integrity controls where practical, and monitoring that can detect changes in vendor-managed code.

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply