Malicious Code Injection in Forthcoming Gecko Dumbs Package
Summary
MAL-2025-102873: Malicious code in forthcoming_gecko_dumbs (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 'forthcoming_gecko_dumbs' package is part of a series of npm packages that have been associated with 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 raises significant concerns regarding the integrity and security of the npm ecosystem.
Vulnerability Detail
The vulnerability in the 'forthcoming_gecko_dumbs' 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 not only compromises the security of the affected package but also pollutes the npm registry with numerous derivative packages, potentially leading to confusion and misuse by developers. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which employs these tactics to manipulate developer reputation scores.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall forthcoming_gecko_dumbsIf 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 package by using npm's package-lock.json to monitor your dependencies. If you are using Vulert, you can check your application for vulnerabilities without any installation by visiting the Vulert playground at https://vulert.com/scanner.
Conclusion
The 'forthcoming_gecko_dumbs' package poses a significant security risk due to its malicious behavior, which includes modifying package metadata and polluting the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their projects.
See every vulnerability recorded for forthcoming_gecko_dumbs →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation of derivative packages.
The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project's dependencies.
You should uninstall the 'forthcoming_gecko_dumbs' package immediately using 'npm uninstall forthcoming_gecko_dumbs'.
Yes, you can use Vulert to monitor your package-lock.json for vulnerabilities in real-time without requiring code access.
You can check your application for this vulnerability using the Vulert playground at Vulert Scanner.
