arweave
Audited by Socket on Feb 28, 2026
1 alert found:
SecurityThis Arweave/ArNS skill is largely coherent: reading a local JWK wallet and contacting Arweave gateways is consistent with its purpose of signing and publishing transactions. The primary risks are operational/privacy: handling of the private JWK (credential exposure), forwarding uploads/keys to third-party Turbo/Irys nodes, and financial risk from spending AR. The documentation addresses many mitigations (local signing, never logging wallet contents, cost estimates, confirmations, dry-run, and prompt-injection cautions). No evidence of obvious malicious code, obfuscated payloads, or download-execute chains is present in the provided text. Overall this skill is plausible and usable for its stated purpose but carries moderate supply-chain and operational risk due to wallet handling and optional third-party upload endpoints; require careful user controls (strict local signing, minimal logging, explicit endpoint choices, and mandatory confirmations for spending) when deploying or granting agent permissions.