OpenSky Flight Tracker

• Outcome: Pass
• Latest audit: Sep 16, 2026 · 5:32 AM UTC
• Version: 0.1.0

Overview

This skill is a straightforward flight-tracking helper, with ordinary privacy and supply-chain cautions but no artifact-backed malicious behavior.

Before installing, be aware that the skill installs a third-party PyPI CLI and may send flight numbers or coordinates for live tracking. For stricter environments, pin and review the package version before use.

A.I.G

Vulnerability Patterns

• Insecure Dependencies: Introduces malicious components through unsafe dependency sources
• Skill Instruction Hijacking: Alters the agent's session goals or safety constraints when the skill loads
• Agent Memory Poisoning: Writes attacker-controlled rules into memory that affect later sessions
• Remote Payload Retrieval and Execution: Fetches external code whose behavior can change after review
• Embedded Malicious Code: Ships malicious scripts inside the skill and executes them locally

Findings (1)

T08 · Insecure Dependencies

Warning

• Location: SKILL.md:13

Finding

Unpinned Third-Party Package Installation

Content

View full analysis

Vulnerability Details

File Location: SKILL.md, lines 13–18
Vulnerability Type: T08: Insecure Dependencies
Risk Level: Medium

Complete Code Snippet:

yaml

install:
  - id: pip
    kind: pip
    package: flight-tracker-cli
    bins: ["flight-tracker"]
    label: "Install flight-tracker-cli (pip)"

Technical Analysis

The skill instructs the framework to install flight-tracker-cli from PyPI without specifying an exact version or package hash. The project contains no lockfile or corresponding implementation source that would allow reviewers to verify the code ultimately installed and executed.

Consequently, the reviewed artifact does not fully determine its runtime behavior. Package compromise, maintainer-account compromise, ownership transfer, or a malicious future release could cause installations to retrieve supplier-controlled code that differs from the version originally intended. This finding identifies an unsafe dependency-management practice; the available files do not establish that the current package release is malicious.

Attack Path

1. An attacker compromises the package publisher or otherwise gains the ability to publish a release under the flight-tracker-cli package name.
2. The attacker publishes a malicious package version or modifies a future release.
3. A user or automation framework installs this skill.
4. Because no version or hash is pinned, pip resolves the attacker-controlled release.
5. Malicious code runs through package installation behavior or when the installed flight-tracker executable is invoked.

Impact Assessment

Successful exploitation could execute arbitrary code with the privileges of the account performing installation or running the CLI. Subject to those privileges, the compromised dependency could access readable files and environment variables, make unauthorized network requests, alter user-owned data, or execute additional proces ...[truncated 173 chars]

Remediation

View remediation

Remediation Suggestions

• Pin the dependency to a specific, reviewed version, such as flight-tracker-cli==X.Y.Z.
• Require a cryptographic hash for the approved distribution and install with hash verification.
• Maintain a lockfile or constraints file containing exact transitive dependency versions and hashes.
• Record and verify the package source, publisher, and source repository.
• Include or reference the source revision corresponding exactly to the approved package artifact so its runtime behavior can be audited.
• Review future upgrades before changing the pinned version, and use automated dependency and provenance scanning in the release process.
• Where practical, install the package in a least-privileged isolated environment.

SkillSpector

Vulnerability Patterns

• Trigger Abuse: Overly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (1)

Vague Triggers

Medium

• Category: Not specified by scanner
• Confidence: 93% confidence

Finding

The trigger description includes broad natural-language phrases such as "where is my flight" and "what's flying over me," which can match ordinary conversation and cause the skill to invoke when the user did not explicitly request this tool. In an agent environment, over-broad invocation can lead to unnecessary external calls, user confusion, and unintended disclosure of location- or travel-related context to the tool.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.