Skip to content
Bellator Cyber Guard
News4 min readQuick Read

Optimizely Flaw Let Hackers Serve Malware on Major Sites

By Bellator Cyber Guard Security Team
Optimizely Flaw Let Hackers Serve Malware on Major Sites - optimizely malware exploitation major websites update 2026

Vulnerability in Optimizely Let Attackers Inject Malware Into 178 Sites

A vulnerability in Optimizely's Experimentation platform let an unauthorized party inject malicious JavaScript into customer websites starting November 16, 2026, according to Optimizely and the security firm Report URI, as reported by SecurityWeek. Optimizely is a digital experience platform that site owners use to run A/B tests and personalize web pages, and it delivers its scripts through a content delivery network (CDN) that customer sites load as trusted code. Report URI said it examined 1,611 Optimizely scripts and found 188 infected ones belonging to 178 organizations, a list that it said includes the BBC, CNN, Zoom, GitLab, Salesforce, Equifax, HSBC and IKEA.

Optimizely confirmed the incident on its status page and on X early on November 17, saying an unauthorized party 'exploited a vulnerability in Experimentation and used it to add malicious JavaScript to some customer projects.' The company said it fixed the vulnerability, removed the injected code from affected projects, secured affected user accounts, and added unspecified additional protections. Optimizely has not disclosed how many customers were affected or named the vulnerability it patched.

Per Report URI's timeline, the first tampered script appeared at 04:21 UTC on November 16, and by 21:52 UTC that evening only one infected script remained uncleaned. The company's quick patching narrowed the exposure window, but the code had already been live across a large number of high-traffic sites for roughly a day.

Key Takeaway

The companies named, including BBC, CNN, Zoom, GitLab, Salesforce, Equifax, HSBC and IKEA, appear on Report URI's list as victims whose sites loaded a compromised Optimizely script, not as organizations accused of any wrongdoing. The incident illustrates how a single flaw in a widely used third-party script provider can turn trusted code on hundreds of otherwise unrelated websites into a malware delivery channel, without those sites' own infrastructure ever being breached.

How the Injected Code Worked

According to Report URI, the attacker placed malicious code in an optional field meant for a customer's own custom JavaScript, which Optimizely's platform executes on every page load. Because the tampered files were served from Optimizely's own CDN, browsers and site operators had no reason to treat the script as anything other than trusted first-party or vendor code. Report URI's Scott Helme summarized the broader lesson: trusted JavaScript does not always remain trustworthy, and a website can be compromised through a third-party dependency even when its own code and servers are untouched.

Report URI said the malware could swap cryptocurrency wallet addresses shown on a page for an address controlled by the attacker, skim payment card details entered on checkout or payment forms, and collect cookies and screenshots of the page a visitor was viewing. By the evening of November 16, Report URI estimated that roughly $7,000 in cryptocurrency had reached the attacker's wallet.

iOS Exploit Kits and Other Script Providers

Report URI also found that iPhone and iPad visitors to affected sites were served exploit kits it identified as Coruna and DarkSword. The threat intelligence firm Hudson Rock said it confirmed a link between the injected scripts and exploit-kit delivery infrastructure, but cautioned that successful exploitation of any device has not been demonstrated. Hudson Rock stated that 'the supported conclusion is a connection to exploit-kit delivery infrastructure. The current evidence does not establish a zero-day, successful device exploitation, or collection of specific device data by unseen downstream stages.' That distinction matters: visiting an affected page does not, on current evidence, mean an iPhone or iPad was actually compromised.

Hudson Rock's report, which it said drew on findings from a researcher at Ohey, also found that scripts from three other providers, Kissmetrics, StorifyMe and Minute-ly, served a small loader leading to the same exploit-kit infrastructure, with the earliest observation dating to November 13, three days before the Optimizely incident began. Hudson Rock said it is unclear how the code reached those providers' scripts, and whether their issue is connected to Optimizely's vulnerability or a separate incident remains unresolved in the current reporting. SecurityWeek also noted that Optimizely disclosed a separate, unrelated security incident in February 2026, in which a threat actor accessed its systems through a voice-phishing attack.

What This Means For Your Business

If your organization uses Optimizely's Experimentation product, confirm with your Optimizely account team or the company's status page that your projects were not among those affected, and review your custom JavaScript field for any changes you did not make. More broadly, this incident is a reminder that any third-party script tag loaded on your site, whether for analytics, A/B testing, personalization, chat widgets, or advertising, runs with the same access to your visitors' browsers as your own code.

Practical steps for site operators: inventory every third-party script your site loads and ask each vendor what its incident notification process looks like. Where vendors support it, use Subresource Integrity (SRI) hashes and a Content Security Policy (CSP) that restricts which domains can execute scripts on your pages, since Hudson Rock noted that some poisoned scripts carried a full payload embedded locally, meaning simply blocking the attacker's domain would not have stopped every instance. Healthcare practices, tax professionals, and small-business sites that rely on marketing or analytics widgets should treat vendor risk reviews as an ongoing task, not a one-time setup decision.

For consumers: if you visited any of the affected sites, particularly for checkout or cryptocurrency transactions, between November 16 and 17, 2026, review recent payment card and crypto wallet activity for unauthorized transactions. iPhone and iPad users should keep devices on the latest iOS update as routine hygiene; while Hudson Rock said successful exploitation was not demonstrated in this case, exploit-kit delivery infrastructure targeting mobile browsers is worth taking seriously regardless of this specific incident's outcome.

Share

Share on X
Share on LinkedIn
Share on Facebook
Send via Email
Copy URL
(800) 492-6076

Learn first. Decide when you are ready.

Keep learning, or apply this to your situation

Continue with a related guide, compare your options, or ask a specialist to help turn the advice into a practical next step.

People also look for

Keep exploring Ransomware & recovery

Reduce the chance of an infection, limit its reach, and make recovery possible without improvising under pressure.