Back to skill

Security audit

Crypto Portfolio Tracker

Security checks for vulnerabilities and agentic risk

Overview

This markdown-only portfolio tracking skill describes expected financial tracking and export features without hidden code, persistence, or unrelated authority.

Before using it with live exchange accounts, confirm what credentials and account permissions the surrounding agent or tools will use, and treat any exported trade-history CSV as sensitive financial data.

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
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • 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 (1)

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
91% confidence
Finding

This markdown file describes data-export behavior via 'CSV ledger export' and 'export my trade history', which can affect user data and create files on the system. Under the markdown-specific warning rule, the description should disclose this behavior so users understand that portfolio/trade data may be written out.

Content

No source excerpt is available for this finding.