Malicious Code Injection in teagood-nakama64: A Threat to npm Users
Summary
MAL-2025-167231: Malicious code in teagood-nakama64 (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-nakama64 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate token rewards for developers by generating and publishing derivative packages. However, it has been identified as containing malicious code that compromises the integrity of the npm registry and can affect developers' reputations.
Vulnerability Detail
The vulnerability in teagood-nakama64 originates from its inclusion in a campaign that floods the npm registry with malicious packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only pollutes the npm registry but also poses risks to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss of reputation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall teagood-nakama64If 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-nakama64 package from your project by executing the command: 'npm uninstall teagood-nakama64'. This will help mitigate any immediate risks associated with the malicious code until a secure version is available.
Conclusion
The teagood-nakama64 package poses a significant risk due to its malicious code that alters package.json and floods the npm registry with unauthorized packages. It is crucial for developers to take immediate action by updating or removing the package to safeguard their projects and reputations.
See every vulnerability recorded for teagood-nakama64 →
FAQ
The primary risk is that the malicious code can modify your package.json file and publish unauthorized packages, potentially harming your project's reputation and security.
You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.
If you cannot update the package, consider removing it from your project as a temporary measure to avoid exposure to the vulnerability.
Yes, the malicious payload is designed to automatically generate and publish derivative packages, which can lead to further exploitation of the npm registry.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about security advisories related to the packages you use.
