Back to skill

Security audit

HFT Paper Trader — Autonomous Crypto Framework

Security checks for vulnerabilities and agentic risk

Overview

This is a paper-trading instruction skill with disclosed local portfolio and ledger state, and it does not include executable code, credential handling, or real-trading commands.

Before installing, treat this as a simulation framework: confirm where PORTFOLIO.json, LEDGER.csv, and lessons.md will be written, use explicit paper-trading-only prompts, and require confirmation before any large watchlist or autonomous run.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (2)

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The skill advertises persistent components such as PORTFOLIO.json, LEDGER.csv, and lessons.md, but does not clearly warn users that invoking the skill may modify local files over time. This can surprise users, create unintended statefulness, and in an autonomous-agent context allow repeated writes that alter records, consume storage, or interfere with other workflows relying on those files.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

The invocation examples are overly broad and action-oriented, including phrases like trading all signals, without defining approval boundaries, simulation-only constraints, or exclusions. In an agent setting, ambiguous triggers can cause the skill to be invoked in situations the user did not clearly intend, leading to autonomous high-frequency actions and downstream file/state changes.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.