Malicious Code Injection in still_louse_z3n Package - npm Vulnerability
Summary
MAL-2025-96779: Malicious code in still_louse_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 still_louse_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. However, its functionality has been compromised, leading to significant security concerns.
Vulnerability Detail
The vulnerability in the still_louse_z3n package originates 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 pollute the npm registry by continuously republishing variants, thereby undermining the integrity of the ecosystem. The ramifications include potential exposure of sensitive data, increased risk of dependency confusion, and a compromised development environment.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall still_louse_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 still_louse_z3n package and replace it with a trusted alternative. Ensure that your package.json does not include this package and monitor your dependencies for any unauthorized changes.
Conclusion
The still_louse_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 remove this package from your project and monitor your dependencies for any vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.
See every vulnerability recorded for still_louse_z3n →
FAQ
The still_louse_z3n package is part of the npm ecosystem and is involved in the tea.xyz token reward campaign, which aims to inflate developer reputation scores.
The vulnerability can lead to unauthorized modifications of your package.json file, potentially exposing sensitive data and compromising your project's integrity.
If you have installed the still_louse_z3n package, you should uninstall it immediately using the command npm uninstall still_louse_z3n.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.
Yes, consider using trusted packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before use.
