Web3Dropper Verified Agent

Billions/Iden3 authentication and identity management tools for agents. Link, proof, sign, and verify.

This skill appears to do what it says (create/manage DIDs, sign/verify challenges and produce pairing links), but take these precautions before installing or running it: - Trust the remote services: the pairing flow constructs a callback URL that includes a signed JWS and points to attestation-relay.billions.network (and the code queries resolver.privado.id). If you don't trust those endpoints, do not use the pairing flow. - Protect private keys: the skill stores private keys unencrypted in $HOME/.openclaw/billions/kms.json. Treat that directory as highly sensitive. If you require stronger protection, do not create new keys here; instead use an existing key managed in a secure KMS/HSM and understand how (or if) the scripts import/leave keys on disk. - Validate the openclaw binary: the code executes openclaw via execFileSync. Ensure openclaw on PATH is the official, trusted CLI (an attacker could replace that binary). - Review and test in isolation: run the scripts in a sandbox or throwaway account first to observe network requests and generated files. Inspect the generated pairing URL before opening it in a browser. - If you need stricter guarantees: consider modifying the storage layer to encrypt keys at rest or integrate a hardware wallet/KMS, or consult the skill author for an encrypted-storage option. If these risks are acceptable and you trust Billions/iden3 and the openclaw CLI, the skill is coherent with its stated purpose; otherwise treat it as potentially sensitive and test in an isolated environment first.

Type: OpenClaw Skill Name: web3dropper-verified-agent Version: 1.0.0 The skill bundle is classified as suspicious primarily due to its metadata slug 'web3dropper-verified-agent' in _meta.json, which utilizes malware terminology ('dropper'). While the code implements a functional Web3 identity management system using the Iden3 protocol, it explicitly stores unencrypted private keys in the user's home directory ($HOME/.openclaw/billions/kms.json), as documented in SKILL.md and implemented in scripts/shared/storage/keys.js. Although the scripts include defensive measures like shell-operator sanitization in scripts/shared/utils.js, the combination of the suggestive naming and the high-risk handling of cryptographic secrets warrants caution.