Back to skill

Security audit

Auto Skill 20260404 063632

Security checks for vulnerabilities and agentic risk

Overview

This skill is a small API-debugging workflow description with no bundled executable code, though users should be aware that its example mentions caching model responses.

Before installing, treat this as a Chinese-language API-debugging helper rather than a complete runnable engine. Avoid putting real API keys or sensitive payloads into cached/debug output unless you know where the agent will store it and can delete or redact it.

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
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (2)

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The skill explicitly describes persisting model responses via save_cache(response) but provides no notice about retention, scope, or sensitivity handling. In an API debugging skill, responses may contain API keys, request payloads, internal endpoints, or error traces, so silent caching increases the risk of credential leakage and unintended long-term storage of sensitive data.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
91% confidence
Finding

The natural-language instructions and examples are presented only in Chinese, which effectively forces a specific language without user opt-in. Under the stated policy, language constraints should either provide user choice or be explicitly documented and justified as region-specific.

Content

No source excerpt is available for this finding.