ClawHub
Back to skill

Security audit

Systematic Debugging

Security checks for vulnerabilities and agentic risk

Overview

This debugging skill is mostly a coherent process guide, but it includes broad activation language and examples that may expose environment values and signing credential inventory without safety guardrails.

Install only if you want a strict debugging workflow to influence many technical troubleshooting sessions. Before following its diagnostic examples, avoid printing secret values, signing identities, or keychain details into CI logs or shared transcripts; use redacted presence checks where possible.

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
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (5)

Credential Access

High
Category
Privilege Escalation
Confidence
91% confidence
Finding

Using commands like 'security list-keychains' and 'security find-identity -v' enumerates local keychain configuration and available signing identities. Even if private keys are not exported, this reveals credential presence and trust relationships that can aid reconnaissance or leak sensitive operational details when run in CI logs or shared support channels.

Content

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

md
env | grep IDENTITY || echo "IDENTITY not in environment"

   # Layer 3: Signing script
   echo "=== Keychain state: ==="
   security list-keychains
   security find-identity -v

Credential Access

High
Category
Privilege Escalation
Confidence
91% confidence
Finding

The keychain-inspection guidance encourages credential discovery behavior by listing keychains and signing identities, which can expose sensitive information about available credentials and code-signing setup. In the context of a broadly applicable debugging skill, this is more dangerous because users may paste the commands into production or CI workflows where the resulting data is broadly visible.

Content

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

md
# Layer 3: Signing script
   echo "=== Keychain state: ==="
   security list-keychains
   security find-identity -v

   # Layer 4: Actual signing

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The description says to use the skill when encountering 'any bug, test failure, or unexpected behavior, before proposing fixes,' which is broad enough to overlap with many ordinary development interactions. It does not provide narrower scope boundaries or exclusion conditions, increasing the chance of unintended invocation.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The section states 'Use for ANY technical issue' and then lists very broad categories like test failures, bugs, unexpected behavior, performance problems, and integration issues. This lacks explicit boundaries or negative examples, so the skill could be triggered for nearly any engineering task rather than a well-defined debugging context.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The diagnostic example explicitly instructs logging secret-related environment state and inspecting signing identities without any warning to avoid exposing sensitive values, identifiers, or credential inventory in logs. In real CI/CD or shared debugging contexts, this can leak whether credentials exist, which identities are configured, and other environment details that help attackers enumerate secrets and signing infrastructure.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.