Malicious Code Injection in trevora-aaissa-cir7: A Threat to npm Ecosystem

trevora-aaissa-cir7 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169145: Malicious code in trevora-aaissa-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 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

The package 'trevora-aaissa-cir7' is part of the npm ecosystem, which is widely used for JavaScript package management. It is associated with the tea.xyz token reward campaign, which has been linked to the proliferation of malicious packages designed to inflate developer reputation scores. This package, like others in the campaign, is engineered to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names.

Vulnerability Detail

The vulnerability in 'trevora-aaissa-cir7' arises 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 intended to pollute the npm registry and undermine the integrity of the package management system. The malicious payload can lead to unauthorized access and exploitation of affected systems, as it allows the package to republish itself continuously, making it difficult to track and remove.

How To Fix

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

npm uninstall trevora-aaissa-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 restrict the installation of this package by using npm's package-lock.json file to prevent the malicious package from being installed. Ensure that your project dependencies do not include 'trevora-aaissa-cir7'.

Conclusion

The 'trevora-aaissa-cir7' package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is essential to remove this package from your projects and monitor your dependencies for any vulnerabilities. Utilizing tools like Vulert can help maintain the integrity of your software.

See every vulnerability recorded for trevora-aaissa-cir7 →

Share this vulnerability

FAQ

'trevora-aaissa-cir7' is an npm package associated with a malicious campaign aimed at inflating developer reputation scores through the creation of numerous derivative packages.

The vulnerability can lead to unauthorized modifications of your project's dependencies, potentially allowing for further exploitation and pollution of the npm registry.

Immediately uninstall the 'trevora-aaissa-cir7' package and check your project for any unauthorized changes to your package.json or package-lock.json files.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. Visit Vulert Scanner to check if your application is affected by this vulnerability.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on known vulnerabilities in the npm ecosystem.

How To Fix

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

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