Malicious Code Injection in trevora-cir6: A Threat to npm Users

trevora-cir6 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169256: Malicious code in trevora-cir6 (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 trevora-cir6 package 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 a series of malicious activities aimed at inflating developer reputation scores. The trevora-cir6 package, like others in this campaign, contains scripts designed to manipulate package metadata and publish numerous derivative packages, potentially compromising the integrity of the npm registry.

Vulnerability Detail

The vulnerability in trevora-cir6 arises from the presence of malicious code that modifies the package.json file by removing private flags and altering version numbers. This code generates random package names, often themed around Indonesian culture, and continuously republishes these variants to the npm registry. The origin of this vulnerability is tied to the tea.xyz token reward campaign, which employs these tactics to artificially inflate developer reputation scores. The ramifications include the pollution of the npm registry, which can lead to confusion among developers and potential security risks if these packages are inadvertently used in projects.

How To Fix

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

npm uninstall trevora-cir6

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, avoid using the trevora-cir6 package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your package dependencies using tools like Vulert to monitor for vulnerabilities.

Conclusion

The trevora-cir6 package poses a significant risk due to its malicious code designed to manipulate npm package metadata. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your projects.

See every vulnerability recorded for trevora-cir6 →

Share this vulnerability

FAQ

trevora-cir6 is an npm package that is part of a campaign aimed at inflating developer reputation scores through malicious practices.

The malicious code modifies package metadata and can lead to the publication of numerous unwanted packages, potentially compromising your project's integrity.

You should uninstall the package immediately using 'npm uninstall trevora-cir6' and monitor your project for any further vulnerabilities.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.

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

How To Fix

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

npm uninstall trevora-cir6

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