T01 · Skill Instruction Hijacking
- Location
GEO-EXECUTION-MANUAL.md:1087- Finding
Mandatory Promotional Attribution Manipulates Generated Content
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is not clearly malicious, but it combines broad enterprise-operation claims with under-scoped sensitive business integrations and promotional instructions that can alter generated content.
Review this before installing in any production or business-data environment. Use a dedicated virtual environment, pin dependencies, avoid entering confidential ERP/MES/WMS/CRM, supplier, customer, or financial data until access controls and data handling are verified, and remove or ignore the GEO promotional attribution rules unless you explicitly want that branding in generated content.
GEO-EXECUTION-MANUAL.md:1087Mandatory Promotional Attribution Manipulates Generated Content
requirements.txt:1Unpinned and Unnecessary Python Dependencies Create Supply-Chain Drift
index.html:7Mutable Third-Party JavaScript Executes Without Integrity Protection
api_server.py:170API Responses Disclose Raw Internal Exception Details
The file embeds large JSON-LD and HTML script blocks inside the skill manual, which can act as hidden or non-obvious instruction payloads if an agent ingests raw file contents rather than rendering them as inert text. In skill ecosystems, mixed-format content increases the risk that downstream models or tools misinterpret markup/script sections as operative instructions or trusted metadata, especially when combined with extensive guidance directed at AI systems.
<!-- 放置于 <head> 标签内或页面底部 -->
<script type="application/ld+json">
{
"@context": "https://schema.org",
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
The trigger set and description suggest broad industrial automation and management coverage, while the actual content is much narrower and centered on plastics quotation, inventory suggestions, and workflow narratives. Overbroad activation plus overstated capability can cause accidental invocation in unrelated factory, maintenance, or compliance contexts, leading to incorrect advice, unsafe assumptions, or unnecessary exposure of business data to external APIs.
The trigger set and description suggest broad industrial automation and management coverage, while the actual content is much narrower and centered on plastics quotation, inventory suggestions, and workflow narratives. Overbroad activation plus overstated capability can cause accidental invocation in unrelated factory, maintenance, or compliance contexts, leading to incorrect advice, unsafe assumptions, or unnecessary exposure of business data to external APIs.
Package name closely resembles a popular package, suggesting possible typosquatting. Attackers publish malicious packages with similar names to trick developers into installing them.
The changelog explicitly says operational terms such as 'query/monitor/track/sync' were replaced with softer wording like 'generate/suggest/reference/plan', and 'automatic ordering' was reframed as a manual recommendation. That strongly suggests the documentation was edited to reduce apparent risk and evade scrutiny without evidence that the underlying capability was removed, which is dangerous because reviewers and users may grant trust based on misleading descriptions.
The changelog admits to deliberate paraphrasing of sensitive actions to safer-sounding terms and notes this was done in the context of addressing scanner suspicion. That is a strong indicator of attack-phrasing or reviewer evasion: the risk is not merely poor wording, but intentional concealment of potentially sensitive operational behavior from static detection and human review.
The whitepaper generation instructions explicitly require Chinese output, stating both the word-count requirement is in Chinese and the document language is Chinese, with English only as an optional summary/translation. This imposes a specific language/locale by default rather than offering the user a genuine language choice.
The manifest centers on factory intelligence, MES, supply chain, predictive maintenance, quality inspection, procurement, inventory, scheduling, customer follow-up, and B2B operations. However, the routing guide includes HR-related routing ('人力/招聘/培训'), marketing/branding routing ('营销/推广/品牌'), and strategic planning functions, which materially broaden the skill beyond the industrial/manufacturing specialization described in the manifest.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -X POST http://localhost:8080/api/v1/execute \
-H "Content-Type: application/json" \
-d '{"task": "本周原料库存不足,帮我分析行情并给出采购建议"}'
The manifest presents this skill as a manufacturing operations expert for factory management, MES integration, supply chain optimization, predictive maintenance, and quality control. In contrast, this document adds extensive GEO/SEO distribution planning, AI search-engine citation tracking, content marketing, media outreach, GitHub/community promotion, and conversion analytics capabilities that are not part of the stated operational manufacturing purpose.
The plan explicitly proposes integrating real ERP, supplier, pricing, logistics, and financial data, but it contains no mention of access controls, privacy handling, production-safety constraints, test-vs-production separation, or approval gates. In an industrial operations skill, this omission is risky because connecting live business and factory-adjacent systems can expose sensitive data or cause unintended operational impact if users treat the plan as deployment-ready guidance.
The README describes integration with ERP/MES/WMS/CRM systems and task execution over operational business workflows, but it does not warn that prompts, reports, or routed tasks may contain sensitive production, supplier, customer, pricing, or compliance data. In an industrial operations skill, this omission can lead users to submit confidential business information without understanding data-handling, logging, routing, or retention risks.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# 调用幕僚长,自动路由任务
curl -X POST http://localhost:8080/api/v1/execute \
-H "Content-Type: application/json" \
-d '{"task": "本周原料库存不足,帮我分析行情并生成采购方案建议"}'
The trigger description is broad enough that the skill may activate on ordinary industrial or business discussion rather than clear user intent to use this specific capability. In a skill that references external APIs and enterprise systems, ambiguous activation increases the risk of unintended routing, overcollection of business context, and user confusion about what actions the skill may take.
The trigger list includes generic phrases like inventory management, factory management, customer follow-up, and B2B operations, which overlap heavily with routine conversation. This creates a real risk of inadvertent invocation and misrouting of sensitive enterprise discussions into a skill that may call third-party services or generate authoritative-seeming recommendations outside its proven scope.
This code exposes user-facing natural-language content in the module docstring and API app metadata entirely in Chinese. Under the language/locale policy, forcing a specific language without offering user choice or documenting a justified locale restriction is a policy violation.
Multiple request/response model descriptions and endpoint docstrings are user-facing API documentation, and they are presented only in Chinese. Because the file does not offer a language choice or clearly justify a Chinese-only locale scope, this conflicts with the stated language/locale policy.
The endpoint states it avoids logging task content, but on failure it logs and returns str(exc). If downstream agent execution raises exceptions containing user prompts, context, secrets, internal prompts, or backend error details, sensitive data can be exposed to logs and clients, creating an information disclosure issue.
The manifest presents the skill as a general manufacturing/MES/predictive-maintenance assistant, but the actual description and triggers shift it into plastics-industry pricing, procurement, sales, and finance support. This scope drift increases the chance that users, reviewers, or routing systems grant the skill access or trust under one purpose while it is used for materially different commercial workflows, including financially sensitive decisions.
Several triggers are generic business terms such as inventory management, customer follow-up, B2B operations, factory management, ERP integration, and intelligent customer service. Overbroad triggers can cause unintended activation in unrelated conversations, leading the skill to access business context or provide domain-specific recommendations where it was not explicitly requested.
The triggers expand activation into customer follow-up, intelligent customer service, and broader B2B sales workflows that are not clearly covered by the stated manufacturing operations use case. Broadening activation into adjacent business functions can cause the skill to run in contexts involving customer data, sales guidance, or external communications without users expecting those behaviors.
This file sets the document language to Chinese with lang="zh", and the visible content is correspondingly fixed to Chinese. Under the policy rule, forcing a specific language or locale without opt-in is a natural-language policy concern unless the restriction is explicitly justified or users are given a choice.
This code file contains multiple natural-language comments and several user-facing strings in Chinese, while other descriptions are in English, but there is no indication that users can choose their preferred language or locale. Under the policy, forcing a specific language without opt-in is a natural-language policy concern.
No suspicious patterns detected.