Attackers used Optimizely’s website-experimentation platform to deliver malicious JavaScript through scripts associated with 178 organizations on November 16, 2026, according to security researcher Scott Helme of Report URI. The investigation found 188 modified scripts among 1,611 examined. Optimizely confirmed exploitation of a vulnerability, said it removed the injected code, and secured affected accounts. The findings do not mean the internal networks of all 178 organizations were breached.
The affected organizations included sites associated with the BBC, CNN, Zoom, Salesforce, GitLab and several financial firms. Website visitors could encounter hostile code simply because an otherwise legitimate page loaded a compromised third-party script. The number of exposed individuals and confirmed infections has not been established.
Optimizely Web Experimentation lets operators run A/B tests and personalization through a JavaScript snippet loaded from its content-delivery network. Attackers inserted a loader into the platform’s customizable Project JavaScript field. The browser then received the code from an already trusted domain, with no obvious change to the host site’s address.
A trusted script became the attack route
Report URI first observed an affected Optimizely script at 04:21 UTC on November 16. Researchers identified three loader variants, including one using base64 encoding and another retaining an inline fallback if the attacker’s remote domain was blocked. The payload changed repeatedly as the incident unfolded.
One function searched pages, form fields and clipboard operations for cryptocurrency addresses, replacing valid destinations with wallets controlled by the attacker. The distinction matters to Bitcoin holders: a legitimate-looking payment page can display or paste a different address after an infected script runs. Earlier Bitcoin security coverage examines separate network and mining risks.
Original RSA Conference 2024 security-headers talk by Scott Helme (Report URI) and Tanya Janca, explaining Content Security Policy and browser defenses. Archival technical context, not footage of the 2026 Optimizely incident. Credit: RSA Conference / conference recording.
Crypto swaps, card skimming and iOS targeting
At 13:43 UTC, the attack added payment-card skimming. The script sought card numbers, expiration dates and security codes entered into ordinary page forms, then attempted to send them away. Fields hosted inside independent payment-provider iframes were outside the script’s stated collection path. The malware could also capture accessible cookies and screenshots.
The code additionally tried to route vulnerable iPhones and iPads toward the Coruna and DarkSword exploit kits. Researchers identified exploit paths targeting older iOS versions. Delivery or attempted exploitation does not establish that every visitor’s phone was compromised; successful-device infections remain unquantified.
Helme’s team observed roughly $7,000 in incoming transactions to attacker-linked cryptocurrency wallets during its investigation. Researchers and independent reporting cautioned that not every transfer can be definitively attributed to visitors of the affected sites. The total value of stolen funds or payment-card data is therefore unknown.
The incident resembles broader software-supply-chain failures. Corelight’s MCP dependency study documented changing software beneath a pinned application, while malicious Cursor marketplace extensions demonstrated another trusted-delivery risk. Neither prior case is evidence of shared attackers.
What Optimizely and affected companies confirmed
Optimizely told BleepingComputer that attackers exploited its Experimentation signup flow. The company says it blocked the vulnerable path, removed malicious code, ended active sessions, revoked tokens and reset affected access. Salesforce disabled the service’s scripts while investigating, and Equifax told Reuters it found no evidence of compromise to its own systems.
Protective browser policies mattered. Report URI assessed 159 affected organizations’ Content Security Policies and reported that 24 had restrictions capable of blocking the payload outright. Other policies could allow execution but block some data transmission. The result shows why merely trusting a well-known script domain is insufficient.
Original NDC London 2018 talk by Scott Helme demonstrating security headers and Content Security Policy. Older first-party speaker material explaining a preventive control; not footage of the November 2026 attack. Credit: NDC Conferences / YouTube.
Protecting websites and visitors
For website administrators, priorities include inspecting third-party script inventories, comparing served JavaScript against trusted versions, reviewing Content Security Policy restrictions, and examining November 16 payment-page activity. A related Web3 malware case emphasizes checking software provenance rather than brand appearance.
Visitors who entered payment data on a potentially affected page should review transactions and contact their card issuer when appropriate. Cryptocurrency users should independently verify destination addresses before sending; updating iOS and browsers reduces exposure to known exploits. The Luxor Commander incident illustrates a distinct form of unauthorized Bitcoin revenue redirection, not an extension of the Optimizely attack.
The vulnerability is reported fixed, but the investigation continues. The reliable measure is 178 organizations with affected scripts, not 178 confirmed network penetrations or millions of proven victims. Future incident reports will be needed to establish the full visitor impact.
Sources and methodology: Scott Helme / Report URI original technical investigation, November 16, 2026; BleepingComputer’s November 16 investigation and Optimizely statement; Reuters’ November 17 independently reported company responses; Help Net Security coverage; TMZ’s original report. Reported script counts and Content Security Policy assessments are researcher samples rather than a complete census of the internet.
Editor’s Note: A script affecting an organization’s website does not prove compromise of its internal networks or infection of every visitor. The number 178 represents organizations whose Optimizely JavaScript snippets carried malicious code in Report URI’s investigation; 188 represents infected scripts among 1,611 checked. The exact monetary loss and number of compromised devices remain unverified. The original 1200 × 630 featured cover is conceptual photorealistic artwork depicting a fictional analyst, not an authentic incident photograph. The identical uploaded BitcoinVersus.tech secondary wordmark was applied at the bottom-left, retaining neon-green lettering and a tight black highlight. Two conference videos explain security controls in earlier recordings. Browser playback and mobile behavior require separate testing.

BitcoinVersus.Tech is volunteer-run and publishes independent technical journalism. An optional 5,000-satoshi donation supports ongoing research. Scan the original QR from a second screen using a compatible Bitcoin wallet; on the same phone, use a wallet that can import a saved QR image when supported. Independently verify recipient 3C9o19EH5HSiwEPyCTmEKzxhNCbo2X6TTb and the 5,000-satoshi amount before sending. Bitcoin transfers are generally irreversible.
We volunteer daily to ensure the information on BitcoinVersus.Tech is Verifiably True. Technical and financial coverage is educational and informational, not personalized engineering, securities, tax or investment advice.

Leave a Reply