Malicious Code Injection in spare_tiglon_z3n Package: A Threat to npm Users
Summary
MAL-2025-90720: Malicious code in spare_tiglon_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 spare_tiglon_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package, like many others in this campaign, is designed to manipulate the npm registry by generating and publishing derivative packages with randomized names. Its primary function is to inflate developer reputation scores for token rewards, which poses a significant risk to the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the spare_tiglon_z3n package originates from its malicious design, which includes scripts that modify the package.json file to remove private flags and change version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only compromises the security of the affected packages but also affects the overall reliability of the npm ecosystem, potentially leading to the installation of malicious code by unsuspecting developers.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall spare_tiglon_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 spare_tiglon_z3n package and any other packages associated with the tea.xyz token reward campaign. Regularly monitor your dependencies and remove any suspicious packages.
Conclusion
The spare_tiglon_z3n package poses a significant threat to npm users due to its malicious code designed to manipulate the npm registry. It is crucial to remove this package from your projects and monitor your dependencies for any suspicious activity. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for spare_tiglon_z3n →
FAQ
The spare_tiglon_z3n package is an npm package that is part of a malicious campaign designed to inflate developer reputation scores by flooding the npm registry with derivative packages.
The vulnerability can lead to the installation of malicious code, compromising the security of your project and potentially affecting the integrity of the npm ecosystem.
If you have installed the spare_tiglon_z3n package, you should uninstall it immediately using the command npm uninstall spare_tiglon_z3n.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can also check your application against known vulnerabilities using the Vulert playground.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
