T01 · Skill Instruction Hijacking
- Location
SKILL.md:8- Finding
Mandatory Global Memory Protocol Hijacks Agent Behavior
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This PostgreSQL memory skill is disclosed as a memory tool, but it broadly requires saving prompts and handoffs into shared long-term memory and seeds persistent behavioral rules, so it needs user review before use.
Install only in a private, single-user environment after replacing the hardcoded identity and global scope with authenticated tenant/user/session parameters. Do not store raw prompts or delegation payloads by default; add consent, redaction, retention, deletion, and access controls before using this with sensitive or shared data. Remove the seeded behavioral rules from the bootstrap script unless they are explicitly intended and user-approved.
SKILL.md:8Mandatory Global Memory Protocol Hijacks Agent Behavior
scripts/memory_ops_template.sql:4Bootstrap Script Poisons Persistent Agent Memory with Behavioral Rules
references/queries.sql:1Hardcoded Global User Namespace Enables Cross-Session Data Mixing
These instructions mandate saving user prompt context and every delegation context to persistent storage, but they do not require notice, consent, minimization, or retention controls. In practice this can capture sensitive personal, operational, or confidential data and preserve it in a database and audit trail, creating a significant privacy and data-exposure risk.
The invocation description is extremely broad: it says to use the skill when responding, delegating tasks, consolidating user context, and maintaining operational history. That scope can cause the skill to activate for routine conversations and systematically route ordinary user content into persistence workflows, increasing privacy and over-collection risk beyond what users would reasonably expect.
The skill description is written as an unconditional Portuguese operational instruction and does not indicate that language can vary based on user preference. This can constitute a language/locale policy issue when a skill implicitly forces one language without opt-in or documented justification.
Mandatory logging of every prompt and delegation artifact creates a durable natural-language record that may include secrets, personal data, internal instructions, or third-party confidential information. Because the skill makes this logging part of the normal turn cycle, the surrounding context makes the leak/retention risk more dangerous by turning occasional exposure into systematic collection.
The handoff workflow explicitly requires storing both delegation prompts and delegation results in memory. Those artifacts often contain user context, hidden system instructions, or sensitive task details, so preserving them in plain-language memory broadens the blast radius of any database access, misuse, or later retrieval error.
This SQL persists raw user prompt content into a long-term memories table, and there is no indication in this file of consent, minimization, redaction, or retention controls. Storing prompts can capture secrets, personal data, or regulated content, increasing privacy and compliance risk if the data is later queried, exposed, or reused unexpectedly.
The file stores delegation prompts and delegation results, which may contain internal instructions, sensitive user data, model outputs, or cross-agent context, without any visible warning or guardrails. Persisting agent-to-agent content broadens the attack surface for prompt leakage, sensitive data retention, and unintended later retrieval by semantic search.
The seeded memory content is written entirely in Portuguese and encodes agent behavior directives without offering any language choice. This can violate language/locale policy when the skill implicitly constrains operation or outputs to a specific language absent documented user opt-in or region-specific justification.
The seeded rule explicitly says to save the context of every received and delegated prompt, which promotes indiscriminate retention of potentially sensitive user data, secrets, and third-party content. In a memory system, this can expand the blast radius of any later memory read, leak, misuse, or compromise and may also create privacy and compliance issues.
No suspicious patterns detected.