Malicious Code Injection in Toyota-Cir11 Package: npm Vulnerability
Summary
MAL-2025-169131: Malicious code in toyota-cir11 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The 'toyota-cir11' package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards through automated publishing of derivative packages. However, it has been compromised to include malicious scripts that manipulate package metadata and inflate developer reputation scores.
Vulnerability Detail
The vulnerability stems from malicious code embedded in the 'toyota-cir11' package, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall toyota-cir11If 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 remove the 'toyota-cir11' package from your project by executing: npm uninstall toyota-cir11. This will prevent any malicious scripts from executing until a fix is available.
Conclusion
The 'toyota-cir11' package has been identified as containing malicious code that compromises the integrity of npm packages. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications from potential threats.
See every vulnerability recorded for toyota-cir11 →
FAQ
The malicious code can lead to the modification of your package.json file, removal of private flags, and the generation of numerous unwanted package variants, which can clutter the npm registry.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.
Regularly audit your dependencies and utilize tools like Vulert to monitor for vulnerabilities in real-time, ensuring that you are alerted to any issues as they arise.
If you cannot update the package, consider removing it from your project and looking for alternative packages that provide similar functionality without the associated risks.
For more information, you can reach out to Amazon Inspector at actran@amazon.com, as they discovered this vulnerability.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
