Back to skill

Security audit

skill-sub

Security checks for vulnerabilities and agentic risk

Overview

This skill is a real chain-planning tool, but it has under-disclosed high-impact local write/delete, configuration, and agent-instruction risks that should be reviewed before installation.

Install only if you are comfortable reviewing and constraining this skill first. It should be limited to a dedicated data directory, patched to validate path components, require explicit confirmation for delete/scheduler/self-healing actions, protect or remove the local settings HTTP API, and accurately declare memory/log access and critical writes.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • 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
Findings (7)

T01 · Skill Instruction Hijacking

Error
Location
scripts/chain_manager.py:843
Finding

Mandatory Agent-facing scheduling directives can hijack the current workflow

Content
View full analysis
") lines.append("! 未注册前,调度不会生效。") ``` ### Technical Analysis The Skill emits imperative, Agent-facing instructions that require an AI Agent to invoke an unspecified platform scheduling API and prevent the normal workflow from continuing until registration is completed. The audited code does not define or constrain that external scheduler integration, its endpoint, authorization model, or resulting privileges. Because schedule properties originate in chain metadata, an attacker able to supply or modify a chain can cause the Skill to emit these mandatory directives. The output is explicitly designed to be consumed as AI execution instructions rather than displayed as passive metadata. ### Attack Path 1. An attacker creates or modifies a chain with a `schedule` object whose `registered` field is false. 2. The chain is created or passed ...[truncated 876 chars]
Remediation
View remediation

T01 · Skill Instruction Hijacking

Error
Location
scripts/chain_executor.py:316
Finding

Stored prompt injection through untrusted chain fields

Content
View full analysis
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Error
Location
scripts/chain_manager.py:370
Finding

Arbitrary recursive directory deletion through chain-name path traversal

Content
View full analysis
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Error
Location
scripts/chain_manager.py:394
Finding

Arbitrary file creation and overwrite through chain-name path traversal

Content
View full analysis
/chain.json` in write mode. 5. An existing file is truncated and replaced, or a new unauthorized file is created. 6. The index may retain the escaped path, facilitating later reads or deletion. ### Impact Assessment The attacker can create or overwrite files named `chain.json` in attacker-selected wr ...[truncated 220 chars]
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Error
Location
scripts/settings.py:137
Finding

Unauthenticated wildcard-CORS local configuration API

Content
View full analysis
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Error
Location
scripts/step_indexer.py:729
Finding

Blueprint output path traversal and unrestricted source-directory access

Content
View full analysis
Remediation
View remediation

T05 · Unauthorized Access and Privilege Escalation

Warning
Location
SKILL.md:8
Finding

Declared permission metadata understates sensitive reads and destructive writes

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • System Prompt LeakageDirect Leakage, Indirect Extraction, Tool-Based Exfiltration
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
Findings (79)

Tp4

High
Category
MCP Tool Poisoning
Confidence
93% confidence
Finding

The declared orchestration functionality is not implemented, while interface matching and gap-analysis capabilities are introduced instead. While not inherently malicious, such undocumented analytical behavior can influence downstream automation decisions and expose internal interface metadata unexpectedly.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
97% confidence
Finding

The declared orchestration functionality is not implemented, while interface matching and gap-analysis capabilities are introduced instead. While not inherently malicious, such undocumented analytical behavior can influence downstream automation decisions and expose internal interface metadata unexpectedly.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
96% confidence
Finding

The declared orchestration functionality is not implemented, while interface matching and gap-analysis capabilities are introduced instead. While not inherently malicious, such undocumented analytical behavior can influence downstream automation decisions and expose internal interface metadata unexpectedly.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
97% confidence
Finding

The declared orchestration functionality is not implemented, while interface matching and gap-analysis capabilities are introduced instead. While not inherently malicious, such undocumented analytical behavior can influence downstream automation decisions and expose internal interface metadata unexpectedly.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
93% confidence
Finding

The declared orchestration functionality is not implemented, while interface matching and gap-analysis capabilities are introduced instead. While not inherently malicious, such undocumented analytical behavior can influence downstream automation decisions and expose internal interface metadata unexpectedly.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
97% confidence
Finding

The declared orchestration functionality is not implemented, while interface matching and gap-analysis capabilities are introduced instead. While not inherently malicious, such undocumented analytical behavior can influence downstream automation decisions and expose internal interface metadata unexpectedly.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

The declared orchestration functionality is not implemented, while interface matching and gap-analysis capabilities are introduced instead. While not inherently malicious, such undocumented analytical behavior can influence downstream automation decisions and expose internal interface metadata unexpectedly.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
95% confidence
Finding

The declared orchestration functionality is not implemented, while interface matching and gap-analysis capabilities are introduced instead. While not inherently malicious, such undocumented analytical behavior can influence downstream automation decisions and expose internal interface metadata unexpectedly.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
95% confidence
Finding

The declared orchestration functionality is not implemented, while interface matching and gap-analysis capabilities are introduced instead. While not inherently malicious, such undocumented analytical behavior can influence downstream automation decisions and expose internal interface metadata unexpectedly.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
95% confidence
Finding

The declared orchestration functionality is not implemented, while interface matching and gap-analysis capabilities are introduced instead. While not inherently malicious, such undocumented analytical behavior can influence downstream automation decisions and expose internal interface metadata unexpectedly.

Content

No source excerpt is available for this finding.

Ae1

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

Scanner excerpt · SKILL.md (reported line 96)May include surrounding context.

md
> 📚 **渐进式加载**:本技能采用渐进式 MD 体系,`SKILL.md` 为入口(≤230行),详细内容拆分到 `references/*.md` 按需加载。

Description-Behavior Mismatch

High
Category
Not specified by scanner
Confidence
97% confidence
Finding

The adhesion step adds undocumented execution behavior: manual execution by the LLM, auto execution via tools/scripts, and self-healing replacement of steps by scanning the skill library. This materially changes the trust boundary of the skill from planning data structure management to autonomous capability discovery and execution, creating a path for unexpected actions not disclosed in the stated description.

Content

No source excerpt is available for this finding.

Context-Inappropriate Capability

High
Category
Not specified by scanner
Confidence
98% confidence
Finding

The documented self-healing flow instructs the system to scan installed skills and scripts, then automatically upgrade an adhesion step into a skill step or execute tool/script-based solutions. That behavior enables dynamic capability expansion and indirect code execution selection beyond the stated planner/editor role, which is especially dangerous because it can activate newly available tools without a fresh security decision by the user.

Content

No source excerpt is available for this finding.

Intent-Code Divergence

High
Category
Not specified by scanner
Confidence
98% confidence
Finding

User-facing messages state that the platform has confirmed scheduled execution, but the implementation only edits local JSON. This is dangerous because operators, other components, or automated governance may rely on a false assurance that a scheduled action is active, causing missed controls, phantom automation, or deceptive audit trails.

Content

No source excerpt is available for this finding.

Hidden Instructions

High
Category
Prompt Injection
Confidence
70% confidence
Finding

Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.

Content

Scanner excerpt · scripts/settings.html (reported line 218)May include surrounding context.

html
<h1>skill-sub</h1>
  <p class="subtitle">v1.2.0 &mdash; Chain Executor Settings</p>

  <!-- Memory Reference -->
  <div class="field-group">
    <h2><span class="icon">&#128218;</span> Memory &amp; Context</h2>
    <div class="field">

Direct Prompt Extraction

High
Category
System Prompt Leakage
Confidence
85% confidence
Finding

Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.

Content

Scanner excerpt · scripts/skill_extractor.py (reported line 198)May include surrounding context.

python
if instruction and instruction not in instructions:
            instructions.append(instruction)

    return instructions

def extract_key_steps(content):
    """提取关键执行步骤(从代码块、列表、流程描述中)"""

Undeclared Tool Scope

Medium
Category
MCP Least Privilege
Confidence
91% confidence
Finding

The skill advertises no explicit tool scope while its documented behavior implies file reads/writes, environment access, and possibly network-facing functionality. This creates a capability-transparency gap: operators and downstream agents cannot accurately assess what the skill may access, increasing the chance of over-privileged or unintended execution.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
89% confidence
Finding

L008 的描述全文以中文固定表述技能用途,但文档中未说明这是面向中文用户的特定区域技能,也未提供语言选择或用户 opt-in。按规则,强制特定语言而没有选择机制或正当限定,属于自然语言层面的语言/locale 策略风险。

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

Overly broad trigger phrases such as generic planning or ordering language can overlap with ordinary conversation, causing accidental activation. Because the skill appears to have broader-than-declared local access and stateful behavior, false activations increase the chance of unnecessary file reads, writes, or pipeline interference.

Content

No source excerpt is available for this finding.

Intent-Code Divergence

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

The trigger rules are internally contradictory: single-skill tasks are both recommended and discouraged. In an agent-routing context, ambiguous activation boundaries can cause the skill to run in unintended situations, expanding exposure to its undeclared file/state behaviors and reducing operator control.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

Conflicting positive and negative trigger conditions make it unclear when the skill should activate, which is a security issue in autonomous systems because routing becomes non-deterministic. Non-deterministic activation can bypass user intent and invoke a more capable skill than necessary.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The metadata is written entirely in Chinese and the triggers are Chinese-only, which effectively constrains interaction language without any explicit user opt-in or multilingual fallback. In an orchestration skill, this can lead to misrouting, misunderstanding of user intent, or silent activation biases for Chinese phrasing while excluding or confusing users in other languages.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The trigger phrases are broad enough to match common planning and sequencing requests, which can cause the skill to activate outside its intended scope. Because this skill is an orchestration and chain-management tool, unintended activation is more dangerous than in a narrow utility skill: it may steer user requests into workflow editing or execution planning when the user did not ask for that behavior.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The document explicitly promotes executing self-authored scripts in auto/hybrid adhesion modes but provides no safety constraints, trust boundary, permission model, or validation requirements. In this skill context, those scripts are generated or selected to bridge missing automation gaps, which makes it easy for an LLM-driven workflow to create and run filesystem-impacting or host-impacting code without adequate guardrails.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The self-healing mechanism instructs the system to scan sibling skill directories, search SKILL.md content, and automatically rewrite execution plans by upgrading adhesion steps to skills. That creates a dangerous trust boundary failure: untrusted or newly added local skills can influence plan resolution and execution behavior, potentially causing the agent to select adversarial skills or silently alter workflows without user review.

Content

No source excerpt is available for this finding.

Static analysis

Detected: suspicious.dynamic_code_execution

Dynamic code execution detected.

Critical
Code
suspicious.dynamic_code_execution
Location
scripts/step_indexer.py:58