Malicious Code Injection in accepted_peafowl_0xrequest Package
Summary
MAL-2025-99079: Malicious code in accepted_peafowl_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 accepted_peafowl_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 through automated publishing scripts, which can lead to significant security risks.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the accepted_peafowl_0xrequest package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The scripts continuously republish these variants, polluting the npm registry and potentially compromising the integrity of other packages. The ramifications include unauthorized access to sensitive data, disruption of package management, and a general degradation of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall accepted_peafowl_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 accepted_peafowl_0xrequest package and replace its functionality with alternative packages that do not have known vulnerabilities. Always verify the integrity of packages before including them in your project.
Conclusion
The accepted_peafowl_0xrequest package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is essential to remove this package from your projects and monitor for any updates or patches. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for accepted_peafowl_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.
You can use Vulert to monitor your application for vulnerabilities. Simply upload your package-lock.json file to receive real-time alerts.
The risks include unauthorized access to sensitive data, disruption of package management, and a loss of trust in the npm ecosystem.
Currently, the best course of action is to uninstall the affected package. Monitor for any updates or patches that may be released in the future.
Regularly audit your dependencies, use tools like Vulert for monitoring, and only install packages from trusted sources.
