Malicious Code Injection in trevora-cir36: A Threat to npm Ecosystem
Summary
MAL-2025-169230: Malicious code in trevora-cir36 (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 package trevora-cir36 is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized by developers to manage dependencies in their projects. However, trevora-cir36 has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. This campaign is linked to the tea.xyz token reward initiative, which incentivizes the creation of numerous packages to inflate developer reputation scores.
Vulnerability Detail
The vulnerability in trevora-cir36 stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly install these malicious packages. The malicious payload is designed to continuously republish variants, further polluting the registry and potentially leading to security risks for applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall trevora-cir36If 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 trevora-cir36 package and replace it with a reputable alternative. Additionally, you can monitor your project's dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time. To check if your application is affected by this vulnerability, you can use the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The trevora-cir36 package poses a significant risk due to its malicious code designed to exploit the npm registry. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of your applications.
See every vulnerability recorded for trevora-cir36 →
FAQ
Trevor-cir36 is an npm package that has been identified as part of a malicious campaign targeting the npm registry.
The vulnerability can lead to the installation of malicious code, which may compromise your application's security and integrity.
You should remove the package immediately and monitor your project for any unusual behavior.
You can use tools like Vulert, which monitors your package-lock.json file to alert you of any open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign up.
