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

trevora-cir124 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169178: Malicious code in trevora-cir124 (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-cir124 is an npm package that has been identified as part of a malicious campaign targeting developers through the tea.xyz token reward system. This package is designed to automatically generate and publish derivative packages, which can lead to reputation inflation among developers. The malicious nature of this package lies in its ability to modify critical files and republish variants, ultimately polluting the npm registry.

Vulnerability Detail

The vulnerability in trevora-cir124 stems from its inclusion in a broader malicious campaign that utilizes autopublish scripts to manipulate package.json files. This manipulation removes private flags, alters version numbers, and generates random package names, which can lead to significant security risks, including the potential for unauthorized access and exploitation of developer environments. The package's behavior is indicative of a systematic attempt to exploit the npm ecosystem for token rewards, posing a threat to both individual developers and the integrity of the npm registry.

How To Fix

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

npm uninstall trevora-cir124

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-cir124 package and monitor your project for any unauthorized changes. You can also use tools like Vulert to monitor your package-lock.json for vulnerabilities. To check if your application is affected by this vulnerability, visit the Vulert playground at https://vulert.com/scanner.

Conclusion

The trevora-cir124 package poses a significant threat due to its malicious code that alters package configurations and repopulates the npm registry with harmful variants. It is crucial for developers to remain vigilant, uninstall affected packages, and utilize monitoring tools like Vulert to safeguard their projects.

See every vulnerability recorded for trevora-cir124 →

Share this vulnerability

FAQ

trevora-cir124 is an npm package that has been linked to a malicious campaign aimed at manipulating developer reputation through token rewards.

The vulnerability can lead to unauthorized modifications in your project, potentially compromising security and integrity.

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

You can use Vulert to monitor your package-lock.json for vulnerabilities in real-time without needing to access the code or install additional tools.

Detailed information can be found in the vulnerability report on the Open Source Vulnerability database or by visiting the Vulert website.

How To Fix

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

npm uninstall trevora-cir124

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