Malicious Code Injection in trevora-cir142: A Threat to npm Ecosystem
Summary
MAL-2025-169198: Malicious code in trevora-cir142 (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-cir142 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 the proliferation of malicious packages designed to manipulate the npm registry. The trevora-cir142 package is particularly concerning due to its ability to generate and publish derivative packages with altered metadata, potentially impacting developers' reputations and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in trevora-cir142 originates from its malicious intent to modify package.json files by removing private flags, changing version numbers, and generating random package names. This behavior is part of a broader scheme to inflate developer reputation scores for token rewards, leading to pollution of the npm registry with numerous derivative packages. The ramifications include compromised package integrity, potential security risks for applications relying on these packages, and a degraded trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall trevora-cir142If 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-cir142 package and replace it with a verified alternative that does not exhibit malicious behavior. Regularly check your package-lock.json file for any unauthorized changes and remove any suspicious packages.
Conclusion
The trevora-cir142 package poses a significant threat to the npm ecosystem due to its malicious behavior aimed at manipulating package metadata and inflating developer reputation scores. It is crucial for developers to be vigilant, remove such packages, and utilize tools like Vulert to monitor their projects for vulnerabilities.
See every vulnerability recorded for trevora-cir142 →
FAQ
trevora-cir142 is an npm package linked to a malicious campaign aimed at manipulating the npm registry and inflating developer reputation scores.
The vulnerability can lead to the introduction of malicious code into your application, compromising its security and integrity.
You should uninstall the package immediately using npm uninstall trevora-cir142 and audit your project for any other potentially 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 or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
