Variflight

Security checks across malware telemetry and agentic risk

Overview

This is a straightforward Variflight travel-query wrapper, with a real API-key handling caveat but no evidence of hidden, destructive, or unrelated behavior.

Install only if you intend to use Variflight and are comfortable sending travel queries to its API. Prefer a protected environment variable or secret manager for VARIFLIGHT_API_KEY, avoid passing the key on the command line, do not commit config files containing the key, set restrictive permissions on local key files, and do not bake live keys into Docker images or shared settings.

SkillSpector

By NVIDIA

Vulnerability Patterns

Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep

Findings (5)

Missing User Warnings

Medium

Confidence: 94% confidence
Finding: The README encourages several credential handling methods, including command-line arguments and plaintext config files, but never warns that these approaches can expose API keys through shell history, process listings, checked-in files, CI logs, or overly permissive file permissions. In a developer-tool skill intended for use across local environments, CI/CD, and shared workspaces, this omission materially increases the chance of accidental secret disclosure.

Missing User Warnings

Low

Confidence: 89% confidence
Finding: The documentation instructs users to send travel queries and an API key to an external HTTPS endpoint, but gives no user-facing privacy notice, data-handling warning, or consent guidance. In practice this can expose itinerary details and credentials to external infrastructure without informed user approval, which is especially relevant for travel data that may reveal personal movement patterns.

Missing User Warnings

Medium

Confidence: 97% confidence
Finding: This script accepts an API key via a command-line argument and forwards it onward, which exposes the secret through process listings, shell history, job control logs, and some monitoring tools. In an agent or shared multi-user environment, other local users or diagnostic systems may be able to observe the key, making credential theft realistic even though the script itself is not overtly malicious.

Missing User Warnings

Medium

Confidence: 91% confidence
Finding: The script explicitly supports passing the API key via --api-key and even documents that usage in its help text. Command-line secrets are commonly exposed through shell history, process listings, audit logs, and orchestration tooling, so this creates a real credential exposure risk even though it is not maliciously implemented.

Missing User Warnings

Medium

Confidence: 88% confidence
Finding: The script accepts an API key via command-line arguments and forwards it to another script, which can expose the secret through process listings, shell history, job control logs, or audit tooling on multi-user systems. In this travel-skill context, the key likely grants access to a third-party API rather than direct system compromise, but leaked credentials can still enable unauthorized API usage, quota exhaustion, billing abuse, or service disruption.

VirusTotal

66/66 vendors flagged this skill as clean.

View on VirusTotal