Polyfill.io Supply-Chain Attack (2024)
What is Polyfill.io Supply-Chain Attack (2024)?
Polyfill.io Supply-Chain Attack (2024)A June 2024 supply-chain compromise in which the polyfill.io CDN, after being acquired by a Chinese-linked company, began serving malicious JavaScript to an estimated 100,000+ sites embedding its widely-used `<script>` tag.
The Polyfill.io supply-chain attack is a 2024 incident centered on `cdn.polyfill.io`, a long-running free service that returned per-browser JavaScript polyfills. In February 2024 the original maintainer (Andrew Betts) publicly warned that the polyfill.io domain and GitHub account had been transferred to a new operator, 'Funnull', without his involvement, and recommended sites stop using it. The warning was largely ignored. In June 2024, Sansec and other researchers confirmed that the CDN had begun injecting malicious code targeting mobile users — redirecting them to scam sites and credential-harvest pages — and that the same domain was implicated in similar incidents against `bootcss.com`, `bootcdn.net`, and `staticfile.org`. Estimates of affected sites range from 100,000 to over 380,000, including high-profile names. Cloudflare and Google rolled out automatic mitigations (URL rewrites to safe mirrors, ad-blocking), Namecheap suspended the domain, and the incident is widely cited as a case study in the dangers of free third-party CDNs and untracked ownership changes.
● Examples
- 01
A retailer including `<script src="https://cdn.polyfill.io/v2/polyfill.min.js">` for legacy IE support began serving redirect-to-scam JS to mobile users overnight.
- 02
Defenders responded by migrating to self-hosted polyfills or to Cloudflare's safe mirror, then adopting subresource integrity for any remaining third-party scripts.
● Frequently asked questions
What is Polyfill.io Supply-Chain Attack (2024)?
A June 2024 supply-chain compromise in which the polyfill.io CDN, after being acquired by a Chinese-linked company, began serving malicious JavaScript to an estimated 100,000+ sites embedding its widely-used `<script>` tag. It belongs to the Attacks & Threats category of cybersecurity.
What does Polyfill.io Supply-Chain Attack (2024) mean?
A June 2024 supply-chain compromise in which the polyfill.io CDN, after being acquired by a Chinese-linked company, began serving malicious JavaScript to an estimated 100,000+ sites embedding its widely-used `<script>` tag.
How does Polyfill.io Supply-Chain Attack (2024) work?
The Polyfill.io supply-chain attack is a 2024 incident centered on `cdn.polyfill.io`, a long-running free service that returned per-browser JavaScript polyfills. In February 2024 the original maintainer (Andrew Betts) publicly warned that the polyfill.io domain and GitHub account had been transferred to a new operator, 'Funnull', without his involvement, and recommended sites stop using it. The warning was largely ignored. In June 2024, Sansec and other researchers confirmed that the CDN had begun injecting malicious code targeting mobile users — redirecting them to scam sites and credential-harvest pages — and that the same domain was implicated in similar incidents against `bootcss.com`, `bootcdn.net`, and `staticfile.org`. Estimates of affected sites range from 100,000 to over 380,000, including high-profile names. Cloudflare and Google rolled out automatic mitigations (URL rewrites to safe mirrors, ad-blocking), Namecheap suspended the domain, and the incident is widely cited as a case study in the dangers of free third-party CDNs and untracked ownership changes.
How do you defend against Polyfill.io Supply-Chain Attack (2024)?
Defences for Polyfill.io Supply-Chain Attack (2024) typically combine technical controls and operational practices, as detailed in the full definition above.
What are other names for Polyfill.io Supply-Chain Attack (2024)?
Common alternative names include: Polyfill.io attack, Funnull CDN attack.
● Related terms
- attacks№ 1234
Supply Chain Attack
An attack that compromises a trusted third-party software, hardware, or service provider in order to reach its downstream customers.
- appsec№ 1186
Software Supply Chain Security
The discipline of protecting every link of the software production chain - source, dependencies, build, signing, distribution, and deployment - against tampering, malicious code, and integrity loss.
- appsec№ 1232
Subresource Integrity (SRI)
A browser mechanism that verifies a cryptographic hash of a script or stylesheet loaded from a third party before executing it, preventing tampered files from running.
- attacks№ 714
Magecart Attack
A category of digital-skimming attacks in which criminals inject malicious JavaScript into e-commerce checkout pages to steal payment-card data as customers enter it.
- network-security№ 169
CDN Security
CDN security uses the global edge of a content delivery network — terminating TLS close to users — to enforce DDoS protection, WAF, bot management, and TLS hygiene.
- privacy№ 1263
Third-Party Cookie
A cookie set by a domain different from the one in the browser's address bar, historically used to track users across websites.