Back to skill

Security audit

Tradebot Ops

Security checks for vulnerabilities and agentic risk

Overview

This trading-bot operations skill is coherent, but it gives restart and process-stop instructions for a live trading system without enough user confirmation or targeting safeguards.

Before installing, treat this as an operations aid for a financial trading bot and require manual confirmation before any stop, restart, or stale-state cleanup. Verify the exact target process, current positions, pending orders, and rollback steps before letting an agent act on the restart instruction.

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

Medium
Confidence
94% confidence
Finding
The skill explicitly instructs the agent to stop a bot PID and restart the system when data appears stale, but it does not require a user-facing confirmation, scope limitation, or warning that this is disruptive process control. In an operations skill tied to live trading, an automated or poorly scoped stop/restart can interrupt active strategies, interfere with open positions, or terminate the wrong process if PID selection is stale or ambiguous.

Static analysis

No suspicious patterns detected.