Back to skill

Security audit

wallet-address-check

Security checks for vulnerabilities and agentic risk

Overview

This is a small wallet-address format checker with no evidence of exfiltration, persistence, destructive behavior, or hidden execution.

Before relying on this for transfers, treat it as a basic format pre-check only. It does not fully verify EIP-55, Base58 checksums, or chain ownership, so high-value transfers still need wallet or exchange confirmation and a small test transfer. Installers may also want to narrow the declared agent tools because Write and WebFetch are broader than the script needs.

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
Vulnerability Patterns
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • 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 (5)

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
88% confidence
Finding

This file imposes a specific language/locale on users or maintainers through its natural-language instructions. Under the policy, forcing a language without offering user choice or documenting a justified locale constraint is a reportable issue.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

The top-level manifest description is written in Chinese only, while this skill is otherwise bilingual. Presenting the primary description in a fixed language without offering user choice can violate language/locale policy expectations for multilingual users.

Content

No source excerpt is available for this finding.

Intent-Code Divergence

Low
Category
Not specified by scanner
Confidence
79% confidence
Finding

L06 describes the skill's role as a narrowly scoped address format checker, which implies validation behavior rather than repository editing. Later, L27 explicitly permits changing the skill's own documentation, scripts, and configuration, creating an intent-level mismatch between the claimed skill behavior and the documented agent actions.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
76% confidence
Finding

The file is explicitly bilingual in Chinese and English, but it does not state that users may choose their preferred language or that the locale scope is intentionally limited. Under the policy rule, forcing or assuming a specific language set without user opt-in can be a natural-language policy concern.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
94% confidence
Finding

This code presents its description and runtime output in Chinese only, including the argparse description and printed status messages. That creates a language/locale constraint without any user opt-in or alternative, which matches the policy-violation category for forced language use.

Content

No source excerpt is available for this finding.