Malicious Code Injection in hungry_wren_z3n Package
Summary
MAL-2025-94888: Malicious code in hungry_wren_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 hungry_wren_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 malicious packages. This package, like others in the campaign, is designed to manipulate developer reputation scores through automated publishing scripts.
Vulnerability Detail
The vulnerability in the hungry_wren_z3n package stems from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores and pollute the npm registry with derivative packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms to distribute harmful code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall hungry_wren_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 prevent the execution of malicious scripts by using npm's package-lock.json file to lock your dependencies. Ensure that you do not install any new packages from untrusted sources until the vulnerability is resolved.
Conclusion
The hungry_wren_z3n package contains malicious code that poses a significant risk to developers and their projects. It is crucial to remove this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for hungry_wren_z3n →
FAQ
The impact includes potential exposure to malicious code that can alter your project's dependencies and compromise your application's integrity.
You can use Vulert, which monitors open-source vulnerabilities in real-time. Simply upload your package-lock.json file to the Vulert playground at Vulert Scanner to check for vulnerabilities.
To prevent similar vulnerabilities, always review and vet packages before installation, and consider using tools like Vulert to monitor your dependencies.
If you have installed the hungry_wren_z3n package, you should uninstall it immediately using the command: npm uninstall hungry_wren_z3n.
While specific alternatives depend on your project's requirements, consider using well-established packages with a strong community and regular updates.
