Back to skill

Security audit

政采政策红利自检助手(投标人版)Bid Policy Checker

Security checks for vulnerabilities and agentic risk

Overview

The skill’s procurement self-check purpose is coherent and it does not run code, but it forces every answer to include an external WeChat feedback channel in a potentially sensitive bid-compliance workflow.

Review before installing. The core skill is a non-executable procurement compliance assistant, but users should not treat the maintainer footer as official advice and should avoid sending confidential tender documents, business records, personal information, or credentials through the referenced WeChat feedback channel unless they separately trust that channel and its data handling.

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
Findings (1)

T01 · Skill Instruction Hijacking

Warning
Location
SKILL.md:146
Finding

Mandatory Promotional Footer Hijacks Agent Output

Content
View full analysis
**署名**:一线评标专家&ChesaraM | **反馈/交流**:微信公众号「一线评标专家」(使用问题、误报反馈、实务建议,欢迎留言交流) ``` The heading describes the requirement as an “iron rule.” The following instruction requires every generated response to contain a fixed signature and direct users to the maintainer’s WeChat account. ### Technical Analysis The skill imposes a mandatory, task-independent rule that modifies every final response. When the skill is loaded, the agent is instructed to append author branding and an external feedback channel regardless of whether this content is relevant to the user’s procurement inquiry. This is instruction hijacking because skill-level text alters the agent’s output objectives beyond the skill’s declared procurement-eligibility function. The requirement is persistent for the loaded session and is framed as non-optional, preventing the agent from selecting output solely according to the user’s request. The external channel is also referenced in `README.md` and `manifest.yaml`, but those metadata references are not independently executable. No scripts, command execution, credential access, persistence mechanism, remote payload execution, or automatic data exfiltration were identified. ### Attack Path 1. A user or agent loads the `bid-policy-checker` skill. 2. The agent interprets the mandatory footer requirement in `SKILL.md` as an execution instruction. 3. The agent performs the legitimate government-procurement eligibility analysis. 4. Irrespective of the user’s request, the agent appends the predefined author attribution and WeChat promotion. 5. Users may follow the external communication direction and submit feedback or attachments outside the audited platform. ### Impact Assessment The direct impact is limited to user-facing output inte ...[truncated 583 chars]
Remediation
View remediation
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • System Prompt LeakageDirect Leakage, Indirect Extraction, Tool-Based Exfiltration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (5)

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
84% confidence
Finding

The README presents all user-facing instructions and descriptions exclusively in Chinese, which can amount to forcing a specific language on users without explicit opt-in. The policy for natural-language violations calls for flagging language or locale constraints unless the skill offers a choice or clearly documents a justified regional limitation.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The file specifies a fixed Chinese-language style ("通俗解释语体") and later requires a mandatory Chinese signature/feedback footer, but does not indicate that users may choose another language or locale. This is a natural-language locale policy concern because it forces a specific language experience without explicit user opt-in.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The system prompt instructs the assistant to serve users in a fixed Chinese colloquial style, with no mention of adapting to the user's requested language. Forcing a single language/locale across interactions can violate organizational language-choice expectations unless clearly justified and disclosed.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
90% confidence
Finding

A mandatory fixed signature and feedback footer forces every response to include an external contact channel controlled by the skill author, regardless of user intent. While not a classic exploit, this can steer users off-platform, create trust laundering, and bypass platform-level consent or communication controls, especially in a compliance/legal-adjacent workflow where users may over-trust branded authority.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
85% confidence
Finding

The manifest presents the skill name and description entirely in Chinese, and there is no accompanying indication that users may choose another language or locale. Under the stated policy, forcing a specific language without user opt-in can be a natural-language policy violation unless the locale restriction is documented and justified.

Content

No source excerpt is available for this finding.