🔍 Read the full analysis: Malware At 178 Major Websites: A Practical Checklist For AI Users on ThorstenMeyerAI.com
Get business pricing on office and shipping supplies
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
TL;DR
Report URI says malicious JavaScript was served to visitors of 178 organizations through the Optimizely Web platform on Nov. 16, 2026. Optimizely says an unauthorized party exploited a vulnerability, added code to customer projects and that it fixed the flaw; the code’s reach and any resulting theft or device compromises remain unclear.
Malicious JavaScript was served to visitors of websites operated by 178 organizations through the Optimizely Web experimentation platform on Nov. 16, according to security researcher Scott Helme of Report URI. Optimizely says an unauthorized party exploited a vulnerability to add code to some customer projects; the incident matters because visitors could receive harmful scripts from a supplier their chosen websites already trusted.
Report URI says it found the code in 188 of 1,611 Optimizely snippets it checked and cautions that the total may be higher. Its report describes code designed to replace cryptocurrency wallet addresses, capture payment-card details entered into sites’ own forms, collect cookies and screenshots, and direct some iPhones and iPads toward exploit kits. These are reported capabilities and delivery behavior; the source material does not establish that every attempted action succeeded or that every visitor was compromised.
The first injection Report URI observed was at 04:21 UTC on Nov. 16. It says all infected Optimizely files had been cleaned by 23:11 UTC that day, about 19 hours later. Optimizely’s Nov. 17 status-page notice says it fixed the vulnerability and removed injected code from affected projects. The company also told BleepingComputer it had ended active sessions, revoked tokens and reset access for affected accounts, and had notified affected customers.
Report URI says the attacker placed code in an optional Optimizely feature called Project JavaScript, which can run across a customer’s pages. The remaining parts of each snippet were untouched, its account says, and the files continued to be served from an Optimizely address trusted by the sites. Report URI says the incident was not a content-delivery-network cache-poisoning attack. BleepingComputer independently confirmed that the script loaded or tried to load on a number of listed sites, including Zoom, KLM, GitLab, the BBC, CNN and Salesforce.
Optimizely script attack · Nov 13 – Nov 17, 2026
How one trusted script carried malware to 178 websites
The sites were not hacked themselves. The code arrived inside a file they loaded on purpose.
The route (schematic)
Whether any iPhone was compromised has not been shown.
Timeline (UTC)
- Nov 13Earlier wave through three other providers’ scriptsKissmetrics, StorifyMe, Minute Media
- Nov 16 04:21First Optimizely injection seen
- 08:28Address-swapping payload first seen on a site
- 13:43Card skimmer added
- 17:13iPhone exploit delivery widened
- 19:24Report URI sweep: 186 of 1,611 snippets infected
- 21:52Only 1 of 188 infected snippets left
- 23:11All infected Optimizely files cleaned
- Nov 17 01:02Optimizely confirms the incident on its status page
Sources: Report URI (Scott Helme), Nov 16, 2026, timeline and update of Nov 17; Optimizely status page, Nov 17, 2026; Hudson Rock (Infostealers.com), Nov 16–17, 2026. The route is a schematic.
Graphic: Powered by Thorsten Meyer AI
How a Trusted Script Reached Visitors
The incident shows how a breach at a third-party web service can expose visitors to harmful code without an attacker first breaking into each customer’s website. A site can load a supplier’s script as part of ordinary operations, and that script may run in the site’s browsing context. Visitors may have no clear indication that a page’s trusted components have been altered.
The possible consequences depend on what the code encountered and what a visitor did. Report URI says card data entered into a site’s own form fields could be watched, while card details entered in hosted payment iframes such as Stripe or Adyen were outside the code’s reach. It also describes wallet-address replacement and cookie or screenshot collection. These findings indicate potential exposure, not confirmed losses across all listed organizations.
Report URI found that only 24 of 159 organizations whose site security policies it checked blocked the code, while 68 had no policy. That snapshot suggests some sites had limited defenses against unauthorized scripts, though the figures do not establish whether a policy would have prevented every effect or measure the incident’s total impact.
Popular right now

TCL 55-Inch F7D Series QLED 4K UHD Smart Fire TV (2026)

TCL F8D Series 50-Inch 4K QLED Smart Fire TV

Bose QuietComfort Headphones (2nd Gen), Wireless Noise-Cancelling Over-Ear Headphones, Eucalyptus Green
As an affiliate, we earn on qualifying purchases.
The Optimizely Project-Code Path
Optimizely Web lets customers run page experiments by loading a small JavaScript snippet. Customers can add their own code through the Project JavaScript field. Report URI says the attacker wrote into that field in customer projects, while the rest of each snippet remained unchanged. That mechanism helps explain how malicious code could appear on many separate sites through a shared service.
The organizations named in Report URI’s list span sectors: 32 banking and finance, 23 technology and software, and 20 retail. The list includes sites or subdomains associated with Zoom, the BBC, CNN, HSBC, Salesforce, IKEA, Equifax, GitLab, Ledger, Peacock, Air France-KLM and UNICEF USA. A listing does not mean an organization’s entire website, product or checkout system was affected. Hudson Rock cautions that exposure on one subdomain does not establish exposure across an organization’s wider services or customer base.
Report URI also describes an earlier wave beginning Nov. 13, involving scripts from Kissmetrics, StorifyMe and Minute Media on sites outside its list of 178. Hudson Rock reported a similar pattern and said how the code entered those services remained unresolved. The available material does not establish that this earlier activity had the same access route as the Optimizely incident.
“An unauthorized party exploited a vulnerability in Experimentation and used it to add malicious JavaScript to some customer projects.”
— Optimizely, in its status-page notice dated Nov. 17
Exposure and Access Details Remain Open
Public statements cited here do not explain the technical mechanics of the signup-flow vulnerability or how it gave the attacker write access to multiple unrelated customer projects. Optimizely says it fixed the flaw, removed injected code and reset access, but the source material does not describe the scope of any investigation or provide a final account of what data, if any, was taken.
It is also unclear how many people saw the script, whether any wallet transfers or card theft resulted, and whether any visitors’ cookies or screenshots were successfully exfiltrated. Report URI says the code was rebuilt 26 times during the day, but that raw count alone does not establish how many distinct versions reached users or how many users were affected. Hudson Rock says its iPhone findings concern delivery observations, not demonstrated compromises. Report URI’s statement that the real number of affected snippets may be higher is an estimate, not a confirmed total.
The list identifies affected sites or subdomains, not uniform exposure across each named organization. Some entries may represent a single tool or subdomain; the material does not show that every page or customer of a listed brand was exposed.
Customer Reviews and Security Updates
Optimizely says it has notified affected customers and removed the injected code after fixing the vulnerability. The next useful updates would clarify the flaw’s technical cause, the number and duration of affected projects, and whether investigations found evidence of data theft or successful device compromise.
Report URI advised iPhone and iPad users to update to iOS 18.7.3 or later, or iOS 26.3 or later, versions it says had been released months earlier by Apple. People who visited an affected site during the exposure window can review relevant account activity and follow guidance from the affected website or service; the source material does not establish that every visitor needs the same response.
For organizations using third-party scripts, the reported policy findings make script restrictions and review of supplier access relevant follow-up issues. Report URI’s figures describe the organizations it checked, not a complete audit of all affected sites. No further public findings or timetable for a detailed technical report are provided in the source material.
Key Questions
Which organizations were affected?
Report URI listed 178 organizations, including sites associated with Zoom, the BBC, CNN, HSBC, Salesforce and IKEA. Its list may include individual subdomains; it does not establish that every page or service of each organization was affected.
What could the malicious script do?
Report URI says it attempted actions including replacing cryptocurrency wallet addresses, watching card details entered into sites’ own forms, collecting cookies and screenshots, and directing some Apple devices toward exploit kits. The reported capabilities do not prove that each action succeeded.
Were iPhones confirmed to be compromised?
Not by the findings described here. Hudson Rock characterized its iPhone findings as delivery observations, not demonstrated compromises. Report URI advised users to update to iOS 18.7.3 or later, or iOS 26.3 or later.
Did Optimizely remove the code?
Optimizely said it fixed the vulnerability and removed injected code from affected projects. Report URI said all infected Optimizely files it tracked had been cleaned by 23:11 UTC on Nov. 16; the source does not provide a complete independent count of all exposure.
Is it known whether data or money was stolen?
The source material does not confirm successful theft of card details, cookies, screenshots or cryptocurrency. It describes what the code attempted or could do, while the extent of any resulting harm remains unclear.
Source: ThorstenMeyerAI.com
