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

trevora-cir80 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169279: Malicious code in trevora-cir80 (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The package trevora-cir80 is part of a broader campaign involving the tea.xyz token reward system, which has been known to flood the npm registry with malicious packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The trevora-cir80 package specifically contains scripts that alter package metadata and republish variants, leading to potential pollution of the npm ecosystem.

Vulnerability Detail

The trevora-cir80 package contains malicious code that modifies the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior is part of a strategy to inflate developer reputation scores for token rewards, which can lead to the proliferation of untrustworthy packages in the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms.

How To Fix

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

npm uninstall trevora-cir80

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 workaround, you can monitor your project for any unintended changes to package.json and regularly audit your dependencies. Additionally, consider using tools like Vulert to monitor for vulnerabilities in your package-lock.json file. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The trevora-cir80 package poses a significant threat due to its malicious code that alters package metadata and repopulates the npm registry with potentially harmful packages. It is crucial for developers to be vigilant, remove such packages, and utilize tools like Vulert for ongoing monitoring of vulnerabilities.

See every vulnerability recorded for trevora-cir80 →

Share this vulnerability

FAQ

trevora-cir80 is an npm package that is part of a malicious campaign aimed at manipulating developer reputation scores through the automatic generation of derivative packages.

The malicious code modifies your package.json file, potentially leading to the publication of untrustworthy packages and pollution of the npm registry.

You should uninstall the package immediately using the command 'npm uninstall trevora-cir80' to prevent any further issues.

While many packages in the npm registry are trustworthy, it is essential to regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities.

Vulert monitors your package-lock.json file for open-source vulnerabilities in real-time, alerting you to any issues without requiring code access or installation.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall trevora-cir80

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