News Application Security
Optimizely Signup Flaw Let an Attacker Inject Malicious JavaScript Into Customer Sites
Optimizely says a flaw in its Web Experimentation signup flow let an attacker impersonate users and plant malicious JavaScript in customer projects. Report URI, which documented the campaign, found infected snippets at 178 organisations in its own crawl.

Key takeaways
- Optimizely attributes the intrusion to a signup-flow flaw that allowed user impersonation, and says it was not a credentials breach.
- Report URI found 188 infected snippets across 178 organisations in a crawl of 1,611, and says the real number is likely higher.
- The payload was served from Optimizely's legitimate CDN origin, so script host allowlisting did not stop it.
- Report URI says only 24 of the organisations whose CSP it evaluated, 15% by its count, had a policy that blocked the payload.
- Customers should review Project JavaScript, rotate access and API tokens, and treat card data entered on 16 November as potentially exposed.
Optimizely says an attacker exploited a flaw in the Web Experimentation account signup flow to impersonate users on targeted customer accounts and insert malicious JavaScript into those customers' projects. The code was then served to visitors of those customers' sites from Optimizely's own snippet.
What Optimizely says #
In a status update on 18 November, the company dated the intrusion to 16 November and described it as exploitation of a signup-flow flaw, not a credentials breach. Optimizely states that less than 5% of its customers were impacted, that it closed the vulnerability within three hours of detection, that it removed the injected code from all affected projects, and that no other Optimizely product was affected. Those are vendor claims. Optimizely has not published a CVE or a count of affected customers.
What Report URI found #
Report URI, which found and documented the campaign, says it fetched 1,611 distinct Optimizely snippets and found 188 infected, belonging to 178 organisations. That is Report URI's own crawl sample, not a total victim count, and it says the real number is likely higher. Its list of affected organisations includes Zoom, BBC, CNN, Salesforce, GitLab, IKEA, HSBC, Equifax and Ledger.
According to Report URI, the malicious code sat in the customer-editable Project JavaScript field and was still served from cdn.optimizely.com. It says this was not CDN cache poisoning. Its timeline puts the first injection it observed at 04:21 UTC on 16 November, with the payload rebuilt 26 times that day, and says every infected file it tracked was clean by 23:11 UTC and stayed clean.
Report URI's analysis describes a payload that swapped cryptocurrency addresses, skimmed card number, expiry and CVV from the site's own forms, and stole cookies and screenshots. Hosted payment iframes were out of its reach. Report URI also reports that the payload loaded iOS exploit kits it identifies as Coruna and DarkSword. SecurityWeek quotes Hudson Rock as saying the evidence "does not establish a zero-day, successful device exploitation", so do not read that as confirmed device compromise.
Why it matters for appsec #
A third-party tag with write access to every page is part of your attack surface. The payload came from the vendor's legitimate origin, so allowlisting the script host did nothing. Report URI crawled 256 hosts belonging to affected organisations and evaluated their Content Security Policy. In its results, 24 organisations, 15% by its count, had a policy that blocked the payload.
What to do #
Report URI's guidance for Optimizely customers:
- Review Project JavaScript and experiment custom code for anything you did not write.
- Review and rotate account access and API tokens.
- Deploy CSP with a restricted connect-src.
- Treat card data entered on your site on 16 November as potentially exposed.
Beyond this incident, audit which third-party scripts can modify your pages and keep payment fields in hosted iframes.
Sources
- Optimizely Service Status - Web Experimentation Security Incident, Optimizely
- World's Largest Brands Infected With Malware Via Optimizely, Report URI
- Optimizely Vulnerability Exploited to Serve Malware on Major Websites - SecurityWeek, SecurityWeek
- Website management platform Optimizely confirms hackers put malicious code into customer sites | The Record from Recorded Future News, The Record
Questions this raises
- How did the attacker get code into Optimizely customer sites?
- Optimizely says an unauthorized third party exploited a flaw in the Web Experimentation account signup flow, used it to impersonate users on targeted customer accounts, and inserted malicious JavaScript into those customers' projects. Report URI says the code sat in the Project JavaScript field and was served from Optimizely's CDN.
- How many organisations were affected?
- There is no confirmed total. Optimizely states that less than 5% of its customers were impacted, which is a vendor claim. Report URI found infected snippets belonging to 178 organisations in its own crawl of 1,611 snippets and says the real number is likely higher.
- Were iPhones compromised through this attack?
- That is not established. Report URI reports that the payload loaded iOS exploit kits it identifies as Coruna and DarkSword. SecurityWeek quotes Hudson Rock as saying the evidence does not establish a zero-day or successful device exploitation.
- What should Optimizely Web Experimentation customers do?
- Report URI advises reviewing Project JavaScript and experiment custom code for code you did not write, rotating account access and API tokens, deploying CSP with a restricted connect-src, and treating card data entered on 16 November as potentially exposed.