T08 · Insecure Dependencies
- Location
references/clanker.md:14- Finding
Unpinned Third-Party Packages Installed in Wallet-Enabled Applications
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This instruction-only skill is coherent, but it guides users through irreversible token and fee transactions with externally constructed transaction payloads and incomplete mandatory validation controls.
Install only if you are comfortable with a third-party service or SDK preparing blockchain transactions. Use a dedicated minimally funded wallet, pin dependencies, verify endpoints and contract addresses independently, decode and simulate every transaction, and require human approval before any signing, fee-recipient change, claim, or deployment.
references/clanker.md:14Unpinned Third-Party Packages Installed in Wallet-Enabled Applications
SKILL.md:102Externally Constructed Transactions Can Be Signed Without Mandatory Semantic Validation
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
After deploying via any platform, run a Quick Intel scan to verify the contract looks clean from an external perspective:
curl -X POST https://x402.quickintel.io/v1/scan/full \
-H "Content-Type: application/json" \
-H "PAYMENT-SIGNATURE: <x402_payment>" \
-d '{"chain": "base", "tokenAddress": "0xYourDeployedToken"}'
The trigger list includes broad phrases such as "token idea," "token strategy," and especially "is this a good token," which can cause the skill to activate in contexts where a user is only seeking discussion or analysis rather than token deployment tooling. In an agent environment with wallet capabilities, unintended invocation increases the chance that the agent moves from advisory conversation into transactional or externally connected behavior without sufficient user intent verification.
The skill provides direct instructions to send user prompts and wallet-associated metadata to an external endpoint, which creates a real external data transmission and action-initiation path. In the context of a token-launching skill, this is more dangerous because the external service returns unsigned transactions intended for signing, so an agent could be induced to initiate sensitive blockchain operations or disclose prompts, addresses, and payment authorization artifacts to a third party.
curl -X POST https://x402.quickintel.io/v1/tator/prompt \
-H "Content-Type: application/json" \
-H "PAYMENT-SIGNATURE: <x402_payment>" \
-d '{