T05 · Unauthorized Access and Privilege Escalation
- Location
scripts/request-readonly-auth.sh:4- Finding
Overbroad Persistent Lark Authorization and Automated Private-Context Collection
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill has a coherent Lark-to-notes purpose, but it asks for broad ongoing access to private workplace context and can automatically persist summaries into local memory notes.
Review before installing. Only use this if you are comfortable granting broad read-only Lark access, including messages, documents, meetings, wiki, calendar, and offline refresh access, and with recurring jobs copying selected work context into local OpenClaw memory notes. Prefer limiting enabled sources, avoiding unattended heartbeat use unless needed, pinning the CLI version, and revoking Lark authorization if you stop using the skill.
scripts/request-readonly-auth.sh:4Overbroad Persistent Lark Authorization and Automated Private-Context Collection
SKILL.md:4Unpinned Globally Installed Lark CLI Dependency
The documented behavior focuses on scanning many Lark resources and validating tool readiness, but it does not define corresponding, constrained note-writing behavior in a way that can be audited against the declared purpose. In practice, this encourages broad data harvesting under the banner of 'context sync,' increasing privacy and scope-creep risk.
The documented behavior focuses on scanning many Lark resources and validating tool readiness, but it does not define corresponding, constrained note-writing behavior in a way that can be audited against the declared purpose. In practice, this encourages broad data harvesting under the banner of 'context sync,' increasing privacy and scope-creep risk.
The skill instructs the agent to read local daily-note files (memory/YYYY-MM-DD.md, HEARTBEAT.md) and to use an external CLI, but it does not declare an explicit tool/permission boundary. That creates implicit file-read capability and weakens reviewability, making accidental overreach or unauthorized data access more likely in a memory-sync workflow handling potentially sensitive context.
The activation language is broad enough to match ordinary conversation, such as asking what the user has been doing recently. That can cause the agent to invoke external data reads and local note updates without a clear, specific request, leading to unintended access, retention, or summarization of sensitive work context.
Phrases like 'any normal turn that read relevant Lark artifacts' and 'update, refresh, or accumulate recent context' are ambiguous and operationally expansive. In a skill that accesses work communications and writes memory notes, such ambiguity materially increases the risk of unintentional triggering and silent persistence of sensitive information.
The manifest advertises syncing recent Lark activity into OpenClaw daily notes but does not warn that the skill will import external context and modify persistent notes. This is risky because users may not realize that potentially sensitive workplace communications or summaries are being copied into another system, increasing the chance of unintended disclosure, over-collection, or persistence of private information.
The skill enables implicit invocation with only broad natural-language triggers in the metadata, which can cause the agent to run automatically in contexts the user did not explicitly intend. Because the skill imports external Lark context and writes into daily notes, unintended activation can silently copy sensitive work activity into notes or alter user data without clear consent.
The manifest describes syncing recent Lark context into daily notes, which aligns with appending relevant context. However, the heartbeat file also instructs broad retrospective maintenance actions like reviewing prior snapshots, merging duplicates, and pruning stale patterns, which goes beyond simple syncing recent Lark context and changes the behavior into ongoing note curation.
This is a manifest-like file, so trigger quality applies. The file defines recurring tasks with generic names and free-form prompts, but does not document narrower activation constraints or exclusion conditions beyond time intervals, which can make task intent and invocation boundaries less explicit.
The prompts require the agent to reply with the fixed English token "HEARTBEAT_OK" when nothing changes. This imposes a specific language/output convention without offering user opt-in or documenting a justified locale constraint.