Optimizely supply-chain attack injected malicious JavaScript into major websites
Optimizely says attackers exploited a vulnerability in its Web Experimentation signup flow to place malicious JavaScript in customer projects. Researchers found poisoned scripts associated with 178 organizations, but the number of exposed visitors, stolen cards, diverted payments, or compromised iPhones remains unresolved.
What happened?
Confirmed facts: Optimizely disclosed on November 17, 2026 that an unauthorized party exploited a vulnerability in its Web Experimentation product and added malicious JavaScript to some customer projects. The company told BleepingComputer that the vulnerable path involved the Experimentation account signup flow. Optimizely says it fixed the vulnerability, removed the injected code, secured affected accounts, and added protections intended to prevent unauthorized code delivery. Independent research: Report URI examined 1,611 Optimizely scripts and identified 188 poisoned snippets associated with 178 organizations. The affected set included scripts used by major brands and media, technology, finance, retail, and travel sites. Reuters confirmed that Salesforce was investigating unauthorized Optimizely script changes and disabled them as a precaution. Equifax told Reuters it stopped using Optimizely and found no evidence its own systems were compromised; IKEA said it was assessing possible impact. Security researchers recovered JavaScript designed to substitute cryptocurrency wallet addresses, collect payment-card data available to the page, capture JavaScript-readable cookies and screenshots, and direct some mobile visitors toward an iOS exploit chain. Important limits: a website loading a poisoned third-party script does not prove that the website's own servers were breached, that every visitor received every payload, or that a card, cookie, payment, or device was successfully compromised. Reuters could not establish successful exploitation at every organization or the total impact. Report URI observed roughly $7,000 reaching attacker-controlled cryptocurrency wallets, but researchers have not publicly established that all of those funds came from affected visitors. Optimizely has not published a complete victim count, technical root-cause report, or total exposure window. The attacker has not been identified.
How the technology works
At a safe defensive level, Optimizely Web Experimentation allows customers to load project-specific JavaScript into webpages for testing and personalization. Because that script is delivered from a trusted Optimizely content-delivery domain and executes inside the customer's page, it can interact with the same page content and browser context that ordinary site code can reach. The attacker abused an Optimizely workflow to add hostile code to selected customer projects. Websites continued loading those project files as a normal dependency, so visitors' browsers executed the injected code without the affected brands necessarily changing their own applications. This is a software supply-chain attack: one trusted service became a delivery path into many unrelated sites. Impact depended on the page, the visitor's device, and what the visitor did. A payment-address replacement only causes loss if a person subsequently approves a payment to the substituted address. A skimmer can collect only data visible to its execution context; HttpOnly cookies and isolated cross-origin payment frames have additional protections. A mobile redirect or exploit attempt is not proof that an iPhone or iPad was successfully compromised. This article omits payload code, domains, wallet addresses, exploit details, and reusable instructions.
Who is affected?
Organizations that loaded the altered Optimizely project files are directly affected and must determine which pages, visitors, and time periods were exposed. Report URI's sample associated poisoned snippets with 178 organizations, including widely visited media, technology, financial, retail, travel, and communications properties. That measurement is a research finding, not Optimizely's confirmed customer total, and it should not be converted into a visitor or victim count. People who visited an affected page may face different risks depending on the page and their activity. Someone who entered payment-card data, copied or approved a cryptocurrency address, or used an iPhone or iPad during the exposure window warrants greater attention than someone who only read a static page. Public evidence does not establish that every visitor had information stolen. Customers of affected brands should wait for specific notices rather than assume that an unrelated account or transaction was compromised solely because the organization's name appeared in a research list.
What should you do?
Website operators should treat this as a client-side incident, not only a vendor ticket. Preserve historical copies and hashes of every third-party script, content-security-policy report, web application firewall record, DNS and proxy log, checkout telemetry, and browser-monitoring event before routine retention removes evidence. Identify every page that loaded Optimizely during the relevant period, with special attention to login, account, checkout, payment, cryptocurrency, identity, and support pages. Review Optimizely project JavaScript, account users, sessions, tokens, audit logs, and recent configuration changes; rotate affected credentials and revoke unfamiliar sessions. Confirm that the current script is clean, but do not assume removing it reverses earlier exposure or clears browser and intermediary caches. Use a restrictive Content Security Policy, Subresource Integrity where operationally possible, dependency allowlists, change alerts, and client-side script monitoring. Minimize the personal and payment data accessible to page scripts, keep payment entry inside isolated provider-hosted frames, and require independent approval for third-party code changes on sensitive pages. Organizations with evidence of exposure should notify affected people with the exact pages, dates, data types, and actions required. Individuals who entered card details or approved a cryptocurrency transfer on a site that later confirms exposure should contact the card issuer or payment provider using an independently verified channel, monitor transactions, and replace the card when advised. Clear active sessions and change a password only if the affected organization says authentication data or sessions may have been exposed; never follow a reset link in an unsolicited breach message. Keep iOS and browsers fully updated, and seek professional device review if a confirmed notice or device behavior supports compromise.
My analysis
My Analysis - opinion and inference: this incident shows the privacy cost of invisible third-party code. A visitor may believe they are dealing only with a bank, news outlet, retailer, or software company, while scripts from several outside services can read and alter parts of the page. My inference is that supply-chain attacks will increasingly target experimentation, analytics, tag-management, chat, and personalization platforms because one successful change can reach many trusted brands. That is a defensive risk assessment, not attribution of this campaign. Optimizely acted appropriately by acknowledging the exploited workflow, removing injected code, and securing accounts, but customers and the public still need a precise timeline, affected-project notifications, root cause, cache analysis, and independent evidence that the vulnerable path is closed. From a privacy-first viewpoint, websites should load far less third-party JavaScript on login, payment, health, financial, and identity pages. Consent banners are not enough when visitors cannot meaningfully understand which scripts can access which fields. Organizations should publish dependency inventories, isolate payment entry, limit script privileges, retain short and security-focused audit evidence, and delete unrelated browsing data rather than expanding surveillance in response. The goal is verifiable code integrity and data minimization, not indefinite recording of everything visitors do.
Why this matters
Cyber incidents often sound distant or overly technical. The important question is whether the same weakness, behavior, surveillance power, or exposure exists in systems you use. Facts and opinion are separated here so you can judge both clearly.
Facts, claims, and unknowns are separated above. Details may change as investigations and official statements develop.
Optimizely service status: Web Experimentation security incident Reuters: popular websites subverted to target payments and iPhone users Report URI: malicious Optimizely scripts found across 178 organizations SecurityWeek: Optimizely vulnerability exploited to serve malware BleepingComputer: Optimizely supply-chain attack delivered malicious scripts