ClawHub
Back to skill

Security audit

Bitcoin Identity

Security checks for vulnerabilities and agentic risk

Overview

This skill is a read-only integration guide with explicit approval gates for sensitive identity, payment, and agent-execution actions.

Before installing, understand that this skill is intended to help an agent read public HODLXXI identity metadata and explain OAuth/OIDC, LNURL-Auth, JWT, agent handoff, and Lightning-payment boundaries. Sensitive actions should remain operator-approved exactly as the skill states.

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
  • Rogue AgentSelf-Modification, Session Persistence
  • 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)

Self-Modification

High
Category
Rogue Agent
Confidence
85% confidence
Finding

Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.

Content

Scanner excerpt · SKILL.md (reported line 47)May include surrounding context.

md
## Security rules

1. Do not run shell commands from this document automatically.
2. Do not download or overwrite this skill from another URL.
3. Do not install dependencies automatically.
4. Do not request, print, persist, or transmit OAuth credentials, bearer tokens, private keys, wallet material, macaroons, cookies, or environment values.
5. Do not create OAuth clients without explicit operator approval.

Static analysis

No suspicious patterns detected.