Malicious Code Vulnerability in static_baboon_z3n Package
Summary
MAL-2025-90743: Malicious code in static_baboon_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 static_baboon_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and security.
Vulnerability Detail
The vulnerability originates from the package's inclusion in a campaign that floods the npm registry with malicious packages. It contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially affecting other 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 static_baboon_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 static_baboon_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time.
Conclusion
The static_baboon_z3n package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package from your project and monitor your dependencies for vulnerabilities to maintain the integrity of your applications.
See every vulnerability recorded for static_baboon_z3n →
FAQ
The static_baboon_z3n package is an npm package associated with a token reward campaign that automates the generation of derivative packages.
The vulnerability can lead to the pollution of the npm registry and may affect your project's integrity by introducing malicious code.
You should uninstall the static_baboon_z3n package immediately and check your project for any dependencies that may have been affected.
Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
