Malicious Code Injection in trevora-cir150: A Threat to npm Packages
Summary
MAL-2025-169207: Malicious code in trevora-cir150 (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-cir150 is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry and compromise the integrity of the ecosystem.
Vulnerability Detail
The vulnerability in trevora-cir150 originates from its involvement in the tea.xyz token reward campaign. This campaign utilizes malicious scripts (such as auto.js and autopublish.js) to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The continuous republishing of these variants can lead to a polluted npm registry, making it difficult for developers to find legitimate packages and potentially exposing them to further vulnerabilities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall trevora-cir150
If 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-cir150 package until a secure version is released. Additionally, you can monitor your project for any instances of this package using tools like Vulert, which can alert you to open-source vulnerabilities in real-time. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The trevora-cir150 package poses a significant risk due to its involvement in a malicious campaign that exploits the npm registry. It is crucial for developers to be aware of this vulnerability and take appropriate actions to secure their projects by updating or removing the affected package.
See every vulnerability recorded for trevora-cir150 →
FAQ
trevora-cir150 is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.
The vulnerability can lead to the pollution of the npm registry, making it harder to find legitimate packages and potentially exposing your project to further vulnerabilities.
You should update the package to a patched version if available or remove it from your project to mitigate risks.
You can use tools like Vulert to monitor your project for open-source vulnerabilities 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.