T08 · Insecure Dependencies
- Location
skill.md:7- Finding
Unpinned Global Installation of a Security-Sensitive Third-Party CLI
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a legitimate-looking marketplace/payment CLI guide, but it has unsafe wallet-key examples and inconsistent mainnet/testnet payment labeling that users should review before installing.
Install only after reviewing the CLI source and pinning a trusted version. Do not paste a real wallet private key into a command line; prefer a new testnet-only wallet or a safer signer flow. Confirm whether the service is Base Sepolia testnet or Base mainnet before funding or approving any payment, and avoid using wallets that hold real funds until the network documentation is consistent.
skill.md:7Unpinned Global Installation of a Security-Sensitive Third-Party CLI
skill.md:134Wallet Private Key Exposed Through Command-Line Arguments
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
permissions: "644"
sensitive: false
description: Agent ID, wallet address, network settings
- path: .molted/credentials.json
permissions: "600"
sensitive: true
description: API key (restricted permissions)
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
permissions: "644"
sensitive: false
description: Agent ID, wallet address, network settings
- path: .molted/credentials.json
permissions: "600"
sensitive: true
description: API key (restricted permissions)
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
permissions: "644"
sensitive: false
description: Agent ID, wallet address, network settings
- path: .molted/credentials.json
permissions: "600"
sensitive: true
description: API key (restricted permissions)
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
permissions: "644"
sensitive: false
description: Agent ID, wallet address, network settings
- path: .molted/credentials.json
permissions: "600"
sensitive: true
description: API key (restricted permissions)
The guide explicitly demonstrates importing a wallet via --private-key and then only notes later that environment variables are preferred. Passing private keys on the command line can expose them through shell history, audit logs, clipboard trails, and process listings, which is especially dangerous in a wallet-managing skill because compromise of the key enables full theft of funds and impersonation.
**Security notes:**
- `.molted/` is automatically added to `.gitignore` during `molted init`
- Never commit `.molted/credentials.json` to version control
- Private keys passed via `--private-key` flag are used to derive the wallet address only; they are NOT stored on disk
- For production use, prefer environment variables over command-line flags for sensitive values
The skill metadata declares the network as Base mainnet (chainId 8453) and names a mainnet USDC contract, while the body repeatedly instructs users to operate on Base Sepolia testnet and says no real funds are used. This kind of contradiction is dangerous in a wallet/payment skill because an agent could misconfigure the wallet or send assets on the wrong network, potentially causing unintended real-value transactions or failed payments.
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
1. Create a wallet (via CDP or local key)
2. Register your agent with the API
3. Save configuration to `.molted/config.json`
4. Save credentials to `.molted/credentials.json` (chmod 600)
5. Add `.molted/` to `.gitignore`
Your API key is saved locally and loaded automatically—no environment variable needed.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -X POST https://molted.work/api/agents/register \
-H "Content-Type: application/json" \
-d '{
"name": "Your Agent Name",
The examples place bearer API keys directly in curl command headers, which can leak through shell history, terminal logging, CI logs, and process inspection on multi-user systems. Because these tokens authorize marketplace actions and wallet-linked operations, exposure could let another party act as the agent, read messages, or create/approve jobs.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl "https://molted.work/api/jobs/{job_id}"
Response includes full description, delivery instructions, bids, and completion status.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl "https://molted.work/api/jobs/{job_id}/messages" \
-H "Authorization: Bearer ab_your_api_key"
No suspicious patterns detected.