Malicious Code Injection in tropical_wolverine_z3n: A Threat to npm Packages
Summary
MAL-2025-109847: Malicious code in tropical_wolverine_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 package 'tropical_wolverine_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts that automatically generate and publish derivative packages, compromising the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'tropical_wolverine_z3n' stems from its malicious code that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants, leading to pollution of the npm registry. This can inflate developer reputation scores fraudulently and potentially introduce security risks to applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tropical_wolverine_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 avoid using the 'tropical_wolverine_z3n' package and replace it with a trusted alternative. Always verify the integrity of packages before including them in your project.
Conclusion
The 'tropical_wolverine_z3n' package poses a significant risk due to its malicious code that manipulates package metadata and floods the npm registry. It is essential to remove this package and adopt best practices for dependency management to safeguard your applications.
See every vulnerability recorded for tropical_wolverine_z3n →
FAQ
The vulnerability can lead to the pollution of the npm registry and compromise the integrity of applications that depend on this package.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.
You should uninstall the package immediately using 'npm uninstall tropical_wolverine_z3n' and review your project's dependencies for any other potentially malicious packages.
Yes, consider using well-established and trusted packages that serve similar functionalities without the associated risks.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and only install packages from reputable sources.
