Malicious Code Injection in teagood-nakamala30: A Threat to npm Users
Summary
MAL-2025-167294: Malicious code in teagood-nakamala30 (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-nakamala30 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, which are often used to inflate developer reputation scores in exchange for tea protocol 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-nakamala30 originates from its inclusion in a campaign that floods the npm registry with malicious packages. These packages contain scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can potentially harm developers and users relying on legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall teagood-nakamala30If 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 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 discovery of malicious code in the teagood-nakamala30 npm package highlights the importance of vigilance when managing dependencies in software projects. By understanding the nature of this vulnerability and taking appropriate action, developers can safeguard their applications and contribute to a healthier open-source ecosystem.
See every vulnerability recorded for teagood-nakamala30 →
FAQ
The malicious code can lead to the pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially compromising the security of applications that rely on these packages.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert provides real-time alerts for any vulnerabilities, including those related to teagood-nakamala30.
To prevent similar vulnerabilities, always review package dependencies and their sources before including them in your project. Regularly update your dependencies and use tools like Vulert to monitor for vulnerabilities.
If you have used teagood-nakamala30 in production, it is crucial to remove it immediately and replace it with a secure alternative. Conduct a security audit of your application to ensure no other vulnerabilities are present.
Yes, you should report the vulnerability to npm and any relevant security authorities to help prevent further exploitation and to protect other developers from similar risks.
