A malicious-code campaign reached websites belonging to at least 178 organisations through Optimizely's web experimentation platform on November 16, according to security researcher Scott Helme of Report URI. The affected web scripts included those associated with Zoom, BBC, CNN, Salesforce, GitLab, IKEA, HSBC, Equifax and Air France-KLM. Optimizely subsequently acknowledged that an attacker exploited a vulnerability in its Experimentation account signup process and said it had blocked the vulnerable path and removed injected code.
How the attack spread
Optimizely lets customers run experiments and personalise websites by loading JavaScript from its service. In this incident, malicious code was written into the Project JavaScript fields of customer projects, so visitors could receive hostile instructions from a normally trusted Optimizely-hosted script. This is a third-party web-script compromise: it does not by itself prove that the affected organisations' internal networks were penetrated.
Report URI checked 1,611 distinct Optimizely snippets and found 188 infected snippets belonging to 178 organisations. That is a measured sample, not a definitive count of all affected websites or all people exposed. Independent reporting by BleepingComputer confirmed the malicious script appeared in archived scans of several named websites.
What the code attempted
Researchers identified several functions in the injected payload. One replaced cryptocurrency wallet addresses with attacker-controlled addresses, potentially diverting transfers. Another watched payment forms for card details, while other components sought cookies and page screenshots. On some iPhones and iPads, the code attempted to load the Coruna and DarkSword exploit kits. The presence of exploit code does not prove that an individual phone was successfully compromised.
Helme reported blockchain transactions worth approximately $7,040 reaching attacker-controlled wallets by 19:25 UTC on November 16. That is evidence of funds reaching the identified wallets, not a reliable estimate of total losses across all visitors. The researchers could not determine how many payment cards, cookies or screenshots were actually obtained.
What Optimizely confirmed
In a statement to BleepingComputer, Optimizely said an unauthorised party exploited a vulnerability in its Experimentation account signup flow to add malicious JavaScript to some customer projects. The company said it had patched the vulnerable path, removed injected code, terminated active sessions, revoked tokens, reset affected account access and blocked code delivery through Cloudflare. It said affected customers had been notified and an investigation was continuing.
This explanation is more specific than the initial uncertainty about how so many projects were modified. It also means the event should not be described simply as an unproven breach of the CDN: the company's account concerns access to customer projects and malicious code delivered through legitimate snippets.
What major companies said
Reuters reported that Salesforce was investigating unauthorised changes to Optimizely scripts and disabled them as a precaution. Equifax said it had investigated and stopped using Optimizely, while finding no evidence that its own systems had been compromised. Such statements are limited to the companies' investigations; they do not settle what happened to every visitor or every other organisation.
Timeline and cleanup
Report URI's reconstruction places an early Optimizely injection at about 04:21 UTC on November 16, with further malicious functionality appearing during the day. The researchers observed a mass cleanup late that evening. By 21:52 UTC, one of the 188 previously infected snippets was still observed carrying the code. This is a point-in-time observation, not a guarantee that all possible exposure or downstream harm had ended.
What users and operators should do
Website operators should review Optimizely project JavaScript changes, relevant account logs, active sessions, tokens and third-party script policies; coordinate with Optimizely and investigate unexpected network requests during the incident window. Security teams should check whether content-security policies and monitoring could have flagged the added domains. Visitors who entered payment information or made cryptocurrency transfers while browsing affected pages should review their accounts and transaction destinations. iPhone and iPad users should install available security updates, although visiting a listed website alone does not establish that their device was infected.
What is confirmed: Malicious scripts were delivered through Optimizely projects used by major brands, and Optimizely acknowledged the signup-flow vulnerability. What remains uncertain: The full number of exposed users, total theft of personal data, and whether any particular visitor's iPhone was successfully exploited.




