Malicious Code Injection in manapf-manta-naya: A Threat to npm Packages
Summary
MAL-2025-159561: Malicious code in manapf-manta-naya (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
manapf-manta-naya is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate token rewards through various automated scripts. However, it has been identified as containing malicious code that can compromise the integrity of the npm registry and the applications that depend on it.
Vulnerability Detail
The vulnerability in manapf-manta-naya originates from its inclusion in a campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This not only inflates developer reputation scores but also pollutes the npm registry, potentially affecting other developers and applications relying on npm packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall manapf-manta-naya
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, you can remove the manapf-manta-naya package from your project by executing: npm uninstall manapf-manta-naya. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The manapf-manta-naya package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. 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 manapf-manta-naya →
FAQ
The main issue is that it contains malicious code that modifies package.json files and floods the npm registry with derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.
Using this package can lead to security vulnerabilities in your application, as it may introduce malicious code and affect the integrity of the npm registry.
Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in real-time. Keeping your packages updated is also crucial.
Remove the package immediately and check for any other dependencies that may have been affected. Update your project to ensure it is secure.