Malicious Code Injection in automatic_shrew_z3n: A Threat to npm Packages
Summary
MAL-2025-93307: Malicious code in automatic_shrew_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 'automatic_shrew_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is linked to the tea.xyz token reward campaign, notorious for flooding the npm registry with malicious packages. Its primary functionality revolves around generating and publishing derivative packages, but it has been compromised to include harmful scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability in 'automatic_shrew_z3n' stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. This behavior is part of a broader scheme to inflate developer reputation scores for token rewards, posing significant risks to developers who may unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall automatic_shrew_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 'automatic_shrew_z3n' package altogether. If it is already in use, consider replacing it with a trusted alternative that provides similar functionality without the associated risks.
Conclusion
The 'automatic_shrew_z3n' package poses a significant risk due to its malicious code designed to manipulate npm package metadata. It is essential to remove this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for automatic_shrew_z3n →
FAQ
The main issue is that it contains malicious code that alters package metadata and floods the npm registry with compromised packages.
You can use Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
You should remove the 'automatic_shrew_z3n' package from your project and check for any dependencies that may have been affected.
Yes, consider using reputable packages that offer similar functionality without the risks associated with malicious code.
Vulert uses the package-lock.json file to monitor and alert you in real-time about open-source vulnerabilities, ensuring your software remains secure.
