When a bank's website serves malware, the bank did not have to be breached. That is the uncomfortable center of the Optimizely story. A site can be compromised through a third-party dependency without its own code or infrastructure being touched, and that gives every organization on the list a convenient defense. It also names the failure. These organizations handed part of their visitors' browsers to a vendor and, in many cases, had little way to see when the code changed [3][7].
This piece does not repeat what is confirmed. The explainer does that. It asks who owes whom an answer, and which of those answers are missing from the public record as of November 17.
Questions Optimizely should be able to answer
- How did a flaw in the account signup flow give an outsider write access to projects that belonged to other customers? Optimizely has said where the flaw was. It has not published how it worked [4][7].
- How many customers were affected? The company has not said [2][7].
- When did the attacker first get access? The earliest injection Report URI recorded was November 16 at 04:21 UTC. Hudson Rock saw related loaders on other services starting November 13, and Report URI traces the injector tool to September 17. None of that tells readers when the Optimizely access began [5][6][7].
- Optimizely's own main site and login page were listed among the infected pages, according to a coverage summary of Report URI's list. What did that exposure involve [6]?
- Optimizely disclosed a voice-phishing breach in February 2026. What changed afterward [2]?
Questions the affected organizations should be able to answer
- Did you tell your visitors? Optimizely says it notified affected customers [2]. In the coverage MB retrieved, Salesforce is the one affected organization quoted publicly. It told Reuters and BleepingComputer it disabled the scripts as a precaution, is investigating, and will notify customers if it finds unauthorized access to their data [2][3]. Most other organizations have no public statement in what MB found.
- Did cards typed into your own payment forms reach the attacker? The reports say the skimmer could read card fields in a site's own forms, and could not read fields inside a hosted payment frame from a provider such as Stripe [3]. A company can know which of its checkout pages used which approach.
- Did your page appear on the list at all? Hudson Rock cautions that an affected public page does not by itself establish a breach of the organization's internal systems [4].
The security basics that were available
Report URI crawled 256 affected hosts and reported what kind of Content Security Policy each had. A Content Security Policy is a browser rule that limits where a page can load and send data. The categories were: 68 hosts with no policy at all, 50 with a policy that let both the payload and the data theft through, 17 with a policy that blocked data theft but not the wallet-address swap, and 24 with a policy that blocked the payload [7].
A NUMBER THAT DOES NOT ADD UP The four categories above total 159, not 256. Report URI's own write-up does not account for the other 97 hosts [1]. The figure "only 15% blocked the payload" matches 24 of 159. It is about 9% if the denominator is 256. MB is not using the 15% figure. Some coverage repeats the 15% figure; MB does not. The same coverage says two policy settings, strict-dynamic and unsafe-eval, let the attack through on some sites. Report URI gives one example: at HSBC, the content security policy blocked the main malicious file and the data theft, but an inline copy still ran. It also points to 'unsafe-eval', a setting Optimizely's own documentation tells customers to allow [1]. |
A policy that allows the vendor's own domain does not help when the malicious file is served from that domain. Allowlisting cdn.optimizely.com would not have stopped this attack, because the code came from there [6]. That is why the question of who edits a vendor-hosted script matters more than the question of which domain it comes from.
MB's argument
This section is MB's analysis, not a reported finding. Most people did not agree to run a stranger's code when they opened a news site, a bank page or a pharmacy site. The industry treats third-party scripts as a convenience. This incident shows them to be a standing risk, and the people exposed to it are the ones least able to see it.
Nothing in the sources MB retrieved shows that medical, credit or other sensitive data was taken. A lack of confirmation is not reassurance, and any organization that holds sensitive data and used an affected script should say plainly what it knows.
QUESTIONS FOR ANY ORGANIZATION YOU DEAL WITH Which third-party scripts run on your site, and on your payment and login pages? Who at the vendor can edit them, and how would you know if one changed? Do you have a policy that limits where those scripts can send data? If a vendor's code harmed your visitors, who tells them, and how fast? |
MB will update this piece as Optimizely, the affected organizations and the investigators release more. The conversation continues.
General information, not individual security or legal advice.
Sources
[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. https://finance.biggo.com/news/556ed6e6-04e4-4c8c-946e-8d3cc816664c (retrieved Nov 17, 2026)
[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; its Report URI CSP figures should be checked against the original Report URI post)
PUBLISHING PACKAGE Slug: optimizely-who-owes-the-public-an-explanation SEO meta description: A bank's site can serve malware without the bank being hacked. Who owes the public an answer after the Optimizely attack, and which answers are missing? Pull quote: "A company can hand part of its visitors' browsers to a vendor and have no way to see when the code changes." Newsletter blurb: The Optimizely attack raises accountability questions for the vendor and for every organization that used it. MB lists the ones still unanswered. Instagram / Threads / LinkedIn caption: Hundreds of sites ran code they never checked. Which organizations told their visitors? Which questions are still unanswered? #Optimizely #Accountability #CyberSecurity #MelaninBlissMedia Audience question: What do you expect a company to tell you after its site serves you malware? |
