Malicious Code Injection in trevora-cir135: A Threat to npm Ecosystem
Summary
MAL-2025-169190: Malicious code in trevora-cir135 (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-cir135 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 modify its own metadata and continuously republish variants, thereby polluting the npm ecosystem.
Vulnerability Detail
The vulnerability in trevora-cir135 originates from its design to include autopublish scripts that alter the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these malicious packages, leading to potential security breaches and loss of trust in the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall trevora-cir135If 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-cir135 by adding it to your npm ignore list or by using the following command to prevent its installation: npm install --no-save trevora-cir135. However, the best practice is to remove the package entirely.
Conclusion
The trevora-cir135 package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package metadata and republishing variants. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in real-time.
See every vulnerability recorded for trevora-cir135 →
FAQ
trevora-cir135 is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
This vulnerability can lead to the installation of malicious packages that compromise your project's security and integrity.
You should uninstall the package immediately using npm uninstall trevora-cir135 and review your project's dependencies for any other malicious packages.
Yes, you can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
