Malicious Code Injection in teagood-nakamala33: A Threat to npm Packages
Summary
MAL-2025-167297: Malicious code in teagood-nakamala33 (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-nakamala33 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate the generation of derivative packages to inflate developer reputation scores for token rewards. However, it has been identified as containing malicious scripts that compromise its integrity and the security of the npm ecosystem.
Vulnerability Detail
The vulnerability in teagood-nakamala33 stems from its inclusion in a series of malicious packages that utilize autopublish scripts to modify package.json files. These scripts remove private flags, alter version numbers, and generate random package names, leading to the pollution of the npm registry. The malicious behavior can result in developers unknowingly using compromised packages, which can lead to further security risks and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall teagood-nakamala33If 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, avoid using the teagood-nakamala33 package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages using tools like npm audit to identify vulnerabilities.
Conclusion
The teagood-nakamala33 package poses a significant security risk due to its malicious code that alters package files and pollutes the npm registry. It is crucial for developers to remove this package from their projects and remain vigilant about the packages they use. Utilizing tools like Vulert can help in monitoring for such vulnerabilities effectively.
See every vulnerability recorded for teagood-nakamala33 →
FAQ
The primary risk is the injection of malicious code that modifies package.json files, potentially leading to the use of compromised packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
You should uninstall the package immediately and check for any dependencies that may be affected. Use 'npm uninstall teagood-nakamala33' to remove it.
Yes, consider using other npm packages that offer similar functionalities without the malicious risks. Always verify the package's reputation before installation.
Regularly audit your dependencies using tools like npm audit, and stay informed about vulnerabilities in the packages you use. Consider using Vulert for real-time monitoring.
