Malicious Code Detected in teagood-manaki32: npm Package Vulnerability
Summary
MAL-2025-167097: Malicious code in teagood-manaki32 (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
teagood-manaki32 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate the distribution of rewards through the npm ecosystem. However, it has been identified as containing malicious code that can compromise the integrity of the npm registry and the reputation of developers using it.
Vulnerability Detail
The vulnerability originates from the package's design to automatically generate and publish derivative packages with randomized names. This is executed through scripts that modify the package.json file, removing private flags, altering version numbers, and creating numerous variants of the package. The continuous republishing of these variants can lead to pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially damaging their reputation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall teagood-manaki32If 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 measure, you can avoid using the affected package by not including it in your project dependencies. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The teagood-manaki32 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their projects.
See every vulnerability recorded for teagood-manaki32 →
FAQ
The primary risk is that it modifies package.json files and floods the npm registry with malicious variants, which can harm developer reputations and lead to confusion in package management.
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 requiring any signup.
You should uninstall the package immediately using 'npm uninstall teagood-manaki32' and review your project for any potential impacts.
Yes, consider looking for other npm packages that provide similar functionality but do not have known vulnerabilities.
Regularly check for updates in your dependencies and utilize tools like Vulert to monitor vulnerabilities in real-time.
