Malicious Code Injection in changing_manatee_z3n Package
Summary
MAL-2025-100325: Malicious code in changing_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
The changing_manatee_z3n package is part of the npm ecosystem, primarily used for JavaScript development. It is often involved in token reward campaigns, which can lead to the proliferation of malicious packages. This package has been identified as part of a scheme that generates numerous derivative packages to manipulate developer reputation scores.
Vulnerability Detail
The vulnerability in the changing_manatee_z3n package stems from its association with a malicious campaign that 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 security risks, including the potential for code injection and reputation damage for developers.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall changing_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 prevent the installation of this package by using npm's package-lock.json file to lock your dependencies. Additionally, consider using the following command to audit your packages for vulnerabilities: npm audit.
Conclusion
The changing_manatee_z3n package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package and monitor your dependencies for vulnerabilities to maintain the security of your applications.
See every vulnerability recorded for changing_manatee_z3n →
FAQ
It is an npm package involved in token reward campaigns that has been identified as malicious.
The vulnerability can lead to unauthorized code execution and can compromise the integrity of your application.
You should remove the changing_manatee_z3n package from your project and monitor for any updates or patches.
Yes, you can use Vulert's playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file.
