Malicious Code Injection in trevora-cir73: A Threat to npm Packages

trevora-cir73 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169271: Malicious code in trevora-cir73 (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package trevora-cir73 is part of a series of npm packages that have been linked to the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages with randomized names, which can inflate developer reputation scores for token rewards. This behavior poses a significant risk to the integrity of the npm registry and can lead to the proliferation of malicious software.

Vulnerability Detail

The vulnerability in trevora-cir73 originates from its association with a malicious campaign that employs autopublish scripts to modify package.json files. These scripts remove private flags, alter version numbers, and generate random package names, which allows the package to continuously republish variants. This behavior not only pollutes the npm registry but also compromises the security of applications that depend on these packages, potentially leading to unauthorized access or data breaches.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall trevora-cir73

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 measure, you can avoid using trevora-cir73 and any other packages associated with the tea.xyz campaign. Regularly audit your package.json and package-lock.json files to ensure that no malicious packages are present.

Conclusion

The trevora-cir73 package poses a significant security risk due to its malicious behavior associated with the tea.xyz token reward campaign. It is crucial to remove this package from your projects and monitor your dependencies for any vulnerabilities to maintain the integrity of your applications.

See every vulnerability recorded for trevora-cir73 →

Share this vulnerability

FAQ

trevora-cir73 is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through automated package publishing.

The vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and integrity.

You should uninstall the package immediately using the command npm uninstall trevora-cir73 and review your dependencies for any other malicious packages.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software using just your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall trevora-cir73

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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback