Malicious Code Vulnerability in formal_goose_0xrequest Package
Summary
MAL-2025-102863: Malicious code in formal_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 formal_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 certain functionalities within the npm registry but has been compromised to include malicious scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign that floods the npm registry with derivative packages. It contains scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior can lead to reputation inflation for developers and pollution of the npm registry, potentially affecting the integrity of the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall formal_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 workaround, you can temporarily avoid using the formal_goose_0xrequest package in your project. Additionally, consider using a tool like Vulert to monitor your package-lock.json for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The formal_goose_0xrequest package has been identified as containing malicious code that can compromise the integrity of the npm ecosystem. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to ensure security.
See every vulnerability recorded for formal_goose_0xrequest →
FAQ
It is an npm package that has been compromised to include malicious code as part of a token reward campaign.
The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your application by introducing malicious code.
You should remove the formal_goose_0xrequest package from your project and monitor for any updates or patches.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without any signup.
