Malicious Code Injection in aggregate_mockingbird_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-99241: Malicious code in aggregate_mockingbird_z3n (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The package 'aggregate_mockingbird_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated scripts that modify package attributes and republish variants continuously.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the 'aggregate_mockingbird_z3n' package. This payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to pollution of the npm registry. The malicious scripts are designed to create and publish numerous derivative packages, potentially compromising the integrity of the npm ecosystem and affecting developers who rely on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall aggregate_mockingbird_z3nIf 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
As a temporary workaround, you can avoid using the 'aggregate_mockingbird_z3n' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your package dependencies using tools like npm audit.
Conclusion
The 'aggregate_mockingbird_z3n' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package attributes and flood the registry. It is essential for developers to remove this package and utilize tools like Vulert for ongoing monitoring of vulnerabilities.
See every vulnerability recorded for aggregate_mockingbird_z3n →
FAQ
The malicious code can lead to the pollution of the npm registry, affecting the integrity of the ecosystem and potentially compromising other packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.
If you have installed this package, it is crucial to remove it immediately and check for any other affected packages in your project.
Yes, tools like npm audit can help identify vulnerabilities in your dependencies. Additionally, Vulert provides real-time monitoring for open-source vulnerabilities.
Regularly audit your dependencies, keep your packages updated, and use trusted sources for package installations to minimize the risk of vulnerabilities.
