Malicious Code Injection in precious_gecko-tool: npm Package Vulnerability
Summary
MAL-2025-107183: Malicious code in precious_gecko-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 precious_gecko-tool is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate token rewards through automated publishing of derivative packages. However, it has been identified as containing malicious code that compromises the integrity of the npm registry by generating and publishing numerous variants of itself with altered metadata.
Vulnerability Detail
The vulnerability in precious_gecko-tool arises from its inclusion in a campaign that floods the npm registry with malicious packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. This can result in developers inadvertently using compromised packages, which may introduce security risks into their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall precious_gecko-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, you can remove the precious_gecko-tool package from your project by executing the following command: npm uninstall precious_gecko-tool. This will prevent any potential exploitation of the vulnerability until a fix is provided.
Conclusion
The precious_gecko-tool npm package has been identified as containing malicious code that compromises the integrity of the npm registry. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications from potential risks.
See every vulnerability recorded for precious_gecko-tool →
FAQ
The vulnerability involves malicious code that alters package metadata and floods the npm registry with compromised packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
If you cannot update the package, it is recommended to uninstall it from your project to mitigate any risks associated with the vulnerability.
While specific exploits have not been detailed, the nature of the vulnerability suggests that it could lead to the use of compromised packages in applications, posing security risks.
This vulnerability can lead to a loss of trust in the npm ecosystem as it allows for the proliferation of malicious packages, potentially affecting many developers and their applications.
