Malicious Code Injection in trevora-cir121: A Threat to npm Users

trevora-cir121 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169175: Malicious code in trevora-cir121 (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

trevora-cir121 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to manipulate package metadata and continuously publish harmful variants.

Vulnerability Detail

The vulnerability in trevora-cir121 stems from its inclusion in a campaign that utilizes autopublish scripts to create and publish numerous derivative packages with randomized names. This behavior not only pollutes the npm registry but also modifies the package.json file by removing private flags and altering version numbers. The malicious payload can lead to significant security risks, including the potential for unauthorized access and exploitation of affected systems.

How To Fix

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

npm uninstall trevora-cir121

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 avoid using the trevora-cir121 package and any other packages that exhibit similar malicious behavior. Regularly audit your package-lock.json file to identify and remove any suspicious packages.

Conclusion

The trevora-cir121 package poses a significant threat to npm users due to its malicious code that modifies package metadata and floods the npm registry. It is essential to remove this package from your projects and utilize tools like Vulert to monitor for vulnerabilities in real-time.

See every vulnerability recorded for trevora-cir121 →

Share this vulnerability

FAQ

trevora-cir121 is an npm package that has been linked to a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.

The malicious code modifies your package.json file, removes private flags, and continuously republishes variants, which can lead to security vulnerabilities and pollution of the npm registry.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. By utilizing the Vulert playground, you can check if your application is affected without requiring any installation.

You should uninstall the trevora-cir121 package immediately and audit your other dependencies to ensure they are secure.

Regularly audit your dependencies, use tools like Vulert for monitoring vulnerabilities, and stay informed about security updates for the packages you use.

How To Fix

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

npm uninstall trevora-cir121

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