Malicious Code Injection in wispy_stork_0xrequest Package
Summary
MAL-2025-110967: Malicious code in wispy_stork_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 wispy_stork_0xrequest package is part of the npm ecosystem, often utilized in various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous packages. This package, like others in the campaign, is designed to manipulate npm's publishing system, potentially leading to significant security risks for developers and users alike.
Vulnerability Detail
The vulnerability in the wispy_stork_0xrequest package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, which are then republished to inflate developer reputation scores. The origin of this issue is linked to the tea.xyz token reward campaign, which employs autopublish scripts to create derivative packages, thereby polluting the npm registry and compromising the integrity of the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall wispy_stork_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 workaround, you can avoid using the wispy_stork_0xrequest package altogether and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The wispy_stork_0xrequest package poses a significant security risk due to its malicious code designed to manipulate npm's publishing system. It is crucial for developers to remove this package and monitor their applications for any vulnerabilities to maintain the integrity of their software.
See every vulnerability recorded for wispy_stork_0xrequest →
FAQ
It is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation and publication of derivative packages.
The vulnerability can lead to the modification of your package.json file, potentially exposing your application to further security risks and compromising its integrity.
You should uninstall the wispy_stork_0xrequest package immediately and monitor your application for any unusual behavior.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.
