Malicious Code Injection in trevora-cir41: A Threat to npm Ecosystem
Summary
MAL-2025-169236: Malicious code in trevora-cir41 (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
trevora-cir41 is an npm package that has been identified as part of a broader malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which has been known to flood the npm ecosystem with harmful packages. The primary functionality of trevora-cir41 is to serve as a conduit for malicious scripts that manipulate package metadata, thereby compromising the integrity of the npm registry.
Vulnerability Detail
The vulnerability in trevora-cir41 stems from its inclusion in a malicious campaign that deploys scripts designed to automatically generate and publish derivative packages with randomized names. These scripts, such as auto.js and autopublish.js, modify the package.json file to remove private flags and alter version numbers. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can inflate developer reputation scores fraudulently. The ramifications include potential security risks for developers who unknowingly integrate these malicious packages into their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall trevora-cir41If 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 measure, you can prevent the installation of trevora-cir41 by adding it to your project's .npmrc file with the following line: 'package-lock=false'. This will help avoid any unintended installations of this malicious package.
Conclusion
The trevora-cir41 package poses a significant threat to the npm ecosystem due to its malicious code that manipulates package metadata. It is essential for developers to remove this package from their projects and to utilize tools like Vulert to monitor for vulnerabilities in real-time. Staying vigilant and informed is key to maintaining the security of your applications.
See every vulnerability recorded for trevora-cir41 →
FAQ
trevora-cir41 is an npm package identified as part of a malicious campaign that manipulates package metadata and floods the npm registry.
The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.
You should uninstall the package immediately using the command: npm uninstall trevora-cir41 to mitigate any risks.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json file. You can check your application for vulnerabilities without any signup at the Vulert playground.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about known vulnerabilities in the npm ecosystem.
