Malicious Code Injection in unable_wren_0xrequest Package
Summary
MAL-2025-110019: Malicious code in unable_wren_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 unable_wren_0xrequest package is part of the npm ecosystem, primarily used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant security risks for users and developers alike.
Vulnerability Detail
The vulnerability in the unable_wren_0xrequest package stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only compromises the integrity of the package but also pollutes the npm registry, potentially affecting other packages and users. The malicious payload can lead to unauthorized access and manipulation of projects relying on this package, posing a severe risk to application security.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall unable_wren_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 unable_wren_0xrequest package altogether and seek alternative packages that provide similar functionalities without the associated risks. Additionally, you can use the following command to uninstall the package: npm uninstall unable_wren_0xrequest.
Conclusion
The unable_wren_0xrequest package poses a significant security risk due to its malicious code that alters package configurations and floods the npm registry. It is crucial to remove this package from your projects and monitor for any updates or patches. Utilizing tools like Vulert can help in identifying and managing such vulnerabilities effectively.
See every vulnerability recorded for unable_wren_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
The vulnerability can lead to unauthorized modifications in your project, potentially compromising its security and integrity.
You should immediately uninstall the package using 'npm uninstall unable_wren_0xrequest' and look for alternative solutions.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
