Malicious Code Injection in tropical_goose_0xrequest Package
Summary
MAL-2025-109839: Malicious code in tropical_goose_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
Background
The tropical_goose_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards through various automated scripts. However, it has been identified as malicious due to its ability to modify package metadata and republish itself under random names, which can lead to reputation inflation and registry pollution.
Vulnerability Detail
The vulnerability originates from the package's malicious payload, which alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior can lead to significant issues, including the proliferation of untrustworthy packages in the npm registry and potential security risks for developers who inadvertently use these packages. The malicious scripts are designed to automate the creation and publication of derivative packages, making it difficult to track and manage.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tropical_goose_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 prevent the installation of this package by using npm's package-lock.json to monitor dependencies. Remove any instances of tropical_goose_0xrequest from your package.json and package-lock.json files to mitigate the risk.
Conclusion
The tropical_goose_0xrequest package poses a significant risk due to its malicious behavior, which can compromise the integrity of npm projects. It is essential to remove this package and monitor your dependencies for vulnerabilities to maintain a secure development environment.
See every vulnerability recorded for tropical_goose_0xrequest →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to automate the publication of packages.
The vulnerability can lead to the introduction of malicious code and untrustworthy packages, compromising the security and integrity of your project.
You should immediately remove the tropical_goose_0xrequest package and check for any unauthorized changes in your project files.
Yes, you can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
