Malicious Code Injection in trevora-cir63: A Threat to npm Users
Summary
MAL-2025-169260: Malicious code in trevora-cir63 (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-cir63 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 by flooding the registry with derivative packages. The malicious nature of this package lies in its ability to manipulate package metadata and continuously publish variants, thus polluting the npm ecosystem.
Vulnerability Detail
The vulnerability in trevora-cir63 stems from its design to execute autopublish scripts that modify the package.json file. This includes removing private flags, altering version numbers, and generating random package names, which can lead to the proliferation of malicious packages in the npm registry. The origin of this vulnerability is linked to a broader campaign that exploits npm's publishing mechanisms, posing significant risks to developers who may unknowingly install these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall trevora-cir63If 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-cir63 package and monitor your project for any dependencies that may inadvertently include it. Regularly audit your package-lock.json file to identify and remove any malicious packages.
Conclusion
The trevora-cir63 package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry with harmful variants. It is essential for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for trevora-cir63 →
FAQ
trevora-cir63 is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the publication of derivative packages.
The vulnerability allows malicious code to modify your package.json file, potentially leading to the installation of harmful packages and compromising your project's integrity.
You should uninstall the trevora-cir63 package immediately using 'npm uninstall trevora-cir63' and audit your project for any other malicious dependencies.
Regularly update your dependencies, use trusted packages, and monitor your package-lock.json file for any unexpected changes or additions.
Yes, Vulert can monitor your project for open-source vulnerabilities in real-time using just your package-lock.json file. You can check if your application is affected by visiting the Vulert playground at Vulert Scanner.
