T08 · Insecure Dependencies
- Location
SKILL.md:9- Finding
Unpinned Global Installation from a Mutable GitHub Source
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
Review recommended: the skill is a coherent Polygon wallet toolkit, but it uses high-impact wallet authority with an unpinned global install, automatic tunnel binary download, and sensitive session material handling that need user scrutiny.
Install only if you are comfortable giving this CLI wallet-session authority and accepting the supply-chain and network exposure. Prefer a pinned/audited version, avoid global installs where possible, review cloudflared download and tunnel behavior before creating wallets, set narrow session limits, use dry-runs before --broadcast, and clean up any /tmp session files immediately after use.
SKILL.md:9Unpinned Global Installation from a Mutable GitHub Source
SKILL.md:137Automatic Download and Execution of an Unverified Cloudflared Binary
SKILL.md:137Sensitive Wallet Session Callback Traverses a Public Quick Tunnel
SKILL.md:151Wallet 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
The quickstart instructs the CLI to auto-download and execute cloudflared and establish a public *.trycloudflare.com callback tunnel, but this network-exposed behavior is not clearly disclosed in the stated toolkit scope. Auto-fetching and running external binaries increases supply-chain and remote exposure risk, and the public callback URL handles wallet-session approval material, making the capability materially security-relevant in an agent wallet context.
The quickstart states that the encrypted session blob is automatically written to /tmp, which is inconsistent with the claim that credentials are stored under AES-256-GCM-encrypted storage in ~/.polygon-agent/. Even if encrypted, placing sensitive session material in a world-accessible temporary location can expose it to local users, malware, backup tooling, or accidental disclosure, especially if file permissions and cleanup are not tightly controlled.
The skill advertises AES-256-GCM encrypted storage in the metadata, but later documents a manual fallback that saves encrypted session blobs to /tmp. Even if the blob is encrypted, storing sensitive session material in a world-accessible or weakly controlled temporary location without a warning creates exposure risk and makes the top-level security claim incomplete and potentially misleading.
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
- **`fund`** — reads `walletAddress` from the wallet session and sets it as `toAddress` in the Trails widget URL. Always run `polygon-agent fund` to get the correct URL — never construct it manually or hardcode any address. The returned JSON contains `fundingUrl` and `walletAddress` so you can confirm the pre-filled recipient before sharing.
The documentation explicitly states that wallet create will auto-download and execute cloudflared and expose a local callback endpoint via a Cloudflare Quick Tunnel. Auto-fetching and running a network-facing binary materially expands the trust boundary and attack surface, especially in an agent toolkit handling wallet/session material. In this context, the behavior is more dangerous because it is tied to approval of crypto wallet sessions and can affect both host security and sensitive session flow.
The documentation describes automatic download of cloudflared and creation of a public tunnel, but does not prominently warn about the privacy, network exposure, and host-impact implications of that action. Users may unknowingly permit execution of external software and public exposure of a local callback path in a security-sensitive wallet workflow.
The manual fallback saves encrypted session material to /tmp/polygon-session-<rid>.txt without a clear warning about local exposure, persistence, or cleanup. Temporary directories are commonly monitored, shared across processes, or left uncleared, so sensitive wallet-session artifacts can be recovered or mishandled even if encrypted.
No suspicious patterns detected.