Back to skill

Security audit

Debugging Log Analyser

Security checks for vulnerabilities and agentic risk

Overview

This is a straightforward log-debugging prompt skill with no code execution, persistence, or hidden data handling, though users should redact sensitive log content before using it.

Installers should be comfortable using this as a debugging assistant, but users should provide minimized excerpts and redact API keys, tokens, passwords, customer data, internal hostnames, and other sensitive production details before sharing 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
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (2)

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

The skill explicitly asks users to provide raw logs, stack traces, environment details, and prior debugging context without any warning to remove secrets, tokens, credentials, personal data, or production-sensitive information. In practice, logs frequently contain API keys, session tokens, internal hostnames, file paths, customer data, and other sensitive artifacts, so the skill can normalize unsafe disclosure of high-value data.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The usage examples include very broad, everyday phrases such as "Why is this crashing?" and "Debug this log for me," which can cause the skill to be invoked in situations broader than intended. Over-broad triggering increases the chance the agent solicits logs or diagnostic context unnecessarily, which can expose sensitive operational data or cause the skill to override more appropriate, narrower workflows.

Content

No source excerpt is available for this finding.