Back to skill

Security audit

AIDLC Bug Killer

Security checks for vulnerabilities and agentic risk

Overview

This is a Markdown-only Chinese bug-fixing workflow skill that writes project bug-tracking documents and does not show hidden execution, credential access, network use, or persistence.

Install this if a Chinese-language, file-based multi-agent bug workflow fits your project. Expect it to create and move bug-report markdown files and update a project changelog; review those changes as normal code/documentation changes.

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
  • 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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (2)

Natural-Language Policy Violations

Medium
Confidence
92% confidence
Finding
The manifest description and the entire operational guidance are written in Chinese, and the workflow implicitly requires agents to operate in Chinese. There is no indication that the user can choose another language or that the locale restriction is required for a region-specific or compliance-related purpose.

Natural-Language Policy Violations

Medium
Confidence
95% confidence
Finding
The markdown template is entirely written in Chinese, including all headings, status labels, and field names, and it provides no indication that users may choose another language. Under the policy, forcing a specific language without user opt-in is a natural-language policy violation unless the locale restriction is explicitly justified.

Static analysis

No suspicious patterns detected.