Malicious Code Injection in useless_lobster_z3n Package
Summary
MAL-2025-98986: Malicious code in useless_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 'useless_lobster_z3n' package is part of the npm ecosystem, primarily used for various JavaScript applications. It has been identified as part of a broader campaign that aims to manipulate the npm registry by flooding it with derivative packages. This package, like others in the campaign, is designed to inflate developer reputation scores through automated publishing scripts.
Vulnerability Detail
The vulnerability in the 'useless_lobster_z3n' package stems from its malicious code that modifies the package.json file to remove private flags and alters version numbers. It generates random package names and continuously republishes variants, leading to pollution of the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall useless_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 'useless_lobster_z3n' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any changes that may indicate the presence of malicious packages.
Conclusion
The 'useless_lobster_z3n' package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their projects.
See every vulnerability recorded for useless_lobster_z3n →
FAQ
It is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
Using this package can lead to the introduction of malicious code, compromising the security and integrity of your project.
You should immediately remove the 'useless_lobster_z3n' package and check for any other potentially compromised packages in your project.
Yes, you can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
