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

trevora-cir95 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

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

The trevora-cir95 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and sharing of code. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. The trevora-cir95 package is specifically designed to manipulate package metadata and publish numerous derivative packages, which can severely impact developers' reputations and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the trevora-cir95 package originates from its association with the tea.xyz token reward campaign. This campaign employs malicious scripts that automatically modify package.json files to remove private flags, alter version numbers, and generate random package names. The scripts continuously republish these variants, leading to pollution of the npm registry and potential exploitation of developers' reputations. The ramifications include loss of trust in the npm ecosystem, potential security risks for applications relying on these packages, and an increase in malicious activity within the registry.

How To Fix

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

npm uninstall trevora-cir95

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-cir95 package and replace it with a trusted alternative. Always verify the integrity and source of packages before including them in your project.

Conclusion

The trevora-cir95 package poses a significant threat to the npm ecosystem due to its malicious behavior. It is essential for developers to be vigilant about the packages they use and to take immediate action to remove any identified vulnerabilities. Regular monitoring and updating of dependencies can help maintain the integrity of your projects.

See every vulnerability recorded for trevora-cir95 →

Share this vulnerability

FAQ

The trevora-cir95 package is an npm package that has been identified as part of a malicious campaign to manipulate package metadata and inflate developer reputation scores.

The vulnerability can lead to the pollution of the npm registry, loss of trust in your project's dependencies, and potential security risks if malicious packages are inadvertently used.

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

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.

Yes, you should look for trusted packages that provide similar functionality without the associated risks of trevora-cir95.

How To Fix

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

npm uninstall trevora-cir95

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