Malicious Code Injection in teagood-nalikoli89: A Threat to npm Users
Summary
MAL-2025-167648: Malicious code in teagood-nalikoli89 (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-nalikoli89 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate token rewards through automatic publishing of derivative packages. However, it has been identified as malicious, containing scripts that manipulate package metadata and flood the npm registry with unwanted variants.
Vulnerability Detail
The vulnerability in teagood-nalikoli89 originates from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores for the tea protocol token rewards, leading to potential pollution of the npm registry and compromising the integrity of the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall teagood-nalikoli89If 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 measure, avoid using the teagood-nalikoli89 package and consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The teagood-nalikoli89 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their applications for vulnerabilities using tools like Vulert.
See every vulnerability recorded for teagood-nalikoli89 →
FAQ
The primary risk is that it modifies package metadata and floods the npm registry with malicious variants, which can compromise the integrity of your project.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.
You should uninstall the package immediately and check your project for any dependencies that may have been affected.
Yes, consider using other npm packages that provide similar functionality but do not have known vulnerabilities.
Vulert uses your package-lock.json to monitor and alert you in real-time for open-source vulnerabilities, helping you maintain a secure software environment.
