Malicious Code Injection in pajero-cir3: A Threat to npm Packages

pajero-cir3 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-163950: Malicious code in pajero-cir3 (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The pajero-cir3 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 exploits npm's publishing capabilities, leading to potential security risks for developers and users alike.

Vulnerability Detail

The vulnerability in pajero-cir3 originates from its association with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages contain scripts designed to automatically publish derivative packages with altered metadata, such as removing private flags and changing version numbers. This behavior not only pollutes the npm registry but also compromises the integrity of the packages, potentially leading to unauthorized access and manipulation of user applications.

How To Fix

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

npm uninstall pajero-cir3

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 the pajero-cir3 package and consider replacing it with a reputable alternative. Regularly audit your package dependencies to identify and remove any potentially harmful packages.

Conclusion

The pajero-cir3 package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is essential for developers to remove this package and monitor their dependencies closely to maintain the integrity of their applications.

See every vulnerability recorded for pajero-cir3 →

Share this vulnerability

FAQ

pajero-cir3 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 application, potentially compromising its security and functionality.

You should uninstall the package immediately using npm uninstall pajero-cir3 and review your other dependencies for similar vulnerabilities.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall pajero-cir3

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