ReadingResearchRadarInvestment framework
Sign in / Sign up
← Back to reading
TopicDisconfirmAI EditorialUpdated 2026-11-21 08:37

Optimizely Supply Chain Attack

8 steps1 pieces5 Sources

The US-based digital experience platform Optimizely confirmed a supply chain attack on November 17, 2026, after attackers exploited a vulnerability in its Web Experimentation service to inject malicious JavaScript into customer projects. This compromise affected 178 organizations, including major entities like the BBC, CNN, GitLab, and HSBC, without directly breaching their own infrastructure. The injected code served as a crypto clipper and card skimmer for website visitors, stealing cryptocurrency addresses, credit card data, and cookies, while also attempting to deliver iOS exploit kits (Coruna and DarkSword) to iPhone and iPad users. Report URI researchers identified 188 infected snippets out of 1,611 checked, with approximately $7,000 in cryptocurrency stolen by the evening of November 16. Optimizely stated that the flaw was fixed, the malicious code removed, and affected accounts secured within hours of discovery. The incident highlights critical risks in third-party script management, prompting security experts to urge stricter Content Security Policies (CSP) and continuous monitoring of external dependencies.

How it got here

  1. 2026-11-13

    November 13, 2026: Hudson Rock reports early observations of similar loader activity via other providers (Kissmetrics, StorifyMe), though the primary Optimizely campaign began later.

    securityweek.com ↗
  2. 2026-11-16

    November 16, 2026, 04:21 UTC: First injection of malicious JavaScript into an Optimizely Web project is recorded by Report URI.

    stepsecurity.io ↗
Sign in / Sign up
ReadingResearchRadarInvestment framework
2026-11-16

November 16, 2026, 08:28 UTC: Researchers observe the main malicious payload being loaded on bbc.com.

malwarebytes.com ↗
  • 2026-11-16

    November 16, 2026, 21:52 UTC: Only one of the 188 infected scripts remains active; most have been cleaned.

    techtarget.com ↗
  • 2026-11-16

    November 16, 2026, 23:11 UTC: All monitored infected Optimizely files are confirmed clean by Report URI.

    stepsecurity.io ↗
  • 2026-11-17

    November 17, 2026: Optimizely publicly confirms the incident, stating the vulnerability in the signup flow was exploited to impersonate admins and modify Project JavaScript fields.

    forrester.com ↗
  • 2026-11-17

    November 17, 2026, 04:11-05:39 UTC: Attacker wallets (LTC, ETH, BTC, TRON) are emptied.

    stepsecurity.io ↗
  • 2026-11-18

    November 18, 2026: Optimizely publishes a fuller account of how the attacker gained access, confirming the flaw was in the account signup flow.

    stepsecurity.io ↗
  • What is still unsettled

    • What specific technical details remain undisclosed about the initial exploitation vector beyond the 'signup flow' vulnerability?
    • Will regulatory bodies or affected enterprises pursue liability claims given the scale of exposure across financial and media sectors?
    • How many total victims were exposed to the iOS exploit kits, and did any result in successful device compromise?

    Sources

    • securityweek.comSecurityWeek↗
    • stepsecurity.ioStep Security↗
    • malwarebytes.comMalwarebytes↗
    • techtarget.comTechTarget↗
    • forrester.comForrester↗

    Coverage in this topic

    • Supply Chain Attack on Optimizely Compromises 178 Organizations Including BBC and GitLab2026-11-18News

      Attackers exploited a vulnerability in Optimizely's Web Experimentation service to inject malicious JavaScript into 178 organizations' websites, stealing cryptocurrency addresses, credit card data, and cookies, while delivering iOS exploit kits.