Malicious Code Injection in trevora-cir11: A Threat to npm Ecosystem
Summary
MAL-2025-169162: Malicious code in trevora-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
Background
trevora-cir11 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to manipulate the npm ecosystem by creating numerous variants with altered metadata.
Vulnerability Detail
The vulnerability in trevora-cir11 stems from its design to execute autopublish scripts that modify the package.json file. This includes removing private flags, changing version numbers, and generating random package names, which can lead to pollution of the npm registry. The malicious payload can compromise the integrity of the npm ecosystem, making it difficult for developers to trust the packages they use. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits the npm publishing mechanism for malicious purposes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall trevora-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 workaround, you can monitor your package dependencies using tools like Vulert, which allows you to check for vulnerabilities in your application without requiring access to the code or installation. You can use the Vulert playground at https://vulert.com/scanner to check if your application is affected by this vulnerability.
Conclusion
The trevora-cir11 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata and inflate developer reputation scores. It is crucial for developers to be vigilant and take necessary actions to remove such packages and monitor their dependencies.
See every vulnerability recorded for trevora-cir11 →
FAQ
trevora-cir11 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the pollution of the npm registry, making it difficult to trust the integrity of packages and potentially exposing your project to further risks.
You should uninstall the trevora-cir11 package immediately using the command npm uninstall trevora-cir11.
Regularly audit your dependencies, use trusted packages, and monitor for vulnerabilities using tools like Vulert.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without needing to sign up.
