Malicious Code Injection in direct_sole_0xrequest Package
Summary
MAL-2025-101591: Malicious code in direct_sole_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 direct_sole_0xrequest package is part of the npm ecosystem, often utilized for various JavaScript applications. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant issues in the integrity of the npm registry.
Vulnerability Detail
The vulnerability stems from the malicious code embedded in the direct_sole_0xrequest package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, thereby polluting the npm registry. The origin of this issue is linked to a token reward campaign that incentivizes the creation of these malicious packages, posing risks such as reputation damage for developers and potential security threats 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 direct_sole_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 direct_sole_0xrequest package and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The direct_sole_0xrequest package contains malicious code that poses significant risks to applications using it. It is crucial to take immediate action to mitigate these risks by updating or removing the package. Utilizing tools like Vulert can help you monitor for such vulnerabilities in real-time.
See every vulnerability recorded for direct_sole_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.
The vulnerability can lead to the pollution of the npm registry, potentially introducing malicious code into your application and compromising its security.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.
If you cannot update the package, consider removing it from your project and replacing it with a safer alternative.
For more information, you can reach out to the finder of this vulnerability, Amazon Inspector, at actran@amazon.com.
