Back to skill

Security audit

Debug Master

Security checks for vulnerabilities and agentic risk

Overview

This is a plain Markdown debugging guide with broad activation wording but no hidden code, persistence, credential handling, or unsafe installation behavior.

Installers should understand this skill is intended for Chinese-language debugging help and may activate on general debugging phrases. Review any generated tests or fixes before applying them, and avoid pasting secrets such as API keys or tokens into debugging logs.

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
  • 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 (3)

Vague Triggers

High
Category
Not specified by scanner
Confidence
95% confidence
Finding

The trigger phrases are broad, generic debugging terms like 'debug', '帮我看看', and '为什么不行', which are likely to appear in ordinary conversation and can cause unintentional activation. This increases the chance the skill intercepts requests outside a clear user opt-in boundary, creating routing and prompt-scope confusion rather than direct code-execution risk.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The manifest description embeds multiple vague trigger words in a free-form description without defining strict activation conditions. If platform logic or downstream tooling uses manifest text for discovery or invocation hints, this can further blur when the skill should activate and contribute to unintended engagement.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
88% confidence
Finding

The skill metadata and introductory text are written as a Chinese-only persona (“AI调试大师”) with no indication that users may choose another language. This creates a language/locale constraint that is not documented as optional or justified for a region-specific use case.

Content

No source excerpt is available for this finding.