T03 · Remote Payload Retrieval and Execution
- Location
encrypted-card.md:177- Finding
Remote API Delivers Executable Decryption Code That Is Run Locally
- Content
View full analysis
Card-ChaseD-9547.md ``` This outputs the card JSON (number, CVV, expiry, name, billing address). ``` The remotely delivered file is described as containing executable code: ```json { "event": "rail5.card.delivered", "bot_id": "bot_abc123", "data": { "card_id": "r5card_...", "card_name": "ChaseD", "card_last4": "9547", "file_content": "", "suggested_path": ".creditclaw/cards/Card-ChaseD-9547.md", "instructions": "Save this file to .creditclaw/cards/Card-ChaseD-9547.md — then confirm delivery via POST /bot/rail5/confirm-delivery" } } ``` ```text Save the file to `.creditclaw/cards/` (or the path in `suggested_path`). The file is self-contained — it includes the decrypt script between `DECRYPT_SCRIPT_START/END` markers and the encrypted data between `ENCRYPTED_CARD_START/END` markers. Follow the `instructions` field in the message payload for next steps. ``` ### Technical Analysis The Skill directs the Agent to obtain a self-contained card file from a remote API. That file contains both encrypted data and a decryption script, and the workflow subsequently runs the delivered script through Node.js. The reviewed package does not define or constrain the actual script that will execute. It provides no pinned digest, digital signature, local script allowlist, authenticated release manifest, or validation of the JavaScript contents. TLS authenticates the current server connection but does not establish that the received code is identical to the version reviewed during this audit. ...[truncated 1611 chars]- Remediation
View remediation
