Malicious Code Vulnerability in sacred_bat_z3n Package
Summary
MAL-2025-108309: Malicious code in sacred_bat_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 sacred_bat_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. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the package's malicious payload, which modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially impacting other developers by inflating reputation scores through deceptive practices.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sacred_bat_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 sacred_bat_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.
Conclusion
The sacred_bat_z3n package contains a serious vulnerability that can compromise the integrity of the npm registry. It is crucial to uninstall this package and monitor your project for any unauthorized changes. Utilizing tools like Vulert can help you stay informed about potential vulnerabilities in your dependencies.
See every vulnerability recorded for sacred_bat_z3n →
FAQ
The sacred_bat_z3n package is an npm package that is part of a token reward campaign and is designed to automatically publish derivative packages.
The vulnerability can lead to the pollution of the npm registry, potentially affecting your project's dependencies and reputation.
You should uninstall the package immediately using the command npm uninstall sacred_bat_z3n and check for any dependencies that may be affected.
Yes, you can use Vulert to monitor your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
