Malicious Code Injection in manus-tavml-maosihabi: A Threat to npm Ecosystem
Summary
MAL-2025-160120: Malicious code in manus-tavml-maosihabi (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 'manus-tavml-maosihabi' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify critical files, such as package.json, and republish variants that can pollute the npm registry.
Vulnerability Detail
The vulnerability in 'manus-tavml-maosihabi' originates from its malicious payload that alters the package.json file by removing private flags and changing version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly incorporate these malicious packages into their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall manus-tavml-maosihabi
If 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, avoid using the 'manus-tavml-maosihabi' package and monitor your project for any unauthorized changes to package.json. Ensure that your npm environment is secure by regularly auditing your dependencies using: npm audit.
Conclusion
The 'manus-tavml-maosihabi' package presents a significant security threat due to its malicious code that alters project files and repackages itself. It is crucial for developers to be vigilant, remove affected packages, and utilize tools like Vulert to monitor for vulnerabilities in their projects.
See every vulnerability recorded for manus-tavml-maosihabi →
FAQ
The main issue is that it contains malicious code that modifies package.json and repackages itself under random names, leading to potential security risks.
You can use Vulert, which monitors open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
If you have installed the package, immediately uninstall it using the command: npm uninstall manus-tavml-maosihabi.
Yes, using this package can lead to unauthorized changes in your project, potential data leaks, and a polluted npm registry.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to your packages.