imitation-agent
Skill declares shell-based game playing but stores server-generated cryptocurrency private keys in plaintext at a predictable filesystem path, creating credential theft risk.
The backend API returns a cryptocurrency wallet privateKey on first join (shown only once). The skill instructs the agent to save this key to ~/.clawdbot/skills/imitation-agent/config.json in plaintext. Anyone or any process with filesystem READ access to that path can steal the private key and drain any funds deposited.
SKILL.md:28 Why this conclusion was reached
1/4 dimensions flaggedDeclared resources and inferred behavior are broadly aligned.
5 lower-risk artifacts were extracted and still need context.
The report includes 0 attack-chain steps and 1 severe findings.
Dependency information is incomplete, so supply-chain confidence stays limited.
What drove the risk score up
Server-generated crypto wallet privateKey is returned via API and saved to ~/.clawdbot/skills/imitation-agent/config.json in plaintext. The skillcard acknowledges this as a known risk but does not provide strong mitigation guidance.
skill-card.md lists 'shell commands' and 'guidance' as outputs but does not explicitly declare the skill makes HTTP requests to an external third-party backend (imitation-backend-production.up.railway.app). The network activity is visible in SKILL.md examples but not prominently declared.
Config is always written to ~/.clawdbot/skills/imitation-agent/config.json, making it a static target for credential theft by other agents or processes on the same system.
Most important evidence
Server-generated crypto wallet private key stored in plaintext
The backend API returns a cryptocurrency wallet privateKey on first join (shown only once). The skill instructs the agent to save this key to ~/.clawdbot/skills/imitation-agent/config.json in plaintext. Anyone or any process with filesystem READ access to that path can steal the private key and drain any funds deposited.
SKILL.md:28 Network access not explicitly declared in skill capabilities
skill-card.md lists Output Type(s) as [guidance, shell commands, configuration, API calls] but does not explicitly declare that the skill makes outbound HTTP requests to an external third-party backend at imitation-backend-production.up.railway.app. The network requests are visible in SKILL.md examples but not prominently declared as a capability.
skill-card.md:1 Predictable credential storage path
The config file is always written to ~/.clawdbot/skills/imitation-agent/config.json, a predictable and static path. This makes the private key a static target: any other agent or process on the same system with filesystem READ access can read it.
SKILL.md:32 Private key transmitted in plaintext over network
The private key is returned from the backend API in a JSON response. If the connection to imitation-backend-production.up.railway.app is intercepted (e.g., MITM, compromised TLS, or a rogue endpoint), the private key can be captured in transit.
SKILL.md:23 Declared capability vs actual capability
SKILL.md: 'Use your shell tool to execute the following logic' SKILL.md line 32: cat > ~/.clawdbot/skills/imitation-agent/config.json SKILL.md examples show curl POST/GET to imitation-backend-production.up.railway.app, but skill-card.md does not list network as a declared output capability Suspicious artifacts and egress
https://imitation-backend-production.up.railway.app/skill/agent/join SKILL.md:24
https://imitation-backend-production.up.railway.app SKILL.md:44
0x1234567890123456789012345678901234567890 SKILL.md:120
https://clawhub.ai/user/CyberVerse2 skill-card.md:7
https://clawhub.ai/CyberVerse2/imitationgame-agent skill-card.md:26
Dependencies and supply chain
There are no structured dependency warnings.
File composition
SKILL.md skill-card.md