Malicious Code Injection in wee_ferret_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-110784: Malicious code in wee_ferret_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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
wee_ferret_z3n is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package, like others in the campaign, is designed to manipulate the npm ecosystem by generating and publishing derivative packages with random names. Its primary function is to inflate developer reputation scores for token rewards, specifically for the tea.xyz protocol. The presence of such malicious packages poses a significant risk to developers and users relying on npm for package management.
Vulnerability Detail
The vulnerability in wee_ferret_z3n originates from its involvement in a token reward campaign that floods the npm registry with malicious packages. The package contains scripts that automatically modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior leads to the continuous republishing of these variants, which can pollute the npm registry and compromise the integrity of the ecosystem. The ramifications include potential security risks for applications using these packages, as they may inadvertently include malicious code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall wee_ferret_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 affected package by removing it from your project dependencies. Ensure that your package-lock.json file is updated accordingly after removal. You can also use tools like Vulert to monitor your project for vulnerabilities without needing to access the code directly.
Conclusion
The discovery of malicious code in the wee_ferret_z3n package highlights the importance of vigilance in the npm ecosystem. Developers should take immediate action to remove affected packages and utilize tools like Vulert to monitor for vulnerabilities. Staying informed and proactive is essential to maintaining secure applications.
See every vulnerability recorded for wee_ferret_z3n →
FAQ
wee_ferret_z3n is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
The vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and integrity.
You should uninstall the package immediately using the command npm uninstall wee_ferret_z3n and check your project for any other affected packages.
You can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
