Malicious Code Injection in Toyota-Cir5 Package: A Threat to npm Users

toyota-cir5 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169140: Malicious code in toyota-cir5 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The toyota-cir5 package is part of the npm ecosystem, primarily used for various JavaScript applications. It is designed to facilitate certain functionalities within the npm registry. However, this package has been identified as part of a malicious campaign that targets developers by inflating reputation scores through the creation of derivative packages. This vulnerability poses a significant risk to developers who may unknowingly use this package, leading to potential security breaches and compromised applications.

Vulnerability Detail

The vulnerability in the toyota-cir5 package originates from its association with the tea.xyz token reward campaign. This campaign has led to the proliferation of malicious packages that contain scripts designed to automatically generate and publish derivative packages with randomized names. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only pollutes the npm registry but also compromises the integrity of the developer's environment, potentially leading to security vulnerabilities in applications that rely on these packages.

How To Fix

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

npm uninstall toyota-cir5

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 workaround, you can avoid using the toyota-cir5 package until a secure version is released. Additionally, consider using alternative packages that provide similar functionalities without the associated risks.

Conclusion

The toyota-cir5 package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their applications. It is crucial to remain vigilant, update packages regularly, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, developers can safeguard their applications against potential threats.

See every vulnerability recorded for toyota-cir5 →

Share this vulnerability

FAQ

The toyota-cir5 package is an npm package used in JavaScript applications, but it has been identified as part of a malicious campaign.

The vulnerability can lead to the injection of malicious code, compromising the security and integrity of your application.

You should immediately update the package to the latest version or remove it from your project to prevent potential security breaches.

Yes, you can use Vulert, which monitors and alerts 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 by this vulnerability without any signup.

How To Fix

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

npm uninstall toyota-cir5

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