Malicious Code Injection in teagood-nalikoli80: A Threat to npm Ecosystem
Summary
MAL-2025-167639: Malicious code in teagood-nalikoli80 (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-nalikoli80 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm registry, potentially inflating developer reputation scores through automated scripts. However, it has been identified as containing malicious code that modifies essential files and repackages itself under random names, posing a significant risk to developers and the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability originates from the package's malicious payload, which alters the package.json file by removing private flags and changing version numbers. It generates random Indonesian-themed package names and continuously republishes variants, leading to pollution of the npm registry. This behavior can compromise the security of projects that depend on this package, potentially introducing further vulnerabilities and affecting the reputation of legitimate developers.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall teagood-nalikoli80If 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 prevent the installation of this malicious package by using npm's package-lock.json to monitor your dependencies. Ensure that you do not install any packages that are not explicitly listed in your package-lock.json file.
Conclusion
The teagood-nalikoli80 package poses a significant threat to the npm ecosystem due to its malicious code that alters project files and repackages itself. It is essential for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your projects.
See every vulnerability recorded for teagood-nalikoli80 →
FAQ
The primary risk is the modification of your project's package.json file, which can lead to unauthorized changes and the introduction of other malicious packages.
You can use Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.
If you have installed this package, you should uninstall it immediately and review your project's dependencies for any other potential vulnerabilities.
Yes, tools like Vulert can help monitor your dependencies for vulnerabilities and alert you in real-time.
Npm registry pollution can lead to confusion among developers, as it becomes difficult to distinguish between legitimate packages and malicious ones, ultimately compromising the security of the entire ecosystem.
