ClawHub
Back to skill

Security audit

WEB3 Integration

Security checks for vulnerabilities and agentic risk

Overview

This skill is a coherent Web3 integration guide with disclosed wallet and contract risks, though its activation metadata should be fixed before relying on automatic triggers.

Install only if you intend to use it for Web3 integration work, and verify contract addresses, chain IDs, ABI files, and signer flows yourself. Do not provide private keys in chat; use environment variables or a proper secrets manager. The publisher should replace the malformed trigger metadata with narrow, explicit triggers.

A.I.G

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs

SkillSpector

Vulnerability Patterns
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (1)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

The trigger field is effectively unspecified and appears to contain a generic serialized type marker ('System.Object[]') rather than concrete activation phrases or constraints. Ambiguous triggers can cause the skill to be invoked unexpectedly or too broadly, increasing the chance of unintended execution in sensitive contexts such as wallet, provider, or contract interactions.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.