Malicious Code Detected in outer_squirrel_z3n: npm Package Vulnerability
Summary
MAL-2025-89335: Malicious code in outer_squirrel_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 'outer_squirrel_z3n' package 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 publishing scripts, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability in 'outer_squirrel_z3n' originates from its association with the tea.xyz token reward campaign. The package contains scripts that automatically modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these malicious packages, potentially leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall outer_squirrel_z3n
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
As a temporary workaround, you can remove the 'outer_squirrel_z3n' package from your project by executing: 'npm uninstall outer_squirrel_z3n'. This will prevent any malicious code from executing in your application until a fix is applied.
Conclusion
The 'outer_squirrel_z3n' package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and applications. It is crucial to take immediate action by updating or removing the package to safeguard your projects. Utilizing tools like Vulert can help in monitoring and managing open-source vulnerabilities effectively.
See every vulnerability recorded for outer_squirrel_z3n →
FAQ
The vulnerability involves malicious code that modifies package.json and floods the npm registry with derivative packages.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
Using this package can lead to security breaches, as it may introduce malicious code into your application and compromise the integrity of the npm registry.
Regularly monitor your dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.
If an immediate update is not possible, consider removing the package from your project as a temporary measure to mitigate risks.