Malicious Code Vulnerability in atomic_louse_z3n: Exploitation of npm Package for Reputation Inflation
Summary
MAL-2025-93298: Malicious code in atomic_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 package 'atomic_louse_z3n' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores in exchange for tea protocol token rewards, making it a target for malicious exploitation.
Vulnerability Detail
The vulnerability in 'atomic_louse_z3n' stems from its malicious payload that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This leads to continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of the ecosystem. The origin of this vulnerability is linked to the broader trend of malicious packages flooding npm, specifically targeting developers seeking token rewards.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall atomic_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 this package by using npm's package-lock.json to monitor dependencies. You can also use the following command to uninstall the package: npm uninstall atomic_louse_z3n.
Conclusion
The 'atomic_louse_z3n' package poses a significant risk due to its malicious behavior aimed at manipulating the npm registry. Developers should take immediate action to remove this package and monitor their dependencies for any potential vulnerabilities. Utilizing tools like Vulert can aid in maintaining security in open-source projects.
See every vulnerability recorded for atomic_louse_z3n →
FAQ
The main issue is that it contains malicious code designed to manipulate the npm registry by publishing numerous derivative packages, which can compromise the integrity of the ecosystem.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
If you have installed atomic_louse_z3n, you should uninstall it immediately using the command: npm uninstall atomic_louse_z3n.
Currently, there are no known patches for the atomic_louse_z3n package. It is advisable to remove the package entirely.
Vulert monitors and alerts in real-time for open-source vulnerabilities using just the package-lock.json file, providing a simple way to keep your applications secure.
