Malicious Code Injection in trevora-cir115: A Threat to npm Ecosystem

trevora-cir115 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169168: Malicious code in trevora-cir115 (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-cir115 is part of a broader campaign that exploits the npm ecosystem by flooding it with malicious packages. These packages are designed to manipulate developer reputation scores through automated publishing scripts. The trevora-cir115 package specifically modifies its own package.json file to remove private flags and generate numerous derivative packages with randomized names, contributing to the pollution of the npm registry.

Vulnerability Detail

The vulnerability in trevora-cir115 originates from its association with the tea.xyz token reward campaign, which aims to inflate developer reputation scores. The malicious payload alters the package.json file, removing private flags and changing version numbers. It also generates random package names, leading to the continuous republishing of variants that clutter the npm registry. This not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly install these malicious packages.

How To Fix

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

npm uninstall trevora-cir115

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 prevent the installation of trevora-cir115 by using npm's package-lock.json file to monitor dependencies. You can also utilize the following command to remove the package: npm uninstall trevora-cir115.

Conclusion

The trevora-cir115 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate developer reputation scores. It is crucial for developers to be vigilant and remove any instances of this package from their projects. Utilizing tools like Vulert can help in monitoring and addressing such vulnerabilities effectively.

See every vulnerability recorded for trevora-cir115 →

Share this vulnerability

FAQ

trevora-cir115 is a malicious npm package that is part of a campaign to inflate developer reputation scores through automated publishing.

The vulnerability can lead to the installation of malicious packages that may compromise your project's integrity and security.

You should uninstall the package immediately using the command: npm uninstall trevora-cir115.

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-cir115

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