T09 · Insecure Skill Coding Practices
- Location
SETUP.md:106- Finding
Wallet API Key and MPC Signing Shares Stored Together in Plaintext Configuration
- Content
View full analysis
", "PORTAL_SECP256K1_SHARE": "", "PORTAL_ED25519_SHARE": "" } } } } } ``` ```text Your openclaw.json now contains your client API key alongside the MPC shares — treat it like any other config file with credentials and add it to .gitignore. Note that the shares alone can't sign anything; signing requires both the share and a valid client API key authenticated against Portal. ``` ### Technical Analysis The recommended configuration stores the Portal client API key and both client-side MPC signing shares together as plaintext values in `openclaw.json`. The project documentation confirms that possession of a valid API key and the corresponding share is sufficient to request Portal-assisted signing. Although adding the file to `.gitignore` reduces the likelihood of committing it to a repository, it does not protect the credentials from: - Local users or processes able to read the configuration file. - Overly permissive filesystem permissions. - Workstation compromise or malicious local software. - Unencrypted backups and configuration synchronization services. - Accidental file sharing. - Credentials already committed before `.gitignore` was configured. - Diagnostic bundles or support archives that collect configuration files. This design co-locates the authentication credential and the signing factor in one compromise target. It therefore weakens the intended separation provided by MPC: an attacker who obtains the configuration can possess the client-side material and authentication c ...[truncated 2253 chars]- Remediation
View remediation
