Malicious Code Injection in Lively Manatee Z3N: A Threat to NPM Packages
Summary
MAL-2025-95290: Malicious code in lively_manatee_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
Lively Manatee Z3N is an NPM package that appears to be part of a broader campaign aimed at exploiting the NPM ecosystem. It is designed to facilitate the automatic generation and publication of derivative packages, often with randomized names. This package, like others in the campaign, is likely to be used for inflating developer reputation scores through deceptive practices.
Vulnerability Detail
The vulnerability in Lively Manatee Z3N originates from its malicious code, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the NPM registry. This can lead to significant ramifications, including the compromise of package integrity and the potential for developers to unknowingly use compromised packages in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lively_manatee_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 remove the Lively Manatee Z3N package from your project by executing 'npm uninstall lively_manatee_z3n'. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The Lively Manatee Z3N package poses a significant threat due to its malicious code that alters package metadata and floods the NPM registry with compromised packages. It is crucial for developers to stay vigilant, update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for lively_manatee_z3n →
FAQ
The vulnerability involves malicious code that modifies package metadata and repackages it under random names, compromising the integrity of the NPM registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
Using compromised packages can lead to security breaches, data loss, and the introduction of additional vulnerabilities into your application.
Regularly updating your dependencies, using tools like Vulert for monitoring, and reviewing package sources can help mitigate the risk of vulnerabilities.
If an immediate update is not possible, consider removing the package from your project and monitoring for updates regularly.
