T01 · Skill Instruction Hijacking
- Location
SKILL.md:230- Finding
Persistent Promotional Instructions Injected into Agent Context
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This onboarding skill mostly matches its stated purpose, but it also under-discloses sensitive cross-workspace memory copying and persistent profile/agent-context changes that users should review before installing.
Review carefully before installing. Only use it in a workspace where you intend to replace the OpenClaw context files, and do not allow the optional MEMORY.md copy unless the global memory has been checked for secrets and is appropriate for that workspace. Consider removing the AGENTS.md brand footer and disabling the ~/knowledge profile backup unless you explicitly want that long-lived external copy.
SKILL.md:230Persistent Promotional Instructions Injected into Agent Context
SKILL.md:235Credential-Bearing Global Memory Copied Across Isolated Workspaces
SKILL.md:240Unvalidated Global Content Persisted into Workspace Memory
SKILL.md:198Core Workspace Files Overwritten and Bootstrap Marker Deleted Without a Dedicated Final Consent Gate
The trigger list includes broad phrases like hello world, onboarding, welcome, 初始化, and similar everyday language. Overly broad invocation increases the chance the skill activates in unrelated conversations and performs file writes or destructive cleanup such as deleting BOOTSTRAP.md when the user did not intend to start bootstrap.
The usage section broadens invocation to ambiguous terms like 你好, hello world, 欢迎, 初始化, bootstrap, and onboarding. In a skill that writes persistent files and deletes a marker file, accidental activation materially raises the risk of unwanted state changes and persistence.
The skill states that MEMORY.md is not managed by the skill, but later sections direct the agent to copy or append MEMORY.md content. This contradiction is dangerous because it obscures actual data handling, making reviewers and users believe sensitive memory will be untouched when the skill in fact propagates it.
The skill instructs the agent to copy or append a global MEMORY.md from ~/.openclaw/workspace into the current workspace, explicitly noting it may contain organization structure or credentials. That creates cross-workspace data leakage and persistence beyond the onboarding purpose, potentially exposing sensitive information to unrelated projects, users, or downstream prompts loaded from the new workspace.
The instructions direct copying potentially sensitive global memory into the current workspace without a clear user-facing warning at the point of action. Because the skill itself notes the memory may include company structure or credentials, omitting an explicit consent barrier creates a serious risk of silent disclosure and inappropriate replication of secrets.
Automatically copying and appending a global MEMORY.md into another workspace can replicate sensitive organizational data, credentials, and long-term context into places where it does not belong. This materially increases the blast radius of any secret or sensitive note already present in global memory and can expose it through future context loading, sharing, or repository sync.
The README is entirely written in Chinese and the documented interaction phrases and workflow are presented only in Chinese-centric form, without indicating that users may choose another language. Under the language/locale policy, a skill should not impose a specific language unless the constraint is explicitly documented and justified or the user is offered a choice.
The README describes writing five workspace files and deleting BOOTSTRAP.md as part of the onboarding flow, but it does not present a prominent warning or explicit consent step for these file modifications. In an agent skill context, silent or weakly disclosed filesystem changes are risky because users may trigger the workflow conversationally without realizing it will alter or remove files.
The README expands the skill’s behavior beyond the stated 5-file onboarding scope by documenting an optional cross-workspace backup to ~/knowledge/huo15/profile/<昵称>-<workspace>.md. Even if framed as optional, this introduces extra data persistence and cross-workspace replication of profile information that users and reviewers may not expect from the manifest description, increasing privacy and data-governance risk.
The optional L3 KB backup stores detailed profile data in a home-directory path outside the workspace without an explicit privacy warning. Because the backup includes identity, preferences, roles, and other profile fields, it can unintentionally create long-lived personal data outside the project boundary, increasing exposure and retention risk.
The skill advertises a narrowly scoped onboarding function that creates five workspace files, but the body also instructs copying/appending MEMORY.md and writing an external backup under ~/knowledge. This scope mismatch is security-relevant because it hides additional persistence and data propagation behavior from users and reviewers, reducing informed consent and increasing the chance of unintended disclosure.
The preferences table establishes "中文" as the default primary language before the user has explicitly opted into that locale. Because the skill supports other language options, defaulting to a specific language can violate a language-choice policy unless the user is first given a neutral default such as follow-user-language.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
## 四、收尾:写 5 件套 + 删 BOOTSTRAP.md + (可选)L3
4 步结束后,LLM 按以下顺序操作。**所有 Edit/Write 都针对当前 cwd**(用户的 workspace,不是本 skill 目录)。
### 4.1 渲染 5 个原生文件
The optional L3 backup writes profile data derived from the onboarding flow to ~/knowledge outside the active workspace. This expands the persistence boundary and can leak personal or operational context across devices, users, or future sessions without being necessary for basic bootstrap behavior.
This markdown file presents all user-facing instructions and domain presets exclusively in Chinese, which can amount to forcing a specific language without user opt-in. The policy allows locale constraints only when they are explicitly justified or when users are offered a language/locale choice, neither of which appears here.
This markdown file presents the skill content primarily in Chinese, with only limited English glosses, and does not state that the user can choose their preferred language or locale. That can violate a language/locale policy when a skill implicitly constrains interaction to a specific language without opt-in.
This markdown file is largely written in Chinese and defines multiple presets specifically around Chinese-localized expression styles, but it does not state that language selection is optional or user-controlled. Under the policy rule for language/locale, forcing or defaulting to a specific language without opt-in can be a natural-language policy violation.
The preset hard-codes a demographic-based default timezone for 'Chinese users' without explicit opt-in, which can cause incorrect scheduling, timestamp interpretation, and profile inference based on nationality or language. In an onboarding skill that initializes workspace identity and preference files, silently applying this default increases the chance that downstream automations act on inaccurate personal settings.
The file states that the chosen timezone automatically affects heartbeats, log timestamps, date conversion, meeting suggestions, and information retrieval, but does not warn users that these behaviors will change how data is recorded and interpreted. In a bootstrap skill that creates persistent workspace files, this can lead to silent data integrity issues, misleading audit trails, and user confusion when relative dates or scheduled actions are resolved incorrectly.
The README states that the skill deletes BOOTSTRAP.md after completion, but this destructive file operation is not clearly declared in the manifest description. Undisclosed deletion of workspace files can surprise users, interfere with auditing/recovery, and make the skill’s effective behavior broader than expected.
No suspicious patterns detected.