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

trevora-cir104 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169156: Malicious code in trevora-cir104 (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

trevora-cir104 is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem. This package is designed to participate in the tea.xyz token reward scheme, which involves the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to modify package metadata and republish variants, thereby inflating developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in trevora-cir104 originates from its inclusion in a broader malicious campaign that floods the npm registry with harmful packages. The malicious code within this package modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly install these malicious packages, leading to potential security breaches and reputation damage.

How To Fix

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

npm uninstall trevora-cir104

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, avoid using the trevora-cir104 package and monitor your project for any dependencies that may inadvertently include it. Regularly audit your package-lock.json file to ensure no malicious packages are present.

Conclusion

The trevora-cir104 package poses a significant risk due to its malicious code that modifies package metadata and repopulates the npm registry with harmful variants. Developers should take immediate action to remove this package and monitor their projects for any dependencies that may include it. Utilizing tools like Vulert can help in identifying vulnerabilities in your application.

See every vulnerability recorded for trevora-cir104 →

Share this vulnerability

FAQ

trevora-cir104 is an npm package involved in a malicious campaign that generates and publishes harmful derivative packages.

The malicious code modifies your package.json file, potentially exposing your project to security risks and affecting your developer reputation.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

You should uninstall the package immediately using npm uninstall trevora-cir104 and check for any other dependencies that may rely on it.

Currently, there is no patched version available for trevora-cir104. It is recommended to remove the package until a safe version is released.

How To Fix

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

npm uninstall trevora-cir104

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