Understanding the polyfill.io domain attack

tl;dr: The recent compromise of the polyfill.io domain has triggered a broad-reaching web supply chain attack, impacting over 100,000 websites across various sectors including finance, healthcare, non-profits, academia, and more. To ensure the security of your website, we strongly advise you immediately remove any reference to polyfill.io.

Latest update: 27th June 2024

Sansec, a leader in malware and vulnerability detection, has published the following update:

Namecheap has now set the status of the domain to clientHold, meaning it is no longer active in the DNS removing the current risk.
• Cloudflare has launched an automatic JavaScript URL rewriting service that redirects any link to polyfill.io found in proxied websites to its own version under cdnjs, ensuring site functionality and mitigating supply chain attack risks.
• polyfill.io must still be removed from your estate, but be aware of the risk of breakages so ensure that you use a replacement. You can find alternatives on Cloudflare and Fastly.

The Polyfill.io compromise

The term “polyfill” is commonly used to describe libraries that help resolve inconsistencies across different web browsers, especially older browsers where cutting-edge technologies are not available. Although polyfill.io was not directly related to the concept, it became a trusted resource for finding and adding these polyfills. 

The polyfill.io domain was sold to a Chinese company, Funnull, in February 2024. It was subsequently discovered that polyfill.io started injecting malicious code into its scripts, causing anyone visiting a website using this domain to unknowingly run malware in their browser.

The malicious code injected through cdn.polyfill.io is sophisticated, dynamically generating payloads based on HTTP headers. It activates only on specific mobile devices, avoiding detection by evading admin users and delaying execution. Websites embedding the compromised scripts may inadvertently redirect visitors to malicious sites, exposing them to further risks such as fake Google Analytics links leading to dubious destinations.

Google has been sending warnings about loading third-party JavaScript from domains like polyfill​.​io and is now blocking Google Ads for websites that use the compromised code.

We’re recommending that all references to polyfill.io be removed from estates due to the potential risk from the wider domain. 

Identifying impacted Red Sift customers

Our headless browser, part of Red Sift ASM, conducts a full daily inspection of all websites monitored in our customers’ estates. We then surface the technologies, libraries, and third-party services that are used by the site, including Polyfill, along with any domains that are found in the HTML of the page that these rely on. This information is also utilized in our HTML Content Check (previously known as Mixed Content check).

Having this information readily available allowed us to quickly check all our customers’ accounts and identify the websites containing the compromised domain name. Our Customer Success team then personally notified each affected customer.

What you should do right now

To ensure the security of your website, we strongly advise you to immediately remove any reference to polyfill.io from your estate.

Should you require alternatives for Polyfill hosting, you can find them on Cloudflare and Fastly.

How Red Sift helps to continuously and proactively prevent these attacks

As mentioned, Red Sift ASM is already able to detect the technologies, libraries, and third-party services, including domains, so that customers can quickly discover when malicious technologies and related assets are part of their external attack surface.

Having this capability also meant we could react rapidly to add warnings about dangerous activity to Red Sift. From today, Red Sift ASM customers will:

1) See an Issue created if the poisoned domain polyfill.io is found anywhere in their monitored estate. The issue explains the reason for the critical warning and the steps that are required to remove the risk from the estate.

2) See a warning in our HTML Content check if the poisoned domain polyfill.io is found anywhere in their monitored estate.

Get protected now

To learn more about Red Sift ASM and how it can continuously help you stay on top of these types of threats, why not book a demo. In the meantime, if you have any questions or need assistance, please contact us

PUBLISHED BY

Francesca Rünger-Field

27 Jun. 2024

SHARE ARTICLE:

Categories

Recent Posts

VIEW ALL
Certificates

TLS certificates are changing: What you need to know

Red Sift

Executive summary: TLS certificates are about to get significantly shorter-lived. Starting 15 March 2026, newly issued public-trust certificates will max out at 200 days—and just three years later, that lifespan drops to 47 days. Backed by Google, Apple, and Mozilla, this shift aims to make the web safer through fresher data, faster failover, and…

Read more
DKIM

The hidden threat: How misconfigured DKIM enables replay attacks

Red Sift

Email authentication isn’t just an IT concern. It protects your brand and customers. A single misstep can let attackers spoof your domain, send phishing emails, and destroy customer trust. One of the most dangerous methods? The DKIM replay attack. In this post, we’ll break down how undersigned DKIM keys and related misconfigurations open your…

Read more
BIMI

Why DMARC and BIMI are a business priority

Jack Lilley

Email threats aren’t slowing down, and neither should your authentication strategy. In our recent joint webinar with Marigold, “From DMARC to BIMI: Navigating the New Email Authorization Landscape,” we broke down what today’s evolving standards mean for both security and marketing teams—and how to take action now with our free Red Sift Investigate tool.…

Read more
ASM

Zoom stops zooming: Why active monitoring is essential

Billy McDiarmid

​On April 16, 2025, Zoom experienced a significant global outage that disrupted video conferencing services and access to its website for thousands of users, as well as their corporate email for all their employees. It was quickly identified as a domain name registration status problem. Despite being a critical name for Zoom, somehow, the…

Read more