Malicious Code Injection in historic_zebra_z3n Package
Summary
MAL-2025-103731: Malicious code in historic_zebra_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 historic_zebra_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package was identified as part of a malicious campaign that aimed to manipulate the npm registry by flooding it with derivative packages. The primary functionality of this package is to serve as a token reward mechanism, but it has been compromised to include harmful scripts that alter package metadata.
Vulnerability Detail
The vulnerability originates from the historic_zebra_z3n package being part of a malicious campaign associated with the tea.xyz token reward initiative. The package contains scripts that automatically modify the package.json file, removing private flags, changing version numbers, and generating random package names. This leads to the continuous republishing of these variants, which pollutes the npm registry and can inflate developer reputation scores fraudulently. The ramifications include potential security risks for developers who unknowingly use these compromised packages, as well as a degradation of the npm ecosystem's integrity.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall historic_zebra_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 workaround, you can temporarily avoid using the historic_zebra_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 using tools like Vulert, which alerts you to open-source vulnerabilities in real-time.
Conclusion
The historic_zebra_z3n package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their projects. It is crucial to remove this package and monitor your dependencies for vulnerabilities to maintain the integrity of your software.
See every vulnerability recorded for historic_zebra_z3n →
FAQ
The historic_zebra_z3n package is an npm package that was part of a malicious campaign aimed at manipulating the npm registry.
The vulnerability can lead to unauthorized modifications of your package.json file, potentially compromising your project's integrity and security.
You should uninstall the historic_zebra_z3n package immediately and monitor your project for any unauthorized changes.
Yes, you can use Vulert, which monitors your package-lock.json file for vulnerabilities and alerts you in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
