Malicious Code Injection in global_wolverine_z3n: A Threat to npm Packages
Summary
MAL-2025-94702: Malicious code in global_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 'global_wolverine_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is linked to the tea.xyz token reward campaign, notorious for flooding the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing significant risks to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'global_wolverine_z3n' stems from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also compromises the security of applications relying on this package, potentially allowing for unauthorized access or data manipulation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall global_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 workaround, you can avoid using the 'global_wolverine_z3n' package altogether and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The 'global_wolverine_z3n' package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to uninstall this package and monitor your application for vulnerabilities using tools like Vulert. By staying informed and proactive, you can protect your applications from potential threats.
See every vulnerability recorded for global_wolverine_z3n →
FAQ
The main issue is that it contains malicious code that modifies package metadata and floods the npm registry with variants, compromising the integrity of the ecosystem.
You can use Vulert to monitor your application for vulnerabilities. By analyzing your package-lock.json file, Vulert provides real-time alerts for any open-source vulnerabilities.
You should uninstall the package immediately using 'npm uninstall global_wolverine_z3n' and check for any dependencies that may be affected.
Yes, consider researching other npm packages that offer similar functionality without the associated risks of malicious code.
Vulert uses your package-lock.json file to monitor and alert you in real-time for any open-source vulnerabilities, ensuring your application remains secure.
