sigil-security@4.2.1
CAUTION· static onlyPublisher claims: "Secure AI agent wallets via Sigil Protocol. 3-layer Guardian validation on 6 EVM chains." Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-18 and scored it 68/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Authorization escalation language. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
…missing either. The agent signer alone cannot execute any transaction. - **Zero admin privileges:** The agent signer cannot change policy, modify whitelists, freeze accounts, …Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.**Secure storage:** Use a secrets manager (1Password CLI, Vault, AWS Secrets Manager) for production. For local setups, ensure `chmod 600 ~/.openclaw/openclaw.json`.Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.- [ ] Config file has restricted permissions (`chmod 600`)Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
12 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim efe-arv: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- File permission modification command≈ +2 on the totalRequest the narrowest permission that works; replace wildcards with the exact paths or hosts.