Optimizely's 188 Infected Snippets Put Customer Code Authority on Trial

By
CTOL Staff Reporter
1 min read

An exploited vulnerability carried hostile JavaScript to 178 organisations. The enterprise cost depends on who held the power to change their code.

At 04:21 UTC on 16 November 2026, an Optimizely snippet for the BBC was first seen carrying an attacker's JavaScript. The file still came from cdn.optimizely.com, wearing Optimizely's certificate, with its ordinary code intact. The browser received the update from a supplier the website already trusted. With 188 infected snippets across 178 organisations, we would pass on a platform that fails to separate customer code editing rights. An attack that reaches the visitor through a trusted supplier has already crossed the expensive boundary.

Optimizely's 17 November 2026 incident statement confirms that an unauthorised party exploited a vulnerability in Web Experimentation and added malicious JavaScript to customer projects. The zero day description is unproven. Write Authority Blast Radius is the number of customer projects that a shared editing privilege can turn into live attack surfaces. Its test is the number of projects modified through a single cross customer writing route. Once a marketing platform can rewrite production browser code, its access rights deserve the scrutiny normally reserved for production systems.

Report URI fetched 1,611 distinct snippets and found 188 infected, belonging to 178 organisations. The 188 over 1,611 is 11.7%, a modest share of the observed scripts with an unusually wide customer reach. Among those organisations were BBC, CNN, Zoom, Salesforce, GitLab, IKEA, HSBC and Equifax. Banking and finance accounted for 32 organisations; technology and software businesses for 23. The average, 188 over 178, is 1.06 infected snippets per organisation. A content field in one supplier's product placed a diverse collection of businesses on the same attack path, changing what they must budget for software access control.

The attacker inserted code into Optimizely's Project JavaScript field while leaving the rest of each snippet alone. Optimizely's CDN served what it received, so the trusted certificate was doing its legitimate job. During 16 November 2026 the payload was rebuilt 26 times. Rapid iteration is one of the attractions of experimentation software, and the same ability speeds malicious changes after an attacker gets editing rights. The relevant privilege was the ability to edit Project JavaScript, making the CDN's normal delivery service an attack channel.

Report URI crawled 256 affected organisations' hosts and classified the policy outcome on 159; the other 97 were unclassified. Of those 159, 68 had no Content Security Policy, 50 allowed the payload and data theft, 17 ran the payload but blocked the theft connection, and 24 blocked the payload itself. The 24 over 159 is 15.1% of classified hosts, distinct from the 256 crawled. Cryptocurrency address swapping still worked in the 17 partially protected cases. Report URI's Scott Helme put the trust problem succinctly: "Allowing cdn.optimizely.com was never going to help." The browser's limited defence makes supplier editing permissions an economic risk for the customer buying the platform.

Money creates another tempting false comfort. As of 19:25 UTC, Report URI had traced about $7,040 into the attacker's cryptocurrency wallets. At 13:43 UTC, a skimmer was added to collect payment card numbers, expiry dates and CVVs entered into sites' own forms. Hosted Stripe and Adyen iframes kept those fields outside its reach. On iPhones and iPads the code also delivered Coruna and DarkSword exploit kits. The wallets measure one criminal return; the script's permissions determine the victim's possible bill.

Optimizely has a persuasive response to the incident's immediate economics. Its status update says, "We've fixed the vulnerability and removed the injected code from affected projects." Report URI's timeline had all infected files clean by 23:11 UTC, and recorded only about $7,040 in cryptocurrency receipts as of 19:25. The skimmer was present for about seven to seven and a half hours, until mass clean up around 20:40 to 21:10. Hosted payment iframes shrank its reach further. For a buyer focused on realised cash theft and rapid containment, tighter approvals can seem like a costly cure for a short episode.

Yet the same attack day contained the counterweight. In Report URI's sweep between 19:24 and 19:59 UTC, 186 of the 1,611 fetched snippets carried malicious code. That observation fell inside the skimming window, hours after the card stealing functionality arrived at 13:43. By the clean up around 20:40 to 21:10, visitors had faced a roughly seven hour period of exposure through trusted code. Those 186 infected snippets remained available for delivery during the hours that the containment argument discounts. Fast remediation caps duration; it leaves the concurrent attack surface priced into the decision.

A different outcome appeared in the UK regulator's British Airways decision. In October 2020, the regulator fined British Airways £20 million after a breach potentially affecting about 429,612 customers and staff, including card numbers and CVVs for 244,000 customers. The incident went undetected for more than two months. Optimizely's infected scripts were cleared on 16 November 2026. The comparison concerns the cost of exposure and detection time, rather than a claim that Optimizely faces a £20 million penalty.

The same question about entrusted access appeared at Infoblox. The Register described a compromised data migration vendor with trusted access to Infoblox's SharePoint, through which intruders obtained some customers' NIOS configuration snapshots and employee data. Infoblox said it had 'no indication' its products, cloud services, software updates or release processes were involved. Affected employees were offered a $100 spot bonus and two years of credit monitoring. The asset at risk was the information the supplier was allowed to reach, rather than code released by Infoblox.

The industry's broader numbers encourage a more fashionable explanation. Reuters, citing Marsh's client data on 17 November 2026, counted 105 cyber incidents in the last two weeks of October against 48 in the last two weeks of May, or 105 over 48, equal to 2.19 times. Marsh's cyber leader attributed a significant number to AI, as an opinion. Optimizely's 26 payload revisions on 16 November 2026 required a trusted editing path. Faster attacks matter; code changing authority determines where they land.

Write Authority Blast Radius also sets a price on convenience. The 188 infected snippets across 178 organisations make narrower permissions and customer visible code changes worth buying, even if that slows experiments. A supplier's fastest feature can become its customers' most expensive permission.

We would pass on a vendor that retains broad cross customer code editing rights, because 188 infected snippets reaching 178 organisations create a production risk worth charging against convenience. A root cause update published on Optimizely's incident page by 31 December 2026 would prove us wrong if it identifies zero customer projects modified through shared cross customer authority among the 178 organisations and instead attributes every modification to separately compromised customer credentials.

You May Also Like

This article is submitted by our user under the News Submission Rules and Guidelines. The cover photo is computer generated art for illustrative purposes only; not indicative of factual content. If you believe this article infringes upon copyright rights, please do not hesitate to report it by sending an email to us. Your vigilance and cooperation are invaluable in helping us maintain a respectful and legally compliant community.

Subscribe to our Newsletter

Get the latest in enterprise business and tech with exclusive peeks at our new offerings

We use cookies on our website to enable certain functions, to provide more relevant information to you and to optimize your experience on our website. Further information can be found in our Privacy Policy and our Terms of Service . Mandatory information can be found in the legal notice