Malicious Code Injection in teagood-manaki4: A Threat to npm Users
Summary
MAL-2025-167105: Malicious code in teagood-manaki4 (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-manaki4 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability in teagood-manaki4 arises from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising other packages. The origin of this vulnerability is linked to a campaign aimed at exploiting npm for token rewards, making it a significant threat to developers and users relying on the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall teagood-manaki4
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 teagood-manaki4 package from your project by executing: npm uninstall teagood-manaki4. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The teagood-manaki4 package poses a significant threat due to its malicious code that alters project files and pollutes the npm registry. It is essential for developers to stay vigilant, update their packages, and utilize tools like Vulert to monitor for vulnerabilities effectively.
See every vulnerability recorded for teagood-manaki4 →
FAQ
The primary risk is the potential for malicious code to alter your project's package.json file, leading to unauthorized package republishing and compromising the integrity of your application.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By simply uploading your package-lock.json file, you can identify if your application is affected.
To prevent similar vulnerabilities, always verify the source of packages before installation, regularly update dependencies, and utilize tools like Vulert for real-time vulnerability monitoring.
If immediate updates are not possible, consider uninstalling the affected package as a temporary measure to mitigate risks until a secure version is available.
You can find more information about vulnerabilities in npm packages on platforms like Vulert, which provides insights and alerts for open-source vulnerabilities.