Malicious Code Injection in common_woodpecker_0xrequest Package
Summary
MAL-2025-100724: Malicious code in common_woodpecker_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 common_woodpecker_0xrequest package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. This behavior not only clutters the npm registry but also poses significant security risks.
Vulnerability Detail
The vulnerability in the common_woodpecker_0xrequest package stems from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior allows the package to continuously republish variants, polluting the npm registry and potentially leading to the exploitation of unsuspecting developers who may unknowingly use these compromised packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been associated with various malicious npm packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall common_woodpecker_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, avoid using the common_woodpecker_0xrequest package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your package dependencies using tools like Vulert to monitor for vulnerabilities.
Conclusion
The common_woodpecker_0xrequest package contains malicious code that poses significant risks to developers and their projects. It is crucial to remove this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.
See every vulnerability recorded for common_woodpecker_0xrequest →
FAQ
It is an npm package that is part of a campaign to inflate developer reputation scores through the automatic generation of derivative packages.
The malicious code modifies your package.json file, removes private flags, and continuously republishes variants, which can lead to security vulnerabilities and clutter in the npm registry.
You should uninstall the common_woodpecker_0xrequest package immediately and check for any dependencies that may be affected.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring any signup.
