T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:155- Finding
Mandatory Full-Memory Loading Exposes Sensitive Context to Sub-Agents
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a coherent memory system, but it asks agents and sub-agents to persist and broadly reuse potentially sensitive personal and infrastructure context without enough scoping or consent controls.
Install only if you are comfortable maintaining local persistent agent memory. Do not put passwords, tokens, private keys, recovery codes, or sensitive credential paths in these files. Before using it with sub-agents, cron jobs, public posting, shared workspaces, or third-party tools, narrow what each agent can read and write, and keep backups or an append-only audit trail for memory changes.
SKILL.md:155Mandatory Full-Memory Loading Exposes Sensitive Context to Sub-Agents
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
# [Platform Name] Posts
<!-- Track all posts to prevent duplicates and enable engagement follow-up. -->
<!-- Copy this file per platform: memory/4claw-posts.md, memory/moltbook-posts.md, etc. -->
<!-- The [YYYY-MM-DD HH:MM] header and **Posted:** line are REQUIRED for dashboard parsing. -->
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
# [Platform Name] Posts
<!-- Track all posts to prevent duplicates and enable engagement follow-up. -->
<!-- Copy this file per platform: memory/4claw-posts.md, memory/moltbook-posts.md, etc. -->
<!-- The [YYYY-MM-DD HH:MM] header and **Posted:** line are REQUIRED for dashboard parsing. -->
## [YYYY-MM-DD HH:MM] Example Post Title
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
<!-- Track all posts to prevent duplicates and enable engagement follow-up. -->
<!-- Copy this file per platform: memory/4claw-posts.md, memory/moltbook-posts.md, etc. -->
<!-- The [YYYY-MM-DD HH:MM] header and **Posted:** line are REQUIRED for dashboard parsing. -->
## [YYYY-MM-DD HH:MM] Example Post Title
- **Posted:** YYYY-MM-DD HH:MM AM/PM EST
The skill is framed as a universal memory architecture for AI agents and lacks explicit activation boundaries, approval requirements, or environment constraints. That broad scope increases the chance an agent will apply persistent memory behaviors in contexts where storage, retrieval, or cross-session continuity was not intended, leading to privacy and governance issues.
The skill instructs agents to create, update, and clear persistent memory files, including inbox processing that deletes processed entries, without requiring user-visible notice or confirmation. This can cause silent retention, modification, or destruction of potentially sensitive user data and makes auditability harder if information is overwritten or cleared automatically.
The sub-agent template directs every spawned sub-agent to read MEMORY.md and recent daily logs, which the skill itself says may contain operator preferences, infrastructure details, and personal context. Without strict scoping, minimization, and explicit warnings, this creates unnecessary propagation of sensitive data across isolated sessions and increases the risk of privacy leakage or overexposure to tools and contexts that do not need it.
The template explicitly prompts the agent/operator to record 'credentials locations' in long-term memory, but provides no warning, minimization guidance, or restrictions on handling secrets. In a memory system designed for persistence across sessions, this increases the chance that sensitive authentication material or directions to retrieve it will be stored in broadly accessible context, leaked to sub-agents, exposed in logs, or surfaced to unintended users.
The markdown template specifies the posting timestamp as 'AM/PM EST', which imposes a specific locale/timezone format in natural language. This can violate language/locale policy expectations because the file does not provide an opt-in, alternative timezone handling, or justification for why EST is required.
No suspicious patterns detected.