Malicious Code Injection in previous_tarantula_z3n Package
Summary
MAL-2025-96011: Malicious code in previous_tarantula_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 previous_tarantula_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, often with randomized names, to inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity.
Vulnerability Detail
The vulnerability in the previous_tarantula_z3n package originates from its association with a malicious campaign that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to significant security risks, including unauthorized access to sensitive data and the potential for further exploitation of affected systems.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall previous_tarantula_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 measure, you can remove the previous_tarantula_z3n package from your project by executing: npm uninstall previous_tarantula_z3n. This will prevent the malicious code from executing until a secure version is available.
Conclusion
The previous_tarantula_z3n package has been identified as containing malicious code that poses significant security risks. It is crucial to take immediate action by updating or removing the package to protect your application from potential exploitation. Utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.
See every vulnerability recorded for previous_tarantula_z3n →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.
The vulnerability can lead to unauthorized modifications in your package.json file and may expose your application to further security risks.
Yes, you can use Vulert, which monitors and alerts 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 for vulnerabilities without needing to sign up.
If an immediate update is not possible, consider uninstalling the package as a temporary workaround to mitigate risks.
