Malicious Code Vulnerability in teagood-nalikami132: npm Package Exploit
Summary
MAL-2025-167407: Malicious code in teagood-nalikami132 (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-nalikami132 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate token rewards for developers by generating and publishing derivative packages. However, it has been compromised to include malicious scripts that manipulate package metadata and flood the npm registry with unwanted packages.
Vulnerability Detail
The vulnerability in teagood-nalikami132 stems from its inclusion in a malicious campaign that employs scripts to modify package.json files. These scripts remove private flags, alter version numbers, and create numerous derivative packages with randomized names, ultimately inflating developer reputation scores. This behavior not only pollutes the npm registry but also poses risks to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss of trust in the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall teagood-nalikami132If 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-nalikami132 package and consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The teagood-nalikami132 package has been identified as a vector for malicious activity within the npm ecosystem. By understanding the nature of this vulnerability and taking proactive steps to remove the package and monitor your dependencies, you can safeguard your projects against potential threats.
See every vulnerability recorded for teagood-nalikami132 →
FAQ
The primary risk is that it contains malicious scripts that can modify your project's package.json, leading to potential security vulnerabilities and pollution of the npm registry.
You can check your package-lock.json file or run 'npm list teagood-nalikami132' in your project directory to see if the package is installed.
Immediately uninstall the package using 'npm uninstall teagood-nalikami132' and review your project for any unintended consequences of its use.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.
Regularly audit your dependencies, keep them updated, and use tools like Vulert to monitor for vulnerabilities in real-time.
