Malicious Code Injection in vicious_lobster_z3n Package
Summary
MAL-2025-97256: Malicious code in vicious_lobster_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 vicious_lobster_z3n package is part of the npm ecosystem, often utilized for various JavaScript applications. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to inflate developer reputation scores through automated scripts that publish numerous variants of itself, potentially leading to security risks for users who unknowingly incorporate it into their projects.
Vulnerability Detail
The vulnerability in vicious_lobster_z3n originates from its association with the tea.xyz token reward campaign, which employs malicious scripts to manipulate package.json files. These scripts remove private flags, alter version numbers, and generate random package names, leading to a polluted npm registry. The ramifications include compromised package integrity, potential exposure of sensitive data, and a significant increase in the risk of dependency confusion attacks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall vicious_lobster_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 vicious_lobster_z3n package and instead rely on alternative packages that provide similar functionality without the associated risks. Additionally, consider using npm audit to identify and address vulnerabilities in your project.
Conclusion
The vicious_lobster_z3n package poses a significant security risk due to its malicious code designed to manipulate npm registry entries. It is essential to remove this package from your projects and monitor your dependencies for vulnerabilities to maintain the integrity and security of your applications.
See every vulnerability recorded for vicious_lobster_z3n →
FAQ
vicious_lobster_z3n is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing of derivative packages.
The malicious code can compromise the integrity of your project by modifying package.json files, potentially leading to security vulnerabilities and dependency confusion.
You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.
If you have installed the vicious_lobster_z3n package, it is recommended to remove it immediately and replace it with a secure alternative.
Yes, tools like Vulert can help monitor your dependencies for vulnerabilities in real-time using just your package-lock.json file.
