Malicious Code Vulnerability in superior_stork_0xrequest Package
Summary
MAL-2025-109315: Malicious code in superior_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
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 superior_stork_0xrequest package is part of the npm ecosystem and is involved in various token reward campaigns. It is designed to facilitate the automatic generation and publishing of derivative packages. However, this package 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. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only inflates developer reputation scores for token rewards but also pollutes the npm registry, potentially leading to security risks for developers and users relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall superior_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 superior_stork_0xrequest package altogether. If it is already in use, consider replacing it with a reputable alternative that does not exhibit malicious behavior. Additionally, regularly audit your package dependencies for vulnerabilities.
Conclusion
The superior_stork_0xrequest package has been identified as containing malicious code that poses a significant risk to applications relying on it. It is crucial to remove this package and monitor your dependencies for vulnerabilities to maintain the security of your projects.
See every vulnerability recorded for superior_stork_0xrequest →
FAQ
It is an npm package involved in token reward campaigns, designed to generate and publish derivative packages.
The malicious code modifies your package.json file, potentially leading to security vulnerabilities and pollution of the npm registry.
You should remove the superior_stork_0xrequest package from your project and replace it with a secure alternative.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check your application for vulnerabilities using the Vulert playground without any signup.
Regularly audit your dependencies, keep them updated, and use tools like Vulert to monitor for vulnerabilities in real-time.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
