Back to skill

Security audit

Lingqu Banner Config

Security checks for vulnerabilities and agentic risk

Overview

The skill matches its banner-operations purpose, but it gives broadly defined chat participants enough influence to change persistent business workflow state and trigger delegated production promotion actions.

Review before installing. Use this only in a controlled Lingqu Banner workflow, restrict eligible groups and senders, and add explicit confirmation or authorization checks before accepting schedules, cancellations, replacements, or delegated promotion mutations. Operators should also document how submitted images, URLs, and campaign metadata are handled by promotion-apply-skills.

Vulnerability Patterns
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
  • 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)

T05 · Unauthorized Access and Privilege Escalation

Error
Location
references/phase-three-exceptions.md:114
Finding

Untrusted Group Participants Can Trigger Schedule Mutations and Terminal Project Cancellation

Content
View full analysis
Phase Three. ``` ```text Trigger condition: Who: Any person who mentions the digital employee in a group. What: Sends a frame schedule by saying "latest frame schedule" or by including the schedule format. After receipt, reply: "Received the latest frame schedule. Processing has started." ``` ```text Comparison B: Tracking table -> scheduled projects For rows whose date equals the current schedule date and whose state is "Reserved" or "Configured," if the project cannot be found in the schedule: 1. Change the state to "Canceled." 2. Record that it disappeared from the schedule and will not run this period. 3. Notify the project manager that it has been marked as not running. ``` ```text Cancellation trigger: Any person, including a project manager or the named operator, says that a project is canceled, delayed, not running this period, or abandoned. Processing: 1. Search the tracking table for the project. 2. The digital employee changes only the tracking table. 3. Change the state to "Canceled," which is terminal. 4. Record the cancellation in the remarks column. 5. Send confirmation. ``` The same Phase Three workflow also directs the agent to process schedule time/port inconsistencies by delegating promotion copying and modification: ```text If the time period or port is i ...[truncated 3839 chars]
Remediation
View remediation
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (23)

Vague Triggers

High
Category
Not specified by scanner
Confidence
97% confidence
Finding

The cancellation trigger is explicitly authorized for '任何人' and accepts broad natural-language phrases like cancel, delay, or 'not doing it this period'. In this skill, that can let an unrelated participant in a group conversation cause the tracking sheet to mark a promotion as cancelled, creating operational disruption and potential loss of scheduled inventory even if backend cancellation still requires PM action.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

Stage-three activation is especially risky because it accepts not only a fixed phrase but also any message 'containing schedule format,' which is inherently fuzzy and easy to spoof. An attacker or careless participant in a group chat could trigger bulk comparison and cancellation/replacement logic using loosely formatted content, potentially corrupting workflow state or causing improper downstream actions.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

Stage-three activation is especially risky because it accepts not only a fixed phrase but also any message 'containing schedule format,' which is inherently fuzzy and easy to spoof. An attacker or careless participant in a group chat could trigger bulk comparison and cancellation/replacement logic using loosely formatted content, potentially corrupting workflow state or causing improper downstream actions.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

Medium
Category
Not specified by scanner
Confidence
88% confidence
Finding

The manifest and top-level documentation frame the skill as only the 'brain' that delegates real backend writes to promotion-apply-skills, but later sections explicitly assign this skill responsibility for writing the shared tracking sheet and sending group/DM messages. Those are still real side-effecting operations, so the stated limitation is narrower than the documented behavior.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
89% confidence
Finding

The 'single entry' rule routes all natural-language requests related to this domain into the skill with insufficiently precise boundaries, increasing the blast radius of misclassification. Because this skill can update shared tracking state and delegate real backend operations to another skill, overbroad intake raises the chance that unrelated or malformed requests will be interpreted as actionable business tasks.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The document is entirely written in Chinese and repeatedly instructs the agent to interact with PMs using Chinese labels and phrases such as '问 PM' and '让 PM 选'. There is no indication that the skill supports other languages, offers opt-in language selection, or is limited to a China-specific/regional workflow, so this constitutes a natural-language locale policy concern.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

The document is written entirely in Chinese and repeatedly prescribes fixed operator/user-facing phrasing such as required reply formats, but it does not mention any option to adapt language based on user preference. Under the policy rule for natural-language violations, this is a locale/language constraint that is not presented as optional or region-justified.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The file includes mandated user-facing dialogue templates in Chinese, such as the DM script, and does not indicate that language should match the user's preference or be selectable. This creates a language/locale policy concern because the skill effectively forces a specific language for interaction.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

The standardized completion messages are specified only in Chinese and are required after successful pre-occupation, but the file does not mention any user opt-in or locale restriction. Under the policy, fixed-language behavior is a natural-language violation unless choice or justified scope is provided.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The trigger activates on any group mention plus loosely defined scheduling-formatted text, which increases the chance of accidental or adversarial activation. In this skill, that matters because downstream behavior includes state changes, copy/update workflows, and notifications, so a spoofed or malformed message can initiate impactful processing.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

This section instructs phase three to mutate tracking state (for example setting N/O fields and sending PM notifications) as part of comparison handling, which weakens separation of duties promised in the skill description. If a broad trigger or bad parse causes a false match, the agent could incorrectly cancel items or message users based on unverified state transitions.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

These instructions expand a compare phase into operational workflows that trigger promotion-copy, promotion-update, preoccupy, material configuration, table writes, and PM notifications. That creates a powerful side-effect surface from schedule text parsing alone, so an incorrect comparison or ambiguous project match can cause unintended duplication, reservation, or approval-state changes in production systems.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
88% confidence
Finding

The material-change trigger relies on broad phrases such as '换物料', '换图', '换链接', and '换角标' in DM or group chat, which are easy to mention conversationally without intending to invoke workflow actions. In this context, the skill can start a reconfiguration path that updates tracked material fields and may lead to re-approval actions, so ambiguous triggering is operationally unsafe.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
84% confidence
Finding

The file prescribes exact Chinese response wording for user-facing interactions, and throughout the document all operational prompts are fixed in Chinese. There is no indication that users may opt into another language or that the locale restriction is explicitly justified as a region-specific requirement.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The edge-case rule still allows processing whenever someone @mentions the digital employee or says trigger keywords, which keeps invocation criteria broad and prone to accidental or spoofed activation. In a multi-user group setting, this increases the chance of unauthorized or mistaken state changes across cancellation, rescheduling, or material-handling flows.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The skill explicitly instructs the agent to forward raw images or image URLs to another technical system for downloading, validation, cropping, and re-upload, but it does not require transparent notice or consent to the sender about downstream processing. This creates a privacy and data-handling risk because users may assume the material stays within the current chat workflow while it is actually transmitted and processed by additional systems.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The trigger is defined as a PM sending any one of several material types, including just an image or link, which is a very broad condition in everyday work chats. The file does not provide clear exclusion conditions or narrow invocation phrases, so ordinary PM-to-DM sharing could unintentionally match this skill.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
85% confidence
Finding

The instruction says that when a PM sends an image, the agent should directly accept it and only confirm which project it belongs to. This makes activation depend on a very common chat behavior without defining when an image is merely informational versus intended to start the material configuration process.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

This section operationalizes downstream transfer of PM-provided raw images, URLs, promotion IDs, and business metadata to another skill and backend services, yet no user-visible notice or approval checkpoint is required. In a workflow that moves content across systems and may persist it, the lack of explicit disclosure increases the chance of unauthorized or unexpected processing of potentially sensitive campaign materials.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

Low
Category
Not specified by scanner
Confidence
83% confidence
Finding

The manifest description says催办 is handled by 灵渠助手, implying this skill no longer performs reminder/escalation messaging. However, the workflow later requires the skill to notify 王可 after repeated handoff failure, which is an additional escalation behavior not reflected in the manifest summary.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
87% confidence
Finding

The file hardcodes user-facing prompts and responses in Chinese, such as the fallback question and the required group reply/DM behavior, without indicating that users may choose another language. This can violate language or locale policy when a skill forces one language without opt-in.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
88% confidence
Finding

The instructions prescribe a fixed Chinese response message and the entire operational text assumes Chinese-only interaction, but there is no user opt-in or explicit justification that the skill is region- or language-limited. Under the policy, forcing a specific language without choice can be a natural-language policy violation.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
82% confidence
Finding

All instructions and quoted user-facing DM templates are fixed to Chinese, which can impose a language policy constraint on users or operators. The file does not indicate that language choice is optional or that the skill is intentionally limited to a Chinese-only audience for a documented reason.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.