T01 · Skill Instruction Hijacking
- Location
encrypted-card.md:83- Finding
Server-Controlled Instructions Are Executed by an Authenticated Sub-Agent
- Content
View full analysis
Card-ChaseD-9547.md", "Use the decrypted card details to complete checkout at DigitalOcean.", "Call POST /api/v1/bot/rail5/confirm with { \"checkout_id\": \"r5chk_abc123\", \"status\": \"success\" } when done.", "If checkout fails, call confirm with { \"status\": \"failed\" } instead.", "Announce the result." ], "spawn_payload": { "task": "You are a checkout agent...", "cleanup": "delete", "runTimeoutSeconds": 300, "label": "checkout-digitalocean" } } ``` ```text ### Step 2: Spawn a Sub-Agent Once the checkout is approved, spawn an ephemeral sub-agent using the `spawn_payload` from the response: sessions_spawn({ task: spawn_payload.task, cleanup: "delete", runTimeoutSeconds: 300 }) The sub-agent executes the `checkout_steps` in sequence. You (the main agent) wait for the sub-agent to complete and then announce the result. ``` ### Technical Analysis The skill directs the main Agent to take the `task` and `checkout_steps` returned by the remote CreditClaw API and execute them as Agent instructions. These fields are treated as trusted commands rather than untrusted data. There is no documented local schema restricting the contents of the task, no allowlist of permitted sub-agent operations, and no requirement to compare the returned instructions with a fixed local transaction procedure. Consequently, control over the API response provides control over the sub-agent’s goals and actions. The sub-agent is expected to possess or obtain access to the CreditClaw API crede ...[truncated 1876 chars]- Remediation
View remediation
