Malicious Code Injection in pajero-cir9: A Threat to npm Users

pajero-cir9 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-163956: Malicious code in pajero-cir9 (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

pajero-cir9 is an npm package that has been implicated in a malicious campaign targeting developers. This package is part of a broader initiative that aims to exploit the npm registry by flooding it 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 who inadvertently install them.

Vulnerability Detail

The vulnerability in pajero-cir9 arises from its association with the tea.xyz token reward campaign, which has been identified as a source of malicious activity on npm. The package contains scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly install these malicious packages, leading to potential data breaches or system compromises.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall pajero-cir9

If 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 measure, avoid using pajero-cir9 and any packages that may have been published as derivatives of it. Monitor your project for any unexpected behavior or changes in the package-lock.json file that may indicate the presence of malicious packages.

Conclusion

The pajero-cir9 package poses a significant security risk due to its malicious code designed to exploit the npm registry. It is essential for developers to remain vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, you can protect your projects from potential threats.

See every vulnerability recorded for pajero-cir9 →

Share this vulnerability

FAQ

pajero-cir9 is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

If you have pajero-cir9 installed, it may compromise your project's security by modifying critical files and introducing malicious behavior.

You should uninstall pajero-cir9 immediately using the command npm uninstall pajero-cir9.

Regularly update your dependencies, monitor your package-lock.json file for changes, and consider using tools like Vulert to track vulnerabilities in real-time.

Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check for vulnerabilities without installation via the Vulert playground.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall pajero-cir9

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback