Malicious Code Injection in unfortunate_gecko-notthedev Package
Summary
MAL-2025-110105: Malicious code in unfortunate_gecko-notthedev (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 unfortunate_gecko-notthedev package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. This behavior poses significant risks to developers and users relying on npm packages for their projects.
Vulnerability Detail
The vulnerability in the unfortunate_gecko-notthedev package stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of dependent projects. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall unfortunate_gecko-notthedevIf 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 unfortunate_gecko-notthedev package and instead look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The unfortunate_gecko-notthedev package poses a significant risk due to its malicious behavior of modifying package metadata and republishing variants. It is crucial for developers to remove this package and monitor their projects for similar vulnerabilities to maintain the integrity of their software.
See every vulnerability recorded for unfortunate_gecko-notthedev →
FAQ
It is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated package publishing.
The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project by introducing unwanted or malicious packages.
You should uninstall the package immediately using the command: npm uninstall unfortunate_gecko-notthedev.
Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities in your software using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.
