Malicious Code Injection in Toyota-CIR1 Package: A Threat to npm Users
Summary
MAL-2025-169129: Malicious code in toyota-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 'toyota-cir1' package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing capabilities. Its primary function is to facilitate the distribution of code, but it has been compromised to include harmful scripts that manipulate package metadata and flood the registry with derivative packages.
Vulnerability Detail
The vulnerability in the 'toyota-cir1' package stems from its association with a malicious campaign that generates and publishes numerous derivative packages with randomized names. This is achieved through scripts that modify the package.json file, removing private flags and altering version numbers. The malicious payload can lead to the pollution of the npm registry, potentially harming developers' reputations and the integrity of the ecosystem. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes the creation of such malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall toyota-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
Currently, the best workaround is to avoid using the 'toyota-cir1' package altogether. If it is already in use, uninstall it immediately and monitor your project for any dependencies that may have been affected by this malicious code.
Conclusion
The 'toyota-cir1' package poses a significant risk due to its malicious code that manipulates npm package metadata. It is crucial for developers to remove this package from their projects and to remain vigilant about the security of their dependencies. Utilizing tools like Vulert can help in monitoring for such vulnerabilities effectively.
See every vulnerability recorded for toyota-cir1 →
FAQ
The 'toyota-cir1' package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
This vulnerability can lead to the pollution of the npm registry and may harm your project's reputation by inflating developer scores with malicious packages.
You should uninstall the 'toyota-cir1' package immediately using 'npm uninstall toyota-cir1' and check for any dependencies that may be affected.
Currently, there is no patched version available for the 'toyota-cir1' package, so it is recommended to remove it from your project.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can also check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner.
