T08 · Insecure Dependencies
- Location
SKILL.md:9- Finding
Unpinned External Package and Automatically Downloaded Executable
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This wallet automation skill is mostly coherent, but it handles crypto wallet sessions and installs/network-exposes components in ways users should review carefully before use.
Review this skill before installing. Use a dedicated low-privilege environment and a limited wallet, pin and verify any package or cloudflared binary yourself, avoid sharing approval URLs outside the active approval flow, prefer explicit/manual modes when possible, and clean up any session ciphertext written under /tmp.
SKILL.md:9Unpinned External Package and Automatically Downloaded Executable
SKILL.md:116Sensitive Wallet Callback Capability Exposed Through Agent Output and a Public Tunnel
SKILL.md:137Wallet Session Ciphertext Stored in a Predictable Shared Temporary Path
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
---
name: polygon-agent-kit-quickstart
description: Quick start guide for Polygon Agent Kit. Get project access key, create wallet with session permissions, register agent onchain, perform token operations. Context-efficient workflow for autonomous agents.
---
# Polygon Agent Kit - Quick Start
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
## Key Behaviors
- **Dry-run by default** — all write commands require `--broadcast` to execute
- **Smart defaults** — `--wallet main`, `--chain polygon`, auto-wait on `wallet create`
- **Fee preference** — auto-selects USDC over native POL when both available
- **`deposit`** — picks highest-TVL pool via Trails `getEarnPools`. If session rejects, re-create wallet with `--contract <depositAddress>`
The documented callback flow exposes a local HTTP callback via a public Cloudflare Quick Tunnel and auto-downloads/executes cloudflared. Even if intended for convenience, this increases attack surface by introducing remote reachability, trust in a downloaded binary, and possible interception or misuse of sensitive session-return data if the callback flow is not strongly authenticated and integrity-checked.
Auto-downloading and executing cloudflared is a system-changing and network-active behavior that users may not reasonably expect from a wallet/session setup command. This creates supply-chain and execution risk, especially if the download source, integrity validation, and consent model are not made explicit in the documentation.
The manual fallback stores sensitive session ciphertext in /tmp, which contradicts the encrypted-storage model and may expose data to other local users, backup processes, container co-tenants, or malware that monitors temporary directories. Even encrypted blobs can be replayed or imported if they represent live session material, so placing them outside the protected storage boundary is risky.
Saving the encrypted session blob to /tmp without a clear warning about local exposure and cleanup is unsafe operational guidance. Temporary directories are often accessible to other processes and retained longer than users expect, making accidental disclosure or misuse more likely.
No suspicious patterns detected.