Malicious Code Injection in subjective_pelican_0xrequest Package
Summary
MAL-2025-109230: Malicious code in subjective_pelican_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 subjective_pelican_0xrequest package is part of the npm ecosystem, typically used for various JavaScript applications. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the generation and publication of derivative packages. This package is particularly vulnerable due to its involvement in automated publishing scripts that compromise the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the package being part of a token reward campaign that floods the npm registry with malicious packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names, leading to pollution of the npm registry. The malicious payload can significantly affect developers by compromising their projects and reputations, as well as potentially introducing security risks into their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall subjective_pelican_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 subjective_pelican_0xrequest package altogether. If it is already included in your project, remove it by running: npm uninstall subjective_pelican_0xrequest. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The subjective_pelican_0xrequest package poses a significant risk due to its involvement in a malicious campaign that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their projects for any vulnerabilities to maintain the integrity and security of their applications.
See every vulnerability recorded for subjective_pelican_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through automated publishing.
The vulnerability can lead to the introduction of malicious code into your project, compromising its integrity and potentially exposing it to security risks.
You should uninstall the subjective_pelican_0xrequest package immediately and monitor your project for any unusual behavior.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just package-lock.json.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.
