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

trevora-cir47 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169242: Malicious code in trevora-cir47 (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

trevora-cir47 is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem. This package is associated with the tea.xyz token reward initiative, which has been known to flood the npm registry with derivative packages. The primary functionality of trevora-cir47 is to serve as a conduit for these malicious activities, including the generation and publication of numerous derivative packages with altered metadata.

Vulnerability Detail

The vulnerability in trevora-cir47 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 designed to inflate developer reputation scores for token rewards while polluting the npm registry with numerous variants. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which employs autopublish scripts to automate the creation and publication of these malicious packages.

How To Fix

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

npm uninstall trevora-cir47

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, you can prevent the installation of trevora-cir47 by adding it to your project's .npmignore file or by using the following command to block it: npm install --no-save trevora-cir47. However, the best practice is to remove the package entirely.

Conclusion

The trevora-cir47 package poses a significant threat due to its malicious code designed to manipulate package metadata and inflate developer reputation scores. Immediate action is required to remove this package and safeguard your project from potential vulnerabilities. Regular monitoring using tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for trevora-cir47 →

Share this vulnerability

FAQ

trevora-cir47 is an npm package involved in a malicious campaign that generates and publishes derivative packages to inflate developer reputation scores.

The malicious code modifies your package.json file, potentially exposing your project to further vulnerabilities and cluttering the npm registry with unwanted packages.

You should uninstall the package immediately using the command npm uninstall trevora-cir47 and review your project for any other potentially malicious packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check if your application is affected by visiting the Vulert playground at Vulert Scanner.

It is advisable to look for well-maintained and reputable packages that serve the same purpose as trevora-cir47 but do not have a history of malicious activity.

How To Fix

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

npm uninstall trevora-cir47

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