contract-deployer

HIGH W007: Insecure credential handling detected in skill instructions.

• Insecure credential handling detected (high risk: 1.00). The skill's example and API accept a private_key argument (and documents a PRIVATE_KEY env var) which requires the agent to receive and include the raw secret/private key verbatim when invoking the deploy tool, creating a direct exfiltration risk.

MEDIUM W011: Third-party content exposure detected (indirect prompt injection risk).

• Third-party content exposure detected (low risk: 0.10). The runtime workflow in scripts/deploy.py ingests outsider-authored Solidity text only when the caller supplies source_code (or a file_path to tenant-provided files), and there is no automatic fetching/selection of arbitrary external text; compilation and deployment operate on this provided input.

MEDIUM W009: Direct money access capability detected (payment gateways, crypto, banking).

• Direct money access detected (high risk: 1.00). The skill is explicitly designed to compile and deploy Solidity smart contracts to EVM chains and includes parameters for rpc_url and private_key. The example calls a "deploy_contract" tool with a private key and RPC endpoint, which implies the agent can sign and submit on-chain transactions (i.e., crypto wallet signing / transaction execution). This is direct blockchain/crypto execution capability.