Malicious Code Injection in prior_impala_0xrequest Package
Summary
MAL-2025-107289: Malicious code in prior_impala_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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The prior_impala_0xrequest package is part of the npm ecosystem, often utilized 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 for users and developers relying on this package.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the prior_impala_0xrequest package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to the pollution of the npm registry. The ramifications include potential exposure of sensitive data, unauthorized access to systems, and overall degradation of the npm ecosystem's integrity.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall prior_impala_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 prior_impala_0xrequest package and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The prior_impala_0xrequest package poses a significant security risk due to its malicious code designed to manipulate the npm registry. Immediate action is required to remove this package and safeguard your project. Utilizing tools like Vulert can help in monitoring and preventing future vulnerabilities.
See every vulnerability recorded for prior_impala_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.
The vulnerability can lead to unauthorized modifications of your package.json file, potentially exposing your project to security risks and affecting its integrity.
You should uninstall the prior_impala_0xrequest package immediately and monitor your project for any unusual activity.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json. You can check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about known vulnerabilities in the packages you use.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
