Malicious Code Injection in trevora-cir1: A Threat to npm Ecosystem
Summary
MAL-2025-169150: Malicious code in trevora-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 package trevora-cir1 is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious activities aimed at inflating developer reputation scores through the creation of numerous derivative packages. The trevora-cir1 package is particularly vulnerable due to its design, which allows for the automatic generation and publication of packages with altered metadata.
Vulnerability Detail
The vulnerability in trevora-cir1 originates from its inclusion in a malicious campaign that utilizes autopublish scripts to modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The ramifications include pollution of the npm registry, potential security risks for developers using these packages, and a compromised reputation for legitimate developers.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall trevora-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
As a temporary workaround, you can avoid using the trevora-cir1 package until a secure version is released. Additionally, you can monitor your project's dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time without requiring code access or installation. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner.
Conclusion
The trevora-cir1 package is associated with a significant vulnerability that poses risks to developers and the npm ecosystem. It is crucial to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing monitoring.
See every vulnerability recorded for trevora-cir1 →
FAQ
trevora-cir1 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 and pose security risks to your project by introducing malicious code.
You should update the package to a patched version if available or remove it entirely from your project to mitigate risks.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities and alerts you in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
