🔍 Read the full analysis: Did You Use An Affected Website? What AI Users Can Check After The Malware Incident on ThorstenMeyerAI.com
Get business pricing on monitors, keyboards and dev gear
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
TL;DR
Security researcher Scott Helme of Report URI says malicious JavaScript reached visitors to sites run by 178 organizations through Optimizely on Nov. 16, 2026. Optimizely says an unauthorized party exploited a vulnerability, has removed the code and notified affected customers. The code attempted several forms of theft, but researchers have not shown that iPhones were compromised, and a listing does not mean an organization’s entire site was affected.
Malicious JavaScript was delivered to visitors of sites associated with 178 organizations through Optimizely on Nov. 16, 2026, according to security researcher Scott Helme of Report URI. Optimizely says an unauthorized party exploited a vulnerability in its Experimentation service to add code to some customer projects, making the incident a third-party supply-chain attack that could expose people browsing otherwise familiar sites.
Report URI says it checked 1,611 Optimizely snippets and found malicious code in 188. The researcher reported that the code was served to visitors of 178 organizations and said the actual number could be higher. BleepingComputer separately reported that urlscan.io scans showed the script loading or attempting to load on sites including Zoom, KLM, GitLab, the BBC, CNN and Salesforce. A presence on the list does not establish that every page or service belonging to an organization was affected.
The code was added to the Project JavaScript field in customer projects, according to Report URI. Optimizely snippets are used to load a site’s experiments and can also run customer-provided code across pages. Report URI says the rest of each affected snippet was unchanged, and it ruled out a content-delivery network cache-poisoning attack. Optimizely told BleepingComputer that the vulnerability was in the Experimentation account signup flow.
Report URI says the code attempted to replace cryptocurrency wallet addresses in page content, forms and clipboard activity; collect card details entered into a site’s own form fields; and capture cookies and screenshots. It also attempted to direct some iPhones and iPads to the Coruna and DarkSword exploit kits. Report URI says card information entered into hosted payment frames, such as Stripe or Adyen, was outside the code’s reach. The payload was rebuilt 26 times during the day, according to the researcher; that figure describes observed revisions, not the number of people affected.
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
What Visitors Should Check Now
The incident shows how a trusted script provider can create risk for visitors across many unrelated organizations without those organizations’ own websites being hacked. A browser may load the provider’s script because the site already relies on it, leaving visitors with little visible indication that the code has changed. The reported behavior could matter to people who copied a wallet address, entered payment details into a site’s own form, or browsed with an older Apple device while the code was active.
Report URI places the first injection it saw at 04:21 UTC on Nov. 16 and says infected Optimizely files had been cleaned by 23:11 UTC, a period of about 19 hours. That is the researcher’s observed window; it does not establish the exposure period for every affected project or whether a particular visitor’s data was taken. People who used a listed site during that period can review relevant account activity and payment transactions, especially if they typed card details into a site-hosted form. Any response should be proportionate: researchers have described what the code tried to do, not confirmed theft from every visitor.
For iPhone and iPad users, Report URI recommends updating to iOS 18.7.3 or later, or iOS 26.3 or later. Hudson Rock, which analyzed the mobile stage, cautioned that its findings were delivery observations rather than proof of successful device compromises. Installing current software is a practical precaution, but the available findings do not establish that every device that loaded the script was infected.
Products Worth Considering

Bose Smart Ultra Dolby Atmos Soundbar with Voice Control, HDMI eARC, Black

LG UltraGear 27-inch QHD OLED Gaming Monitor, 240Hz, 0.03ms, G-SYNC Compatible, FreeSync Premium Pro, HDR True Black 400

Anker SOLIX C1000 Gen 2 Portable Power Station with 200W Solar Panel
As an affiliate, we earn on qualifying purchases.
How the Optimizely Script Was Altered
Optimizely Web runs through a small JavaScript snippet that a customer site loads from Optimizely. The snippet can deliver experiments and, when configured, execute custom Project JavaScript. Report URI says the attacker inserted code into that field in customer projects, while the file continued to come from an address the affected websites already trusted. This helps explain how a change at one provider could reach visitors across a broad set of brands.
Optimizely’s Nov. 17 status-page entry said it had 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 user accounts, and said it had notified all affected customers. Report URI says an earlier wave involving the same actor’s injector appeared from Nov. 13 in scripts associated with Kissmetrics, StorifyMe and Minute Media; those sites are not part of the 178-organization Optimizely list, and how the code entered those services remains unresolved.
Report URI’s list spans multiple sectors, including 32 banking and finance organizations, 23 technology and software organizations, and 20 retailers. Those are counts in the researcher’s published list, not counts of confirmed compromised customers or affected visitors. Hudson Rock cautioned that an affected subdomain does not establish exposure across an organization’s entire website, product, customer base or checkout system.
“An unauthorized party exploited a vulnerability in Experimentation and used it to add malicious JavaScript to some customer projects.”
— Optimizely, in a status-page update posted Nov. 17
Exposure and Data Theft Remain Unclear
The available reporting does not establish how many people loaded the malicious code, whether it successfully stole any payment or account data, or whether any iPhone or iPad was compromised. The 178 organizations are those tied to the affected snippets in Report URI’s findings; a listed organization may have had only a particular subdomain affected. Report URI’s scan found code in 188 of 1,611 snippets, but those figures do not reveal the number of exposed visitors.
Optimizely has said the flaw was in its account signup flow and that it revoked access and reset affected accounts. The company has not, in the source material, explained how the flaw enabled writes to multiple unrelated customer projects. It is also unclear how the earlier activity involving Kissmetrics, StorifyMe and Minute Media was carried out or whether it is connected through the same access method. Hudson Rock says its findings do not demonstrate successful iPhone compromises.
Follow Optimizely’s Incident Updates
Optimizely says it has fixed the vulnerability, removed the injected code, notified affected customers and reset access tied to affected accounts. The next useful developments would be a fuller account of how the signup-flow flaw enabled changes to customer projects, the precise scope of affected project snippets, and whether the investigation found evidence of data theft or successful device compromise. Customers of the other named script providers may also look for clarification about the earlier activity.
Visitors who believe they entered payment details into a site’s own form during the reported window can review card transactions and contact their bank if they see activity they do not recognize. People who copied cryptocurrency addresses from a page while it was open can verify any subsequent transfer details with their wallet provider; a copied address is not proof that funds were diverted. Users should install current operating-system updates, including the versions recommended by Report URI, and rely on direct notices from affected services for account-specific guidance.
Key Questions
Was every page of the listed organizations’ websites affected?
No. The findings concern particular Optimizely snippets and projects. Hudson Rock cautioned that an affected subdomain does not establish exposure across an organization’s full website, products, customer base or checkout system.
What did the malicious code try to do?
Report URI says it attempted to replace cryptocurrency addresses, collect card details entered into a site’s own form fields, capture cookies and screenshots, and direct some Apple devices to exploit kits. These are reported capabilities and attempts, not proof that each action succeeded for a visitor.
Were iPhones confirmed to be compromised?
No such confirmation appears in the supplied findings. Hudson Rock described its observations as evidence of exploit delivery, not demonstrated iPhone compromises. Report URI advised users to update to iOS 18.7.3 or later, or iOS 26.3 or later.
How long was the Optimizely code active?
Report URI says it first observed an injection at 04:21 UTC on Nov. 16 and that all infected Optimizely files had been cleaned by 23:11 UTC that day. That is an observed period of about 19 hours, not a confirmed exposure window for every project or visitor.
What should a visitor do if they used an affected site?
Review payment and account activity if you entered details during the reported period, and contact your bank about transactions you do not recognize. Update Apple devices to a current supported version. If you copied a cryptocurrency address from a page, verify the destination of any transfer; the reported incident does not by itself show that your data or funds were stolen.
Source: ThorstenMeyerAI.com
