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

trevora-cir44 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169239: Malicious code in trevora-cir44 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The package trevora-cir44 is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards in the tea protocol, making it a significant concern for developers relying on npm for package management.

Vulnerability Detail

The vulnerability in trevora-cir44 stems from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This can lead to a compromised development environment, where developers may unknowingly use malicious packages, risking security breaches and data integrity.

How To Fix

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

npm uninstall trevora-cir44

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-cir44 by using the following command to uninstall it: npm uninstall trevora-cir44. Additionally, consider using npm audit to identify and address any other vulnerabilities in your project.

Conclusion

The trevora-cir44 package poses a significant risk due to its malicious behavior of altering package metadata and republishing variants to the npm registry. Developers should take immediate action to remove this package and monitor their projects for any signs of compromise. Utilizing tools like Vulert can aid in maintaining a secure development environment.

See every vulnerability recorded for trevora-cir44 →

Share this vulnerability

FAQ

trevora-cir44 is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.

The vulnerability can lead to the introduction of malicious code into your project, potentially compromising security and data integrity.

You should uninstall the package immediately and monitor your project for any unusual behavior.

Yes, tools like Vulert can monitor your project for open-source vulnerabilities in real-time using just the package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall trevora-cir44

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