Back to skill

Security audit

Meta Debugger

Security checks for vulnerabilities and agentic risk

Overview

The skill is mostly an in-memory debugging helper, but its install instructions create an avoidable package-installation risk.

Review before installing because the published install command should not be followed as written. The skill itself appears to be a simple local debugging helper, but install it only after removing the unnecessary pip install step or using an isolated environment.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • 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
Findings (1)

T08 · Insecure Dependencies

Error
Location
SKILL.md:52
Finding

Unnecessary Installation of Third-Party Packages Named After Python Standard-Library Modules

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, line 52
Vulnerability Type: Dependency confusion and unsafe package installation
Risk Level: High

Vulnerable Code

bash
pip install json traceback ast

Technical Analysis

The installation instructions direct users to install packages named json, traceback, and ast from pip. These names correspond to modules already provided by Python’s standard library and do not need to be installed separately.

As a result, pip may retrieve unrelated third-party distributions from the configured package index. These dependencies are unnecessary, unpinned, and not protected by package hashes. Package installation can execute distribution-controlled build or installation code with the privileges of the user running pip.

The implementation confirms that these dependencies are unnecessary: meta_debugger.py uses standard-library imports for json and traceback, while ast is not imported. No legitimate project functionality requires the documented pip command.

Attack Path

  1. A user follows the installation instructions in SKILL.md.
  2. The user runs pip install json traceback ast.
  3. pip searches its configured public or private package indexes for distributions with those names.
  4. An attacker-controlled, compromised, or otherwise unsafe distribution is selected.
  5. pip downloads the package and processes its build or installation metadata.
  6. Distribution-controlled code executes with the privileges and environment access of the invoking user.
  7. The package can compromise data or the environment within that privilege boundary.

This path depends on the availability and selection of an unsafe distribution; the audited project itself does not contain a malicious payload.

Impact Assessment

Successful exploitation could provide arbitrary code execution under the account running pip. Depending on that account’s permissions and environment, the package could:

  • Read or alter ...[truncated 536 chars]
Remediation
View remediation

Remediation Suggestions

  1. Remove the pip command because the implementation requires no external dependencies:
markdown
## Installation

No external dependencies are required. This Skill uses only Python standard-library modules.
  1. Do not publish or install third-party packages merely because their names match standard-library imports.

  2. If external dependencies are added later:

    • Declare only dependencies actually imported and required by the project.
    • Pin reviewed versions in a dependency or lock file.
    • Verify package ownership, provenance, and integrity before adoption.
    • Use package hashes where supported.
    • Restrict installation to trusted package indexes.
    • Perform installation in an isolated, least-privileged virtual environment.
    • Add automated dependency and supply-chain scanning to the release process.
  3. Add a clean-environment test confirming that the project works using only the supported Python runtime and its standard library.

Vulnerability Patterns
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Tool MisuseTool Parameter Abuse, Chaining Abuse, Unsafe Defaults
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Findings (5)

Credential Access

High
Category
Privilege Escalation
Confidence
70% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · meta_debugger.py (reported line 257)May include surrounding context.

python
return f"Value error: {error_message}"
        
        elif error_type == "KeyError":
            # Extract key from message
            match = re.search(r"['\"](.+?)['\"]", error_message)
            key = match.group(1) if match else "unknown"
            return f"Missing key: '{key}'"

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The skill description advertises a very broad, always-useful capability ('AI-powered self-debugging... fixes errors automatically... apply fixes autonomously') without defining clear invocation boundaries, permissions, or operational constraints. In an agent ecosystem, this can cause over-activation or inappropriate use on unrelated failures, increasing the chance the skill is given sensitive context and allowed to influence system behavior beyond a narrowly scoped debugging task.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The skill explicitly promotes automatic code patches, configuration fixes, and autonomous fix application, but the documentation does not provide strong warnings or enforceable safeguards around data loss, integrity damage, privilege boundaries, or unintended modifications. In context, a self-healing debugging skill is especially risky because it is designed to operate during failures, when context may be incomplete and automated changes can silently worsen outages or introduce security regressions.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The code enables autonomous remediation when auto_fix is set, immediately selecting and applying the top-ranked fix without any approval, policy check, or explicit user confirmation. In a self-healing/debugging skill, that creates a real integrity and availability risk because remediation actions may alter runtime behavior or state based on heuristic error analysis and could be triggered repeatedly on attacker-influenced inputs.

Content

No source excerpt is available for this finding.

Unsafe Defaults

Medium
Category
Tool Misuse
Confidence
80% confidence
Finding

Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.

Content

Scanner excerpt · meta_debugger.py (reported line 552)May include surrounding context.

python
'applied': False,
                'reason': 'safe_mode_enabled',
                'fix': fix,
                'suggestion': 'Review fix and apply manually or set safe_mode=False'
            }
        
        # Record fix attempt