Malicious Code Injection in explicit_louse_z3n Package
Summary
MAL-2025-94391: Malicious code in explicit_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 explicit_louse_z3n package is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate npm's registry by creating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol. The package's functionality is compromised due to its malicious intent, making it a significant risk for developers using it.
Vulnerability Detail
The vulnerability in the explicit_louse_z3n package originates from its design to include malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. The ramifications include pollution of the npm registry, potential security risks for applications using these packages, and a negative impact on the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall explicit_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 prevent the installation of the explicit_louse_z3n package by adding it to your project's .npmrc file with the following line: 'package-lock=false'. This will help avoid the automatic installation of this malicious package.
Conclusion
The explicit_louse_z3n package poses a significant risk due to its malicious code that alters package configurations and pollutes the npm registry. It is essential for developers to be aware of this vulnerability and take immediate action to remove the package and monitor their projects for any potential impacts.
See every vulnerability recorded for explicit_louse_z3n →
FAQ
The explicit_louse_z3n package is an npm package associated with a token reward campaign that contains malicious code designed to manipulate the npm registry.
This vulnerability can lead to the pollution of the npm registry and may introduce security risks to your application by modifying important files and generating unwanted packages.
If you have installed the explicit_louse_z3n package, it is crucial to remove it from your project immediately and check for any potential impacts on your application.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check if your application is affected by this vulnerability using the Vulert playground.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by the explicit_louse_z3n vulnerability without requiring any signup.
