Malicious Code Detected in ac-polyfills Package - Security Alert

ac-polyfills Updated 06 Feb 2026

Summary

06/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-782: Malicious code in ac-polyfills (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The ac-polyfills package is a JavaScript library used in Node.js applications to provide polyfills for various ECMAScript features. It is commonly utilized to ensure compatibility across different environments. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that depend on it.

Vulnerability Detail

The vulnerability in the ac-polyfills package originates from the inclusion of malicious code that can compromise the integrity of applications using this library. This code can lead to unauthorized access, data breaches, or other malicious activities. The specific version affected is any version starting from 0, as indicated by the semantic versioning range. The malicious code was identified by Amazon Inspector, highlighting the importance of monitoring dependencies for security threats.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall ac-polyfills

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

If an immediate update is not possible, consider removing the ac-polyfills package from your project and replacing it with an alternative library that provides similar functionality without the security risks. You can do this by running:

npm uninstall ac-polyfills

Then, install a safer alternative package.

Conclusion

The ac-polyfills package has been identified as containing malicious code, posing a significant security threat to applications that utilize it. It is essential to update to a secure version or consider alternative libraries to mitigate risks. Regular monitoring of dependencies is crucial for maintaining application security.

See every vulnerability recorded for ac-polyfills →

Share this vulnerability

FAQ

ac-polyfills is a JavaScript library that provides polyfills for ECMAScript features, ensuring compatibility across different JavaScript environments.

The malicious code was detected by Amazon Inspector, a security tool that scans packages for vulnerabilities and malicious content.

Using the compromised package can lead to unauthorized access, data breaches, and other security incidents that can affect your application and its users.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software. It requires only the package-lock.json file for analysis.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall ac-polyfills

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback