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

toyota-cir12 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169132: Malicious code in toyota-cir12 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The toyota-cir12 package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publishing of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been compromised, leading to significant security concerns.

Vulnerability Detail

The vulnerability in the toyota-cir12 package originates from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which are then continuously republished to pollute the npm registry. This behavior can lead to unauthorized access, reputation damage for developers, and a cluttered npm ecosystem, making it difficult for legitimate packages to be found.

How To Fix

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

npm uninstall toyota-cir12

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, avoid using the toyota-cir12 package and monitor your project's dependencies for any signs of malicious activity. You can also utilize tools like Vulert to check for vulnerabilities in your package-lock.json file.

Conclusion

The toyota-cir12 package poses a significant threat due to its malicious code that alters project files and floods the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your applications.

See every vulnerability recorded for toyota-cir12 →

Share this vulnerability

FAQ

The toyota-cir12 package is an npm package associated with the tea.xyz token reward campaign, which has been compromised to include malicious code.

The malicious code modifies your package.json file, potentially leading to unauthorized access and reputation damage by flooding the npm registry with derivative packages.

You should uninstall the toyota-cir12 package immediately using 'npm uninstall toyota-cir12' and monitor your project for any unusual activity.

Yes, you can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Regularly monitor your dependencies using tools like Vulert, keep your packages updated, and review package sources before installation.

How To Fix

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

npm uninstall toyota-cir12

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