Malicious Code Injection in teagood-nakamala4: A Threat to npm Ecosystem
Summary
MAL-2025-167304: Malicious code in teagood-nakamala4 (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-nakamala4 is a package within the npm ecosystem that is part of a broader token reward campaign associated with the tea.xyz protocol. This package is designed to facilitate the distribution of rewards through the generation of derivative packages. However, it has been identified as containing malicious scripts that compromise its integrity and the npm registry.
Vulnerability Detail
The vulnerability in teagood-nakamala4 originates from its inclusion in a campaign that floods the npm registry with derivative packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only inflates developer reputation scores but also leads to pollution of the npm registry, potentially affecting other 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-nakamala4If 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 workaround, you can avoid using teagood-nakamala4 and any other packages associated with the tea.xyz token reward campaign. Additionally, consider using npm audit to identify and address vulnerabilities in your project.
Conclusion
The discovery of malicious code in teagood-nakamala4 highlights the importance of vigilance in the npm ecosystem. Developers should take proactive measures to secure their applications by auditing dependencies and removing any compromised packages. Utilizing tools like Vulert can enhance security monitoring and alerting.
See every vulnerability recorded for teagood-nakamala4 →
FAQ
The malicious code can lead to the pollution of the npm registry, affecting the integrity of other packages and potentially compromising the security of applications that depend on them.
You can use tools like npm audit to scan your project for vulnerabilities. Additionally, Vulert can monitor your package-lock.json for real-time alerts on open-source vulnerabilities.
To prevent similar vulnerabilities, regularly audit your dependencies, avoid using unverified packages, and stay informed about security advisories related to the packages you use.
If you have already used teagood-nakamala4, it is crucial to remove it from your project and replace it with a secure alternative. Ensure to update your package dependencies accordingly.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
