Malicious Code Injection in gardukereta-tool: A Threat to npm Packages
Summary
MAL-2025-103057: Malicious code in gardukereta-tool (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
The gardukereta-tool is an npm package that has been implicated in a malicious campaign targeting the npm registry. This package is part of the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package compromises its integrity and poses a significant risk to users and developers relying on it.
Vulnerability Detail
The vulnerability in the gardukereta-tool arises from its association with a malicious payload that modifies the package.json file. This payload removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The origin of this issue is linked to the tea.xyz token reward campaign, which employs scripts designed to exploit the npm ecosystem for fraudulent gains. The ramifications include potential security risks for users who inadvertently install these compromised packages, as well as damage to the reputation of the npm registry.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall gardukereta-toolIf 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, users can avoid using the gardukereta-tool package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The gardukereta-tool package poses a significant security risk due to its malicious code injection. Users are advised to remove the package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your npm packages.
See every vulnerability recorded for gardukereta-tool →
FAQ
The gardukereta-tool is an npm package involved in a malicious campaign that aims to inflate developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the installation of compromised packages that may contain malicious code, posing security risks to your project and its users.
If you have installed the gardukereta-tool package, you should remove it immediately and check for any updates or patches that may address the vulnerability.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
