Malicious Code Injection in manus-tavml-maos: A Threat to npm Ecosystem
Summary
MAL-2025-160115: Malicious code in manus-tavml-maos (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-maos' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the tea.xyz token reward system. It is designed to automatically generate and publish derivative packages with randomized names, which can lead to pollution of the npm registry and potential security risks for users.
Vulnerability Detail
The vulnerability in 'manus-tavml-maos' originates from its association with a malicious campaign that employs autopublish scripts to modify package.json files. This includes removing private flags, changing version numbers, and generating random package names. The continuous republishing of these variants can lead to a cluttered npm registry, making it difficult for developers to find legitimate packages and potentially introducing security risks into their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall manus-tavml-maosIf 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 'manus-tavml-maos' package from your project by executing the command: 'npm uninstall manus-tavml-maos'. This will prevent any potential malicious activity associated with the package until a fix is implemented.
Conclusion
The 'manus-tavml-maos' package poses a significant threat due to its malicious code designed to manipulate npm packages. It is crucial for developers to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities in their applications.
See every vulnerability recorded for manus-tavml-maos →
FAQ
The main issue is that it contains malicious code designed to manipulate package.json files and flood the npm registry with derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground at Vulert Scanner without requiring any signup.
If you cannot update the package, it is advisable to uninstall it and look for alternative packages that provide similar functionality without the associated risks.
This vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and ensure to only use trusted packages from reputable sources.
