Malicious Code Injection in teagood-nalikami33: npm Package Vulnerability
Summary
MAL-2025-167432: Malicious code in teagood-nalikami33 (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-nalikami33 is part of the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with various packages. These packages are designed to manipulate developer reputation scores through automated publishing scripts. The vulnerability in this package allows for the modification of critical files, leading to potential security risks and pollution of the npm registry.
Vulnerability Detail
The vulnerability originates from the package's malicious payload, which modifies the package.json file by removing private flags and altering version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly install these compromised packages, leading to potential exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall teagood-nalikami33If 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 avoid using the affected package by replacing it with a trusted alternative or by manually managing dependencies to ensure that no malicious packages are included in your project.
Conclusion
The teagood-nalikami33 package presents a significant security vulnerability due to its malicious code that alters package files and repopulates the npm registry with compromised versions. It is essential for developers to take immediate action by removing the package and monitoring their projects for any related issues.
See every vulnerability recorded for teagood-nalikami33 →
FAQ
The impact includes potential security risks from malicious code execution and pollution of the npm registry, which can affect other developers and projects.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software by analyzing your package-lock.json. Visit Vulert Scanner to check your application without any signup.
If you have installed teagood-nalikami33, it is crucial to uninstall it immediately and check for any dependencies that may be affected.
Yes, consider using well-established packages that provide similar functionality without the associated risks. Always verify the package's reputation and reviews.
Vulert uses your package-lock.json to provide real-time alerts for open-source vulnerabilities, ensuring that you are informed about any potential risks in your dependencies.
