Malicious Code Injection in specified_wren_0xrequest Package - npm Vulnerability
Summary
MAL-2025-108995: Malicious code in specified_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 specified_wren_0xrequest package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, making them a significant risk for developers and users alike.
Vulnerability Detail
The vulnerability in the specified_wren_0xrequest package stems from its inclusion in a campaign that deploys malicious code. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potential exploitation of developers who unknowingly use these packages. The origin of this vulnerability is linked to the broader issue of malicious packages flooding the npm ecosystem, which can have serious ramifications for software integrity and security.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall specified_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 specified_wren_0xrequest package altogether and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The specified_wren_0xrequest package poses a significant security risk due to its malicious code that alters package metadata and repopulates the npm registry with harmful variants. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain software integrity and security.
See every vulnerability recorded for specified_wren_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at manipulating package metadata and inflating developer reputation scores.
Using this package can lead to the pollution of your project's dependencies, potential security risks, and issues with package integrity.
You should uninstall the specified_wren_0xrequest package immediately and check for any alternative packages that can fulfill your requirements.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can check your application against known vulnerabilities using the Vulert playground.
Always vet packages before installation, use tools to monitor dependencies, and stay updated on security advisories related to the packages you use.
