Malicious Code Injection in teagood-nakamala83: A Threat to npm Ecosystem
Summary
MAL-2025-167352: Malicious code in teagood-nakamala83 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
teagood-nakamala83 is a package within the npm ecosystem, which is often used for JavaScript development. It is part of a broader campaign involving the tea.xyz token reward system, which has been known to flood the npm registry with numerous packages. This package, like others in the campaign, is designed to manipulate npm's publishing system, potentially leading to reputation inflation for developers involved in the tea protocol.
Vulnerability Detail
The vulnerability in teagood-nakamala83 stems 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 create and republish numerous derivative packages, which can clutter the npm registry and mislead developers. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms for malicious purposes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall teagood-nakamala83If 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 affected package from your project by executing: npm uninstall teagood-nakamala83. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The vulnerability in teagood-nakamala83 highlights the risks associated with malicious packages in the npm ecosystem. By understanding the nature of this threat and taking proactive measures, developers can protect their applications and contribute to a healthier software environment.
See every vulnerability recorded for teagood-nakamala83 →
FAQ
The malicious code can lead to the proliferation of unwanted packages in the npm registry, potentially affecting the reputation of developers and polluting the ecosystem.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
If you cannot update the package, consider removing it from your project as a temporary measure until a secure version is released.
This vulnerability can lead to a cluttered npm registry, making it difficult for developers to find reliable packages and potentially compromising the integrity of the ecosystem.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and only install packages from trusted sources.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
