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

trevora-llisa-cir7 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169327: Malicious code in trevora-llisa-cir7 (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

trevora-llisa-cir7 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 has been known to flood the npm ecosystem with harmful packages. The primary function of this package, like others in the campaign, is to manipulate the npm registry by generating and publishing derivative packages with altered metadata, thereby inflating developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in trevora-llisa-cir7 originates from its inclusion in a malicious campaign that employs autopublish scripts to automatically create and publish numerous derivative packages. These scripts modify the package.json file by removing private flags and changing version numbers, which allows the package to be republished continuously. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly install these malicious packages, potentially leading to security breaches and compromised applications.

How To Fix

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

npm uninstall trevora-llisa-cir7

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-llisa-cir7 package and monitor your project for any dependencies that may inadvertently include it. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.

Conclusion

The trevora-llisa-cir7 package poses a significant risk due to its malicious behavior of manipulating the npm registry. It is crucial for developers to be vigilant, remove any affected packages, and utilize monitoring tools like Vulert to safeguard their applications against such vulnerabilities.

See every vulnerability recorded for trevora-llisa-cir7 →

Share this vulnerability

FAQ

trevora-llisa-cir7 is an npm package involved in a malicious campaign that manipulates the npm registry.

The vulnerability can lead to the installation of malicious packages, compromising your application's security and integrity.

You should uninstall the trevora-llisa-cir7 package immediately and monitor your project for any other affected dependencies.

Regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and stay informed about security advisories.

Yes, you can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities 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-llisa-cir7

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