Optimizely’s web experimentation tag runs on 110,000 websites, according to the technology tracker Wappalyzer, and on about 0.1% of all websites by W3Techs’ count. On 16 November, security firm Report URI found malicious code in 188 of the 1,611 Optimizely snippets it checked, belonging to 178 organisations (our first report).
The card industry’s security standard, PCI DSS, already asks merchants to manage every script that runs on their payment pages and to deploy change-and-tamper detection on them. Both requirements were a best practice until 31 March 2025, after which they became effective, the PCI Security Standards Council says; that date was 595 days before the attack, by our arithmetic.
Business Pill · Verification Cost
An evergreen Business Engineer explainer on verification cost: cheap to make is not cheap to check. It teaches the general idea only and does not discuss Optimizely or this attack.
The key insight: Wappalyzer tracks 110,000 websites using Optimizely, and Report URI found the malicious code in 188 of the 1,611 snippets it checked; PCI DSS requirements 6.4.3 and 11.6.1 on payment-page scripts became effective on 31 March 2025, 595 days before the attack, and 118 of the 159 organisations in Report URI’s policy table, 74% by our arithmetic, had no policy or one that stopped neither the payload nor the theft.
How One Tag Reaches So Many Pages
Each Optimizely Web customer loads a JavaScript snippet from Optimizely’s CDN. iTWire reported that the referenced script updates automatically, so a site can receive changed code without its own developers making a new website release, and that under the default model several experiments in a project share one file.
Report URI says the attacker wrote a loader into the Project JavaScript field of customer projects, custom code that runs on every page, and left the rest of each snippet untouched. It says this was not a CDN cache-poisoning attack: Optimizely’s CDN served exactly what it was given, from a host every affected site already trusted.
Report URI’s 1,611 snippets, found mostly through its own crawl data, equal about 1.5% of the 110,000 sites Wappalyzer tracks, by our arithmetic. A snippet is a project file and a site can load more than one, so the two counts measure different things; the comparison shows scale only. Wappalyzer puts 78% of the sites where it detects Optimizely in the United States.

What the Card Rules Say
The Council’s summary of PCI DSS version 4.0 lists requirement 6.4.3 as: “Manage all payment page scripts that are loaded and executed in the consumer’s browser”. Requirement 11.6.1 is listed as: “A change-and-tamper-detection mechanism is deployed for payment pages”, which the Council’s summary describes as alerting for unauthorized changes to the headers and contents of payment pages as received by the browser.
The Council says the two requirements aim to ensure that payment page scripts are properly authorized, checked for integrity and monitored for tampering. It also says it does not enforce compliance or decide whether a specific implementation is compliant, and tells companies to work with the organisations that manage their compliance programmes, such as acquirers or payment brands.
The rules cover payment pages. Report URI says the injected code ran on every page that loaded an infected snippet, and that its card skimmer read card numbers typed into a site’s own form fields; cards entered in hosted payment iframes, such as Stripe or Adyen, were out of its reach. The sources we read do not say which affected pages took card payments, and we make no finding on any organisation’s compliance.
What Stopped the Code
Report URI evaluated the content security policies of affected organisations against what the payload needed. Its table covers 159 organisations, by our sum: 68 had no policy at all, 50 had a policy that let both the payload and the data theft through, 17 blocked the data theft but not the address swapping, and 24 blocked the payload.
That puts 118 of the 159, or 74%, in the two groups where neither the payload nor the theft was stopped, by our arithmetic. “Allowing cdn.optimizely.com was never going to help”, Report URI says, because the malicious code arrived from the trusted host itself; what separated the protected sites was a restrictive script policy.
StepSecurity, as reported by The Hacker News, advises keeping third-party tags off checkout pages and taking card details through the payment provider’s own fields in a cross-origin iframe. Report URI also says ‘unsafe-eval’, which Optimizely’s own documentation tells customers to allow, let an inline copy of the payload run where the external file was blocked.
The Structural Read
As we read Report URI’s account, a trusted host is the weak point in this attack: the code came from cdn.optimizely.com, so allow-listing that host did nothing, and only restrictive script policies blocked it.
As we read the PCI Council’s summary, its two requirements are about knowing which scripts run on payment pages and noticing when they change, which is the check Report URI says would have exposed this attack.
As we read the counts, Report URI’s 1,611 snippets equal about 1.5% of the 110,000 sites Wappalyzer tracks, by our arithmetic; the units differ, so the share shows scale, not a rate.
Report URI, in its report
“Allowing cdn.optimizely.com was never going to help”
Three Implications
FOR MERCHANTS The PCI Council’s summary lists requirement 6.4.3 as managing all payment page scripts loaded and executed in the consumer’s browser.
FOR SECURITY TEAMS Report URI says the 24 organisations whose policies blocked the payload had a restrictive script-src, and that allowing cdn.optimizely.com did not help.
FOR CHECKOUT DESIGN StepSecurity, as reported by The Hacker News, advises keeping third-party tags off checkout pages and taking card details in the payment provider’s own cross-origin iframe.
The Business Engineer Lens
This story maps onto the Business Engineer framework The AI Embedding Business Model.
The analysis says: “Your product stops being the thing companies buy and becomes the thing other systems assume exists.”
As we read it, a tag on 110,000 sites is exactly that kind of assumed layer, and the Optimizely attack shows what happens when the assumed code changes. The analysis does not discuss this attack.
What Is Not Established
The sources we read do not say which of the affected pages were payment pages, how many card numbers reached the attacker, or whether any acquirer or card brand has asked an affected merchant about the incident. How the attacker gained write access across unrelated customer projects is also not fully explained: an Optimizely spokesperson told Cointelegraph the flaw was in its Experimentation account signup flow, and Report URI says it does not know how the attacker got write access to so many projects.
The Bottom Line
Wappalyzer tracks 110,000 sites using Optimizely, and Report URI found the malicious code in 188 of the 1,611 snippets it could check. PCI DSS has required payment-page script management and tamper detection since 31 March 2025, and in Report URI’s table 118 of 159 affected organisations, 74% by our arithmetic, had no policy or one that stopped neither the payload nor the theft.
95,000+ executives read Business Engineer for the AI strategy frameworks cited by ChatGPT, Claude, and Perplexity.
A note on sourcing. The deployment counts are Wappalyzer’s and W3Techs’ public figures as read on 17 November 2026. The requirement texts and dates come from the PCI Security Standards Council’s Summary of Changes from PCI DSS v3.2.1 to v4.0 and its blog on payment page security. The attack details and policy results come from Report URI’s report of 16 November 2026 by Scott Helme, which we read in full; the snippet mechanics are as reported by iTWire and StepSecurity’s advice as reported by The Hacker News. The 1.5%, 595-day, 159 and 74% figures are our arithmetic. We make no finding on any organisation’s PCI DSS compliance.
Sources: Wappalyzer: Websites using Optimizely (read 17 Nov 2026) · W3Techs: Usage statistics of Optimizely (November 2026) · Report URI (16 Nov 2026) · PCI SSC: PCI DSS v3.2.1 to v4.0 Summary of Changes · PCI SSC blog: Payment Page Security and Preventing E-Skimming · iTWire (17 Nov 2026) · The Hacker News (17 Nov 2026) · Optimizely status page (17 Nov 2026)









