Options Wheel Strategy Screener

• Outcome: Pass
• Latest audit: Sep 16, 2026 · 10:19 AM UTC
• Version: 1.0.0

Overview

This skill is a straightforward options-screening script that fetches market data and does not trade, persist, or access accounts.

Install and run this in a virtual environment, avoid administrator privileges, and verify any options data independently before making trades. The main review note is that the dependency is not pinned, so future package versions could change behavior.

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: README.md:22

Finding

Unpinned Third-Party Dependency Installation

Content

View full analysis

Vulnerability Details

File Location: README.md, lines 22-24
Vulnerability Type: Unpinned third-party dependency and insufficient supply-chain integrity controls
Risk Level: Medium

Vulnerable Code Snippet:

text

## Dependencies

pip install yfinance

Technical Analysis

The documented installation command retrieves the latest version of yfinance and its transitive dependencies from the configured Python package index. The project provides no version constraint, dependency lockfile, package hashes, or provenance verification.

Consequently, the code installed by users can change after this project has been audited. Exploitation is conditional on compromise or malicious replacement of the named package, one of its transitive dependencies, or the configured package index. The repository itself does not contain evidence that yfinance is malicious.

Attack Path

1. An attacker compromises a dependency release, a transitive dependency, a maintainer account, or the package index used by the victim.
2. The attacker publishes a malicious version that remains compatible with the unconstrained package name.
3. A user follows the README and executes pip install yfinance.
4. Pip resolves and installs the attacker-controlled release because no approved version or cryptographic hash is enforced.
5. Malicious package code executes during installation or when scripts/wheel_screener.py imports or invokes the package.

Impact Assessment

Malicious dependency code could execute with the privileges of the user running pip or the screener. Depending on those privileges and the local environment, it could read or modify accessible files, access user-level credentials and environment data, make arbitrary network requests, tamper with Python environments, or execute additional processes.

The potential scope is the invoking user's account and any resources accessible to that account. System-wide impac ...[truncated 169 chars]

Remediation

View remediation

Remediation Suggestions

1. Add a reviewed dependency manifest and pin yfinance to an explicitly approved version.
2. Lock all transitive dependencies using a reproducible dependency-management tool such as pip-tools, Poetry, or uv.
3. Generate and verify cryptographic hashes for every resolved distribution, then install with:

   bash

   python3 -m pip install --require-hashes -r requirements.txt
   

4. Store the lockfile or fully pinned requirements file in version control and update it through a controlled review process.
5. Use automated dependency scanning and provenance checks before approving upgrades.
6. Recommend installation in a dedicated virtual environment without administrative privileges.
7. Prefer trusted package indexes over unverified mirrors, and document the expected index configuration.

SkillSpector

Vulnerability Patterns

• 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
• Excessive Agency: Unrestricted Tool Access, Autonomous Decision Making, Scope Creep

Static analysis

No suspicious patterns detected.