Malicious Code Injection in organic_lion_z3n: A Threat to npm Packages
Summary
MAL-2025-122415: Malicious code in organic_lion_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 'organic_lion_z3n' is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names, thereby inflating developer reputation scores for token rewards. The malicious nature of this package poses significant risks to developers and the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'organic_lion_z3n' originates from its inclusion in a malicious campaign that utilizes autopublish scripts to modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The ramifications of this vulnerability include potential reputation damage for developers, increased clutter in the npm registry, and the risk of inadvertently using compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall organic_lion_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 workaround, you can temporarily avoid using the 'organic_lion_z3n' package by removing it from your dependencies. You can do this by running the following command in your project directory: npm uninstall organic_lion_z3n.
Conclusion
The 'organic_lion_z3n' package poses a significant threat due to its malicious code that manipulates the npm registry. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can aid in real-time monitoring of open-source vulnerabilities.
See every vulnerability recorded for organic_lion_z3n →
FAQ
The vulnerability involves malicious code that modifies package.json to remove private flags and generates random package names, leading to potential pollution of the npm registry.
You can use the Vulert platform to monitor and alert for open-source vulnerabilities. Visit Vulert Scanner to check if your application is affected without requiring any signup.
Using organic_lion_z3n can lead to reputation damage for developers, increased clutter in the npm registry, and the risk of using compromised packages.
Currently, there is no specific patch for organic_lion_z3n. The best course of action is to remove the package from your project.
If you have used organic_lion_z3n, it is recommended to uninstall the package immediately and review your project's dependencies for any other potentially compromised packages.
Follow Vulert in Google
Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.