Malicious Code Vulnerability in greasy_butterfly_0xrequest Package
Summary
MAL-2025-103362: Malicious code in greasy_butterfly_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 greasy_butterfly_0xrequest 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 concerns regarding the integrity and security of the npm ecosystem.
Vulnerability Detail
The vulnerability in greasy_butterfly_0xrequest originates from its association with malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This can result in compromised developer reputations and potential security risks for applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall greasy_butterfly_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, consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your dependencies using tools like Vulert, which alerts you to open-source vulnerabilities in real-time without requiring code access or installation.
Conclusion
The greasy_butterfly_0xrequest package poses a significant risk due to its malicious code that modifies package metadata and repopulates the npm registry with potentially harmful variants. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities.
See every vulnerability recorded for greasy_butterfly_0xrequest →
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 application by introducing malicious code.
You should remove the greasy_butterfly_0xrequest package from your project and monitor for any updates or patches.
You can use Vulert to monitor your package-lock.json file for vulnerabilities in real-time without needing to install any software.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.
