Malicious Code Injection in pajero-cir1: A Threat to npm Ecosystem
Summary
MAL-2025-163937: Malicious code in pajero-cir1 (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 pajero-cir1 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that aims to manipulate the npm registry and inflate developer reputation scores through the creation of derivative packages.
Vulnerability Detail
The vulnerability in the pajero-cir1 package stems from its association with a malicious campaign that utilizes autopublish scripts to generate and publish numerous derivative packages with randomized names. This behavior not only pollutes the npm registry but also modifies the package.json file to remove private flags and alter version numbers. The malicious payload can lead to significant security risks, including the potential for unauthorized access to sensitive data and the compromise of the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall pajero-cir1If 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 pajero-cir1 package and replace it with a trusted alternative. Additionally, ensure that your package.json file does not include any references to pajero-cir1 or similar malicious packages.
Conclusion
The pajero-cir1 package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant and remove any instances of this package from their projects. Utilizing tools like Vulert can help in monitoring and identifying vulnerabilities in real-time.
See every vulnerability recorded for pajero-cir1 →
FAQ
pajero-cir1 is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
The vulnerability can lead to unauthorized modifications in your package.json file and may expose your application to security risks.
You should remove the pajero-cir1 package from your project immediately and check for any other potentially malicious packages.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.
