Malicious Code Injection in standard_parrot_requirement Package
Summary
MAL-2025-96748: Malicious code in standard_parrot_requirement (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 standard_parrot_requirement package is part of the npm ecosystem, primarily used for managing dependencies in JavaScript applications. This package has been identified as part of a malicious campaign that aims to exploit npm's package management system. It is designed to automatically generate and publish derivative packages, which can lead to reputation inflation for the associated token reward scheme.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the standard_parrot_requirement package, which contains scripts that modify the package.json file to remove private flags and alter version numbers. This allows the package to continuously republish variants with randomized names, polluting the npm registry and potentially compromising the integrity of applications that depend on it. The ramifications include unauthorized access to sensitive data and the introduction of unstable or harmful code into production environments.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall standard_parrot_requirementIf 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 standard_parrot_requirement package from your project by executing: npm uninstall standard_parrot_requirement. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The standard_parrot_requirement package poses a significant risk due to its malicious code that alters package configurations and repopulates the npm registry with harmful variants. It is crucial for developers to take immediate action by removing the package and monitoring for updates to safeguard their applications.
See every vulnerability recorded for standard_parrot_requirement →
FAQ
It is an npm package that has been identified as part of a malicious campaign to exploit the npm ecosystem.
The vulnerability can lead to unauthorized modifications in your application's dependencies, potentially introducing harmful code.
You should uninstall the package immediately and monitor for any updates or patches that may be released.
Yes, Vulert can monitor your package-lock.json file for open-source vulnerabilities in real-time, alerting you to any issues.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
