Malicious Code Injection in teagood-nalikami131: npm Package Vulnerability
Summary
MAL-2025-167406: Malicious code in teagood-nalikami131 (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-nalikami131 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate token rewards through various scripts that automate the generation and publication of derivative packages. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm ecosystem.
Vulnerability Detail
The vulnerability originates from the malicious payload embedded within the teagood-nalikami131 package. This payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the automatic republishing of these variants. This behavior not only inflates developer reputation scores fraudulently but also pollutes the npm registry, potentially affecting other developers and applications relying on npm packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall teagood-nalikami131If 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 temporarily avoid using the teagood-nalikami131 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for any unauthorized changes in the package.json file.
Conclusion
The teagood-nalikami131 package has been identified as containing malicious code that poses significant risks to developers and the npm ecosystem. It is essential to remove this package from your projects and monitor for any unauthorized changes. Utilizing tools like Vulert can help in identifying vulnerabilities in your dependencies.
See every vulnerability recorded for teagood-nalikami131 →
FAQ
The primary risk is the injection of malicious code that modifies package metadata and repopulates the npm registry with potentially harmful packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground at Vulert Scanner.
If you have installed the package, it is crucial to uninstall it immediately and review your project for any dependencies that may be affected.
Yes, there are several alternative packages available on npm that provide similar functionalities without the associated risks. Research and choose a reputable package.
This vulnerability can lead to the proliferation of malicious packages in the npm registry, compromising the security of other developers' applications and undermining trust in the npm ecosystem.
