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

trevora-cir99 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169299: Malicious code in trevora-cir99 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package trevora-cir99 is part of the npm ecosystem, which is widely used for JavaScript package management. It is associated with the tea.xyz token reward campaign that has been linked to the proliferation of malicious packages. These packages are designed to inflate developer reputation scores through automated scripts that publish derivative packages with randomized names, potentially compromising the integrity of the npm registry.

Vulnerability Detail

The vulnerability in trevora-cir99 stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to pollute the npm registry and can lead to significant security risks, including the unintentional installation of compromised packages by developers who may not be aware of the malicious activity.

How To Fix

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

npm uninstall trevora-cir99

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 workaround, you can avoid using the trevora-cir99 package and monitor your project for any unintended installations of malicious packages. Regularly audit your npm packages using the command: npm audit to identify and address vulnerabilities.

Conclusion

The trevora-cir99 package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is essential to remove this package and regularly audit your dependencies to maintain the security of your projects. Utilizing tools like Vulert can further enhance your ability to monitor for vulnerabilities.

See every vulnerability recorded for trevora-cir99 →

Share this vulnerability

FAQ

trevora-cir99 is an npm package that has been identified as containing malicious code aimed at manipulating the npm registry.

The vulnerability can lead to the installation of compromised packages, potentially exposing your project to security risks and data breaches.

You should uninstall the package immediately using the command: npm uninstall trevora-cir99 and audit your project for other vulnerabilities.

Regularly update your dependencies, use trusted packages, and utilize tools like Vulert to monitor your project for vulnerabilities.

Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check for vulnerabilities in your application without any signup using the Vulert playground.

How To Fix

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

npm uninstall trevora-cir99

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