Polyfill.io Supply-Chain Attack (2024)
Qu'est-ce que 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.
● Exemples
- 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.
● Questions fréquentes
Qu'est-ce que 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. Cette notion relève de la catégorie Attaques et menaces en cybersécurité.
Que signifie 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.
Comment fonctionne Polyfill.io Supply-Chain Attack (2024) ?
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.
Comment se défendre contre Polyfill.io Supply-Chain Attack (2024) ?
Les défenses contre Polyfill.io Supply-Chain Attack (2024) combinent habituellement des contrôles techniques et des pratiques opérationnelles, comme détaillé dans la définition ci-dessus.
Quels sont les autres noms de Polyfill.io Supply-Chain Attack (2024) ?
Noms alternatifs courants : Polyfill.io attack, Funnull CDN attack.
● Termes liés
- attacks№ 1234
Attaque de la chaîne d'approvisionnement
Attaque qui compromet un fournisseur de logiciel, de matériel ou de services de confiance afin d'atteindre ses clients en aval.
- appsec№ 1186
Sécurité de la chaîne d'approvisionnement logicielle
Discipline qui protège chaque maillon de la chaîne de production logicielle - source, dépendances, build, signature, distribution et déploiement - contre les manipulations, le code malveillant et la perte d'intégrité.
- appsec№ 1232
Intégrité des sous-ressources (SRI)
Mécanisme du navigateur qui vérifie un hash cryptographique d'un script ou d'une feuille de styles tiers avant son exécution, empêchant tout fichier altéré de s'exécuter.
- attacks№ 714
Attaque Magecart
Famille d'attaques de skimming numerique consistant a injecter du JavaScript malveillant dans les pages de paiement de sites e-commerce pour voler les donnees de carte au moment de la saisie.
- network-security№ 169
Securite CDN
La securite CDN s'appuie sur le edge global d'un reseau de distribution de contenu — terminant TLS pres des utilisateurs — pour appliquer protection DDoS, WAF, gestion des bots et hygiene TLS.
- privacy№ 1263
Cookie tiers
Cookie déposé par un domaine différent de celui affiché dans la barre du navigateur, historiquement utilisé pour pister les utilisateurs entre sites.