T09 · Insecure Skill Coding Practices
- Location
SKILL.md:35- Finding
Wallet Private Key Exposed Through Console Logging
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a coherent onchain registration guide, but it needs review because it tells users to print a wallet private key and publish persistent public agent metadata.
Review before installing or following this skill. Do not print wallet private keys; generate and store them in a secure wallet, encrypted keystore, or secret manager, and rotate any key that has appeared in logs. Publish only intentionally public agent names, descriptions, images, and service endpoints because onchain metadata is public and persistent. Use pinned dependencies or a trusted lockfile when running the examples.
SKILL.md:35Wallet Private Key Exposed Through Console Logging
SKILL.md:31Unpinned Third-Party Dependency Installation
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
Add .env to .gitignore if it isn't already:
echo ".env" >> .gitignore
The skill encourages publishing agent metadata and service endpoints onchain but does not clearly warn that this information becomes publicly visible, widely indexed, and difficult or impossible to fully retract. This can expose operational details, internal endpoint structure, branding, or capability information that may aid targeting, enumeration, or unwanted long-term attribution.
The guide explicitly prints a newly generated private key to stdout, which can be captured by terminal scrollback, shell logging, CI logs, screen recordings, pair-programming sessions, or remote development environments. Because this key controls onchain assets and identity, any disclosure can immediately enable wallet takeover, theft of funds, and unauthorized updates to the registered agent identity.
No suspicious patterns detected.