Malicious Code Injection in traditional_gecko_0xrequest: npm Package Vulnerability
Summary
MAL-2025-109800: Malicious code in traditional_gecko_0xrequest (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The traditional_gecko_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate interactions with various APIs and services. However, it has been identified as containing malicious code that compromises its integrity and the security of applications that depend on it.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign that floods the npm registry with derivative packages. It includes scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only inflates developer reputation scores but also leads to pollution of the npm registry, potentially introducing security risks to applications that utilize these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall traditional_gecko_0xrequestIf 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 measure, you can avoid using the traditional_gecko_0xrequest package in your project. If it is already included, remove it from your package.json and run npm install to clean up your dependencies.
Conclusion
The traditional_gecko_0xrequest package poses a significant security risk due to its malicious code that alters package configurations and floods the npm registry. It is essential to remove this package from your projects and monitor for updates or patches. Utilizing tools like Vulert can help in identifying vulnerabilities in your applications.
See every vulnerability recorded for traditional_gecko_0xrequest →
FAQ
The vulnerability involves malicious code that modifies package.json files and floods the npm registry with derivative 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.
You should remove the package from your project and ensure that you are not using any of its functionalities.
Currently, there is no specific patch available for traditional_gecko_0xrequest. It is recommended to remove the package until a secure version is released.
Failing to address this vulnerability can lead to security breaches, data leaks, and the introduction of malicious code into your application.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
