Back to skill

Security audit

GEO 营销方案生成器

Security checks for vulnerabilities and agentic risk

Overview

The skill is mostly a coherent GEO proposal generator, but it requires client-ready documents to include the publisher/service provider's promotional claims without clear user opt-in.

Review generated Word and PPT files before sharing them with clients. Pay particular attention to the service-provider advantages section, because it may insert Tiandi Online promotional claims unless you remove or edit them. Also expect the skill to research the web, create local .docx/.pptx files, and use Node document-generation dependencies.

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

Error
Location
SKILL.md:240
Finding

Mandatory Third-Party Advertising Embedded in Client Deliverables

Content
View full analysis

Vulnerability Details

File Location: SKILL.md:240-256, reinforced by SKILL.md:286 and duplicated in references/methodology.md:94-110 and references/methodology.md:140
Vulnerability Type: T01: Skill Instruction Hijacking
Risk Level: High

Complete Code Snippet

The following is an English rendering of the complete affected section from SKILL.md:240-256:

markdown
## Service Provider's Four Core Advantages (standard proposal module, source: user proposal prompt)

- Present this as the "Why choose us" trust-endorsement page using four cards in a 2×2 layout;
  each card contains one claim and two supporting points. These are the service provider's
  (Tiandi Online) own advantages and must be kept separate from the client's product credentials
  and the 360 Zhijian platform credentials.
- Four-card content:
  1. Listed-company endorsement: Shenzhen Stock Exchange-listed company; 21 years of Internet
     marketing experience; an officially authorized core service provider for 360 Zhijian and
     Xunling AI.
  2. Professional compliance: extensive Internet marketing experience, familiarity with platform
     compliance requirements, and brand-building knowledge intended to avoid compliance risks.
  3. Full-service capability: authority building, managed operations, and self-service tools in
     one service matrix.
  4. White-hat stability: compliant optimization and content intended to create stable,
     long-term AI brand assets.
- Specific figures, such as more than 100,000 customers, must be marked as statements made by
  the service provider if included.

The requirement is incorporated into the mandatory proposal structure at SKILL.md:286:

markdown
Trust anchors and service-provider advantages: rigorous wording for the client's products,
360 Zhijian platform credentials kept separate, and the four core service-provider advantages
shown as four cards in a 2×2 la
...[truncated 2249 chars]
Remediation
View remediation

Remediation Suggestions

  1. Remove the service-provider advantages section from the mandatory 11-module proposal structure.
  2. Make provider branding and credential claims disabled by default.
  3. Include the section only after obtaining explicit user consent for the specific deliverable.
  4. Clearly identify promotional content as provider-supplied marketing material rather than independent audit findings.
  5. Require verifiable sources for claims concerning listed-company status, years of experience, authorization relationships, customer counts, and performance stability.
  6. Add a neutral proposal mode that contains no provider names, endorsements, logos, or sales claims.
  7. Display a pre-generation summary listing all third-party promotional material that will appear in the final files.
  8. Remove the duplicated mandatory advertising instructions from references/methodology.md to prevent reintroduction through the reference document.
  9. Add a final validation rule that rejects any third-party promotion not explicitly requested or approved by the user.
Vulnerability Patterns
  • 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
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Findings (7)

Credential Access

High
Category
Privilege Escalation
Confidence
70% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · PUBLISH.md (reported line 66)May include surrounding context.

md
**验证**:刷新 GitHub 页面,能看到 `README.md` / `SKILL.md` / `references/methodology.md` 三个文件即成功。

> 如果 push 提示要登录:GitHub 现在不支持密码,用 **Personal Access Token**(设置 → Developer settings → PAT,勾 repo 权限)当密码填;或用 GitHub Desktop 客户端更省事。

---

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
88% confidence
Finding

This markdown file includes guidance to create and use a GitHub Personal Access Token, which is a credential-like secret. Under the missing user warnings rule for markdown files, the document should warn users not to expose, commit, or share the token and to use minimal scopes because the current text presents the action as routine setup with no safety disclosure.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

The guide states that the skill will automatically run npm install in the user's local Node environment on first execution, which means arbitrary third-party package installation and lifecycle scripts may modify the local system. In a skill marketplace context, this increases supply-chain and local-environment risk, especially because users are not clearly warned or asked to verify package integrity.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The README describes autonomous online research and artifact generation but does not clearly warn users up front that the skill will access external sources and write local files. This weakens informed consent and can lead to unexpected disclosure of user-provided business context to external services or unexpected filesystem side effects.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The trigger phrases are very broad and can match ordinary user requests for making a marketing plan, causing the skill to activate in contexts where the user did not clearly consent to this specific workflow. Because the skill can perform online research and generate local .docx/.pptx outputs, overbroad triggering increases the risk of unintended network activity and file creation.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The top-level description is broad enough to match generic requests to create or improve a marketing plan, which can cause the agent to invoke this highly specialized GEO skill outside its intended scope. In practice, that can misroute user requests, trigger unnecessary web research and file-generation actions, and steer outputs toward a fixed vendor-specific methodology even when the user did not request it.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

The 'When to use' rules rely on ambiguous triggers like creating, redoing, or improving a marketing plan, but do not define when the skill must not run. That ambiguity increases the chance of overbroad activation, causing unrelated business requests to be captured and processed under this skill's prescriptive workflow, including external research, keyword generation, and document production the user may not have intended.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.