On Monday, November 16, 2026, malicious JavaScript reached visitors of at least 178 organizations through Optimizely Web Experimentation, a tool companies use to test changes to their websites. Affected sites included Zoom, the BBC, CNN, Fox News, Salesforce, GitLab, IKEA, HSBC, Equifax, Air France-KLM and Ledger [2][3]. Report URI's list includes 32 banking and finance organizations and 8 in healthcare and pharma, among them Invisalign, Takeda and Covetrus [1]. Optimizely has confirmed that an unauthorized party used a flaw to add malicious code to some customer projects [2][4].

This piece separates three things: what has been confirmed, what has been reported but not established, and what no one has answered yet. The story is moving. Everything here is current as of the morning of November 17.

WHO IS REPORTING, AND WHY THAT MATTERS

The 178 figure comes from Report URI, a website security monitoring company run by researcher Scott Helme. Report URI sells tools that detect malicious scripts, which Gizmodo noted and Report URI's write-up promotes [2]. That does not make the findings wrong. It means readers should know the source has a commercial interest in the topic.

StepSecurity documented the payload. Some researchers have called the campaign OPTIMJACK [9]. Hudson Rock, a separate firm, recovered some infected Optimizely files itself [4][5]. BleepingComputer independently confirmed that the malicious script loaded, or tried to load, on Zoom, KLM, GitLab, the BBC, CNN and Salesforce [2].

What is confirmed

  • Report URI examined 1,611 Optimizely scripts and found malicious code in 188 of them, belonging to 178 organizations. Report URI says, "The real number is likely higher" [1].
  • Optimizely's spokesperson Victoria Johnson told Gizmodo that the flaw was in the Experimentation account signup flow [4].
  • The attacker edited a customer-facing field called Project JavaScript. The files still came through Optimizely's normal delivery, so the affected sites' own code was not changed. Report URI says this was not cache poisoning [3].
  • The code swapped cryptocurrency wallet addresses on the page for the attacker's own. It collected card details typed into a site's own forms. After an address swap it sent cookies, the page address and a screenshot to the attacker. Card fields inside a hosted payment frame, such as Stripe's, were out of reach, and so were HttpOnly cookies [3].
  • On iPhones and iPads it loaded exploit kits named Coruna and DarkSword, chosen by iOS version. The kits list iOS 18.7.3 or later, and iOS 26.3 or later, as patched [2][3].
  • Report URI counted about $7,000 in the attacker's wallets on Monday. Report URI's figure was about $7,040 by 19:25 UTC [1]. StepSecurity put it near $6,600. Two of the addresses were active before the injections began, and StepSecurity says the transaction chain does not show which transfers came from victims [2][6].
  • Optimizely's status notice, posted at 01:02 UTC on Tuesday, says it fixed the vulnerability, removed the injected code and secured affected accounts. The incident was still listed as being monitored [3][4]. The notice says Optimizely added protections to prevent unauthorized code from being delivered [8]. Optimizely also told BleepingComputer it removed the code, ended sessions, revoked tokens and notified all affected customers [2].

The timeline, in UTC

Time Event Source
Mon Nov 16, 04:21 First injection recorded, on the BBC's script Report URI [1]
13:43 Card skimmer added to the payload Report URI [1]
17:13 to 17:57 Coruna exploit frame added for iOS 18.6 and earlier visits Report URI [1]
20:40 Mass cleanup begins. Report URI says the payload was rebuilt 26 times during the day Report URI [1]
21:52 One snippet, TalkTalk's, still carried the code Report URI [1]
23:11 Report URI says all infected Optimizely files were clean Report URI, as reported by [2]
Tue Nov 17, 01:02 Optimizely posts its incident notice [8]

Both clean-up figures are Report URI's: the 21:52 entry comes from its own post, and the 23:11 "all clean" entry as reported by The Next Web [1][2]. Smartsheet's script was also reported to have been cleaned once and then re-infected with a hidden copy [6].

What has been reported but not established

  • Successful iPhone takeovers. Cynet retrieved the iOS stage with an emulated browser and called it conditional delivery, not a compromise of a real device [2]. Hudson Rock writes that “No successful real-device exploitation or campaign-wide victim count is asserted” [5].
  • That the named companies' own networks or databases were breached. The reports describe malicious code reaching visitors' browsers. They do not establish that internal systems were accessed [3].
  • That every visitor to an affected page was compromised. The code had conditions, and the reports do not give a count of affected visitors [3].

What is still unknown

  • How a signup-flow flaw gave an outsider write access to existing customers' projects. Optimizely has not published a technical description [7].
  • When the attacker first got access, how many customers were affected in total, and whether any customer data held by Optimizely was accessed [7].
  • Who did it. No threat actor has been publicly named [7].
  • How many card numbers, cookies and screenshots reached the attacker. Neither Report URI nor StepSecurity can see this [2].
  • The total financial loss, which a wallet total cannot show [3].

The earlier warnings

Hudson Rock found that scripts from three other services served a small loader tied to the same infrastructure. Kissmetrics was observed on securitybank.com on November 13 at 05:42 UTC, StorifyMe on faz.net on November 13 at 20:31 UTC, and minute-ly on foxsports.com on November 16 at 16:25 UTC. Hudson Rock says these are observation times, not the start of any intrusion, and that Optimizely is the only one of the four with a confirmed access path [5].

Hudson Rock draws a limit on its own finding: “Evidence from four poisoned delivery services does not establish four independently explained vendor-system breaches.” It says shared infrastructure supports a technical relationship, but does not identify one operator [5]. Report URI traces the same injector tool back to September 17, when it surfaced on Turkish websites [6]. Optimizely also disclosed a separate incident in February 2026, a voice-phishing attack that exposed basic business contact data [2].

What you can do

  1. Update iPhones and iPads to iOS 18.7.3 or later, or iOS 26.3 or later. Those are the versions the exploit kits list as patched [2].
  2. If you sent cryptocurrency on an affected site on November 16, compare the address you intended with the address the transfer went to. The code swapped addresses in the page [3].
  3. If you paid by card on an affected site that day, watch your statement and report unauthorized charges to your card issuer right away. The FTC says federal law protects you from unauthorized use of your credit card [10].
  4. If you sent cryptocurrency, contact the exchange or ATM operator immediately and ask them to reverse the transaction. The FTC warns that crypto payments do not have the same legal protections as card payments, so it can be hard to get money back [10].

MB will update this piece as Optimizely, the affected organizations and the investigators release more. The conversation continues.

General information, not individual security or financial advice. If you believe money was stolen, contact your card issuer or exchange immediately.

Sources

[1] Helme S. World's Largest Brands Infected With Malware Via Optimizely. Report URI, Nov 2026. https://blog.report-uri.com/worlds-largest-brands-infected-with-malware-via-optimizely/ (primary source; retrieved Nov 17, 2026)

[2] Hackers used Optimizely to plant malware on Zoom, BBC, CNN and HSBC sites. The Next Web, Nov 17, 2026. https://thenextweb.com/news/optimizely-hack-malware-zoom-bbc-cnn-hsbc-178-sites (retrieved Nov 17, 2026)

[3] Optimizely Hack Serves Malware Through Scripts Used by 178 Organisations. Hackread, Nov 17, 2026. https://hackread.com/optimizely-hack-malware-scripts-178-organisations/ (retrieved Nov 17, 2026)

[4] Optimizely flaw used to inject malware into customer websites. iTWire, Nov 2026. https://itwire.com/business-it-news/security/optimizely-says-it-has-fixed-flaw-used-to-inject-malicious-scripts (retrieved Nov 17, 2026)

[5] Beyond Optimizely: Malicious Scripts Traced Across Four Web Services. Infostealers.com (Hudson Rock), Nov 2026. https://www.infostealers.com/article/beyond-optimizely-malicious-scripts-traced-across-four-web-services/ (retrieved Nov 17, 2026)

[6] Optimizely Script Hijack Reaches 178 Sites, Swaps Crypto Wallet Addresses and Skims Cards (Updated). BigGo Finance, Nov 2026, relaying StepSecurity and Report URI data. https://finance.biggo.com/news/556ed6e6-04e4-4c8c-946e-8d3cc816664c (retrieved Nov 17, 2026; secondary relay of the primary timelines)

[7] The Optimizely Web incident: what happened, and what SaaS teams should test now. DEV Community (rokkhe), Nov 2026. https://dev.to/rokkhe/the-optimizely-web-incident-what-happened-and-what-saas-teams-should-test-now-5bbj (retrieved Nov 17, 2026; independent write-up, used for the list of open questions and Optimizely's notices)

[8] Optimizely status page, incident notice posted Nov 17, 2026, 01:02 UTC. https://status.optimizely.com (primary source; retrieved Nov 17, 2026; still listed as Monitoring)

[9] Hijacked Optimizely scripts served card skimmers. The Hacker News, Nov 2026. https://thehackernews.com/2026/11/hijacked-optimizely-scripts-served-card.html (retrieved Nov 17, 2026)

[10] What To Do if You Were Scammed. Federal Trade Commission, updated Aug 21, 2026. https://consumer.ftc.gov/articles/what-do-if-you-were-scammed (retrieved Nov 17, 2026)

PUBLISHING PACKAGE

Slug: optimizely-attack-confirmed-unknown

SEO meta description: Malicious code reached visitors of at least 178 organizations through Optimizely. What is confirmed, what is not, and what no one has answered yet.

Pull quote: "The reports describe malicious code reaching visitors' browsers. They do not establish that the named companies' own databases were breached."

Newsletter blurb: A vendor flaw put malicious code on at least 178 organizations' websites on Nov 16. MB separates what is confirmed from what is viral.

Instagram / Threads / LinkedIn caption: 178 organizations. One vendor. Here is what is confirmed, what is not, and what is still unanswered. Update your iPhone, check your cards, check any crypto you sent. #Optimizely #CyberSecurity #FactsFirst #MelaninBlissMedia

Audience question: If a company you use served you malicious code, how and when do you expect to be told?