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

trevora-ppisa-cir7 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169336: Malicious code in trevora-ppisa-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 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

The package trevora-ppisa-cir7 is part of the npm ecosystem and has been identified as part of a malicious campaign targeting developers. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores by flooding the npm registry with derivative packages. These packages often contain scripts that automatically publish variants with altered names and metadata, compromising the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in trevora-ppisa-cir7 stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of these variants, polluting the npm registry and potentially affecting developers who rely on the integrity of npm packages. The malicious payload can compromise the security of applications that depend on this package, leading to reputational damage and potential exploitation.

How To Fix

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

npm uninstall trevora-ppisa-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 prevent the installation of trevora-ppisa-cir7 by using the following command: npm uninstall trevora-ppisa-cir7. Additionally, ensure that your package-lock.json is monitored for any unauthorized changes, and consider using tools like Vulert to keep track of vulnerabilities in your dependencies.

Conclusion

The trevora-ppisa-cir7 package poses a significant threat due to its malicious behavior aimed at manipulating the npm registry. It is crucial for developers to remain vigilant, update their dependencies, and utilize tools like Vulert to ensure the security of their applications.

See every vulnerability recorded for trevora-ppisa-cir7 →

Share this vulnerability

FAQ

trevora-ppisa-cir7 is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the publication of derivative packages.

This vulnerability can compromise the integrity of your application by introducing malicious code that modifies package metadata and republishing variants, which can lead to security risks.

You should immediately update the package to the latest version or uninstall it if no safe version is available. Regularly monitor your dependencies for vulnerabilities.

Yes, you can use Vulert to monitor and alert for open-source vulnerabilities in your software. You can check your application using the Vulert playground without any signup.

Vulert is a tool that monitors open-source vulnerabilities in your software using just the package-lock.json file, providing real-time alerts for any detected issues.

How To Fix

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

npm uninstall trevora-ppisa-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