Malicious Code Injection in corresponding_wren_0xrequest Package - npm Vulnerability
Summary
MAL-2025-101025: Malicious code in corresponding_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 corresponding_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 derivative packages. These packages are designed to inflate developer reputation scores for token rewards, leading to potential security risks for users who unknowingly integrate them into their projects.
Vulnerability Detail
The vulnerability originates from malicious code embedded in the corresponding_wren_0xrequest package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. It continuously republishes these variants, polluting the npm registry and potentially compromising the integrity of applications that rely on this package. The ramifications include unauthorized access to sensitive data, increased attack surface, and degradation of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall corresponding_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 remove the corresponding_wren_0xrequest package from your dependencies. Use the following command to uninstall it: npm uninstall corresponding_wren_0xrequest. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The corresponding_wren_0xrequest package poses a significant security risk due to its malicious code designed to manipulate package metadata and pollute the npm registry. It is essential to take immediate action by removing the package and monitoring your applications for any vulnerabilities. Utilizing tools like Vulert can further enhance your security posture.
See every vulnerability recorded for corresponding_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 package.json file, potentially compromising your application’s integrity and security.
You should uninstall the corresponding_wren_0xrequest package immediately and monitor your application for any unusual behavior.
Yes, tools like Vulert can monitor your package-lock.json file to alert you in real-time for open-source vulnerabilities.
You can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without needing to sign up.
