Optimizely's abandoned CDN domain hijacked, pushed malware on Zoom and GitLab

4 min read 1 source clear_take
├── "This is 'supply-chain decay' — a systemic, nameable failure mode of third-party script dependencies rotting through corporate reorganizations"
│  └── top10.dev editorial (top10.dev) → read below

The editorial frames this as the third major variant of the same attack class in 2025 (after Polyfill.io and the Cloudflare-tunnel-abuse campaign), arguing the pattern is now clear enough to name. The root cause is organizational — Statsig being spun out, re-acquired, and re-organized inside Optimizely caused operational ownership of subdomains to be 'dropped on the floor,' leaving DNS pointing at reclaimable infrastructure.

├── "The attack reveals how toothless CSP whitelisting is when the whitelisted domain itself gets hijacked"
│  ├── Scott Helme / Report-URI team (Report-URI blog) → read

Helme's write-up documents that attacker-controlled JavaScript executed with full first-party privileges on Zoom, GitLab, FanDuel, LinkedIn marketing pages, and Shopify storefronts — all because those sites had whitelisted cdn.statsig.io in their CSP. The payload fingerprinted visitors, checked for admin cookies, and redirected to SSO-mimicking credential harvesters, demonstrating that CSP allowlists provide zero protection once the allowlisted origin is compromised.

│  └── @kristjansson (Hacker News, 263 pts) → view

By surfacing the Report-URI post to 263 points on HN under the framing 'Optimizely compromised, served malware on Zoom, GitLab,' the submitter emphasized the scale of the first-party-privilege blast radius across Fortune 500 properties as the newsworthy angle.

└── "Copy-paste integration culture is a latent liability — stale snippets from years-old guides remain live attack surface"
  └── top10.dev editorial (top10.dev) → read below

The editorial highlights 'a long tail of Shopify storefronts that had copy-pasted the snippet from a 2022 integration guide' as a key part of the affected population. This implicates the broader industry practice of embedding third-party script tags once and never auditing them, meaning a vendor's internal reorg years later can silently convert thousands of sites into malware distributors.

What happened

On November 14, Scott Helme's Report-URI team published evidence that `cdn.statsig.io` — a domain Optimizely had controlled as part of its Statsig experimentation product — had lapsed, been re-registered by an unknown party, and was serving actively malicious JavaScript to every site still embedding the script tag. The affected properties read like a Fortune 500 roll-call: Zoom, GitLab, FanDuel, Microsoft-owned LinkedIn marketing pages, and a long tail of Shopify storefronts that had copy-pasted the snippet from a 2022 integration guide.

The mechanics are depressingly simple. Statsig was spun out of, then re-acquired by, then re-organized inside Optimizely over the last 18 months. During one of those shuffles the operational ownership of `statsig.io` subdomains got dropped on the floor. DNS stayed pointed at a CloudFront distribution that no longer belonged to anyone at Optimizely. When the underlying bucket/origin was reclaimable, the attacker claimed it and started shipping their own payload under the same URL every integrator was already whitelisting in their CSP.

Report-URI's write-up shows the payload fingerprinting the visitor, checking for admin cookies, and in some variants redirecting to credential-harvesting pages mimicking the host site's SSO. By the time the post went public, the script had been live for an unknown number of hours — Helme's team says "at least overnight" and possibly longer. Optimizely acknowledged the issue within a few hours of the post and nulled the DNS, but every browser that loaded one of the affected pages during the window executed attacker-controlled JavaScript with full first-party privileges.

Why it matters

This is the third major variant of the same attack class in 2025, after the Polyfill.io takeover in January and the Cloudflare-tunnel-abuse campaign in August. The pattern is now clear enough to name: supply-chain decay — the slow, unsupervised rotting of third-party script dependencies that no one on either side of the integration remembers signing up for.

The uncomfortable part is that none of the usual mitigations caught it. Subresource Integrity (SRI) hashes would have, but basically nobody uses SRI for analytics scripts because the vendors update them continuously and SRI breaks on every rev. Content Security Policy didn't help because the domain was explicitly allow-listed — that's the whole point of a CSP whitelist. Even careful customers who pinned the exact subdomain in their CSP got owned, because the attacker took over that exact subdomain. The security control was doing exactly what it was configured to do.

The community reaction on Hacker News (263 points and climbing) split predictably. One camp — the Troy Hunt / Scott Helme school — argues this is a vendor hygiene failure and the cure is radical: self-host every third-party script, treat any `