For Windows users and enterprise administrators, the immediate concern is malicious code running inside otherwise legitimate webpages—not evidence that every visitor’s computer received a persistent malware infection.
A vendor notice changes the initial picture
The initial reporting left the entry point unresolved. A subsequent update provides an important qualification: status-monitoring service IsDown reproduces an Optimizely incident notice timestamped 01:02 UTC on November 17, 2026, stating that an unauthorized party exploited a vulnerability in Experimentation to insert malicious JavaScript into customer projects.
According to that reproduced notice, Optimizely says it fixed the vulnerability, removed injected code, secured affected user accounts, and added protections against further unauthorized code delivery. This is a vendor statement carried by a monitoring service, not an independently verified account of the underlying vulnerability. The notice does not identify the flaw or explain the full scope of access.
How trusted scripts became the delivery route
Helme’s Report URI investigation places the injected code in Optimizely’s Project JavaScript, or projectJS, field. The surrounding snippets continued arriving from the trusted cdn.optimizely.com domain. Report URI explicitly distinguishes this from CDN cache poisoning: the distribution network served modified project content.
BleepingComputer described loaders that fetched track.js from 1688360[.]cc, including versions that concealed the address using Base64 and JavaScript’s atob() function. Another variant contained an embedded payload that could execute if the remote script was blocked. A search for the visible attacker domain alone therefore cannot establish that a snippet is clean.
The practical lesson is uncomfortable but straightforward: trusting a script’s delivery address does not establish that its contents remain trustworthy.
What the payload could—and could not—reach
StepSecurity’s payload analysis describes several distinct behaviors:
- Cryptocurrency substitution: Rewriting wallet addresses in page content, forms, clipboard interactions, and requests.
- Card skimming: Capturing card numbers, expiration dates, and security codes from accessible forms or requests.
- Conditional data theft: Sending page information, screenshots, and JavaScript-readable cookies after an address substitution.
- An iOS stage: Loading additional scripts and an iframe on selected Apple devices.
The boundaries matter. StepSecurity found that the skimmer could not read card fields inside cross-origin payment iframes, while cookies marked HttpOnly were inaccessible to the script. Helme identified Coruna and DarkSword exploit kits, but StepSecurity did not retrieve those secondary files and could not independently establish their exploit coverage. Attempted delivery is not proof that every visiting iPhone or iPad was successfully compromised.
Cleanup is not a historical all-clear
Report URI’s observed timeline starts with an Optimizely injection at 04:21 UTC on November 16. By 21:52 UTC, only one of the 188 identified snippets still contained malicious code. These observations demonstrate substantial cleanup, not a universal exposure window for every customer.
Helme reported roughly $7,040 in attacker-wallet receipts as of 19:25 UTC that day. Those receipts should not be treated as a complete loss assessment: StepSecurity found some associated wallets had activity predating the incident, and blockchain records do not identify every victim or measure stolen card data.
What administrators and visitors should do
For organizations using Optimizely Web, Report URI recommends reviewing project and experiment code, auditing users and API-token access, rotating relevant credentials, and assessing exposed session secrets.
StepSecurity additionally recommends checking historical browser telemetry and Content Security Policy reports, preserving snippet modification information, and asking Optimizely which project IDs changed and when. A clean download now does not prove the same file was clean during the incident.
Potentially exposed visitors should verify cryptocurrency destinations against an independently trusted address—not merely the copied webpage text—and contact their card issuer if they entered payment details into an affected page. The response should follow the actual exposure: which page loaded which payload, when, and what the visitor did there—not simply whether a familiar brand appeared on an affected-site list.
References
- Optimizely supply chain attack infects major brands' sites with malware BleepingComputer · 2026-11-16T21:12:17-05:00
- OPTIMJACK: Optimizely-Hosted Scripts Loaded a Crypto Clipper and Card Skimmer on 186 Confirmed Sites - StepSecurity stepsecurity.io
- Episerver Web Experimentation Security Incident — Nov 2026 | IsDown isdown.app