Malicious Code Injection in working_tarantula_z3n Package
Summary
MAL-2025-97409: Malicious code in working_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 working_tarantula_z3n package is part of the npm ecosystem, primarily used for JavaScript development. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with packages that inflate developer reputation scores. This package, like others in the campaign, contains scripts that automatically generate and publish derivative packages, potentially compromising the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the working_tarantula_z3n package stems from its inclusion in a malicious campaign aimed at manipulating the npm registry. The package contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only pollutes the npm registry but also poses a risk of unintentional installation of malicious packages by developers who may not be aware of the underlying issues. The malicious payload can lead to security breaches, data leaks, and a compromised development environment.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall working_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 workaround, avoid using the working_tarantula_z3n package and monitor your project's dependencies for any malicious activity. You can also use tools like Vulert to check for vulnerabilities in your package-lock.json file. To do this, visit the Vulert playground at https://vulert.com/scanner and upload your package-lock.json file to see if your application is affected by this vulnerability.
Conclusion
The working_tarantula_z3n package is implicated in a malicious campaign that compromises the integrity of the npm registry. Developers should take immediate action to remove this package from their projects and monitor for any vulnerabilities using tools like Vulert. Staying informed and proactive is essential to maintaining a secure development environment.
See every vulnerability recorded for working_tarantula_z3n →
FAQ
The working_tarantula_z3n package is an npm package associated with a token reward campaign that generates and publishes derivative packages to inflate developer reputation scores.
The vulnerability can lead to the installation of malicious packages, compromising your project's security and potentially exposing sensitive data.
You should uninstall the working_tarantula_z3n package immediately using the command npm uninstall working_tarantula_z3n.
You can use Vulert to monitor your project for open-source vulnerabilities by checking your package-lock.json file at Vulert Scanner.
Currently, there is no patched version available for the working_tarantula_z3n package. It is recommended to uninstall it until a secure version is released.
