Skip to content
[ SIGNAL VERIFIED ] INDEPENDENT CYBERCRIME JOURNALISMCLASSIFIED // THE UNDERGROUND HAS A NEWSROOM / RSS
.COM
Latest News
ALL NEWS
Newsroom

Optimizely Script Compromise Spreads Malicious Code Across 178 Organizations’ Websites

Updated November 18: Censys maps infrastructure linked to the Optimizely script compromise, separating observed web properties from confirmed infections.

Optimizely Script Compromise Spreads Malicious Code Across 178 Organizations’ Websites
PUBLISHED UPDATED November 18, 2026 at 2:39 PM EST

Update — November 18, 2026: Censys maps related infrastructure

A November 17 Censys analysis expands the infrastructure context around the supply-chain poisoning. Censys counted 142 web properties with MCH panel titles, 144 with the Caishen backend title and 55 with the storefront title. These are observed infrastructure counts, not confirmed victims or proof that every visitor received an exploit.

Censys also reported that the original staging and command infrastructure went offline on November 17, while five new MCH hosts appeared within roughly a day. It cautioned that channel code 02111110 was a kit default present in more than 100 deployments. That shared value can connect components but cannot uniquely identify an operator.

IPCRIME assessment: defenders should retain the original exposure window and investigate relevant visitor and endpoint evidence even when a delivery domain disappears. A link to iOS exploit infrastructure warrants investigation; it does not establish successful infection on every exposed device.

IPCRIME NEWSROOM / NOVEMBER 17, 2026

A major website supply-chain incident is under investigation after the Optimizely experimentation platform delivered injected JavaScript through sites used by global media, retail and technology organizations. In research published November 16, Scott Helme of Report URI identified malicious code in snippets associated with 178 organizations. Optimizely subsequently confirmed that attackers exploited a vulnerability in its Experimentation account signup flow.

What was compromised and what wasn’t

Optimizely provides JavaScript that websites load to run experiments and personalization. Attackers inserted their own code into customer project scripts. That meant visitors could receive a malicious script from a domain the site already trusted. Researchers observed affected files connected with prominent organizations including BBC, CNN, Zoom, GitLab and Salesforce. This does not establish that every visitor was infected or that the underlying systems of each customer organization were breached.

How the injected code was designed to operate

Report URI’s analysis describes cryptocurrency address substitution, payment-card skimming and attempts to direct vulnerable iOS devices toward exploit content. Researchers documented changes to the payload during November 16 and observed some cryptocurrency transfers. The fact that malicious functionality was delivered should not be confused with a confirmed count of successful wallet thefts, payment-card compromises or iPhone infections.

What Optimizely says it fixed

Optimizely told BleepingComputer it blocked the vulnerable signup path, patched the weakness, removed malicious code from affected projects, revoked tokens, ended sessions, reset affected accounts and blocked delivery of the code through Cloudflare. It says affected customers have been notified and the investigation continues. Salesforce says it disabled Optimizely scripts as a precaution while reviewing potential impact.

What web teams should review

Site operators should inventory externally hosted scripts, examine recent third-party JavaScript changes, confirm whether their project was among those notified, and look for unexpected network requests and checkout-page modifications. A well-scoped Content Security Policy and script-integrity monitoring may reduce the blast radius of compromised trusted dependencies.

What’s still unknown

The exact number of people exposed to functioning payloads and the scale of any downstream theft are not settled. Investigators also distinguish customer-project injection from a CDN infrastructure compromise. IPCRIME will follow authenticated vendor or researcher updates rather than extrapolating from the number of affected scripts.

Original sources and documentation

IPCRIME coverage prepared November 17, 2026. Event dates and publication dates of primary sources may differ. Confirmed statements, external reporting and allegations are distinguished above. Corrections can be submitted through the site’s Contact page.

Editorial note

IPCRIME distinguishes public records and documented findings from allegations, analysis and commentary. Report corrections through our contact page.