T02 · Agent Memory Poisoning
- Location
main.py:47- Finding
Persistent Agent Memory Poisoning Through Untrusted Interaction Data
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is Review-worthy because it creates persistent local memory from broad user and physical-environment interactions without clear consent, filtering, or deletion controls.
Install only if you want a local agent-memory system that can retain interaction history and physical-context information. Keep its storage directory private, avoid recording secrets or precise personal data, and require explicit review before any memory is consolidated or reused by another agent.
main.py:47Persistent Agent Memory Poisoning Through Untrusted Interaction Data
main.py:29Sensitive Interaction and Physical Anchor Data Stored in Plaintext
The document explicitly describes a background utility that 'silently intercepts' raw interaction logs and multi-modal sensory inputs, which indicates covert collection of potentially sensitive user and environmental data. In the context of an agent skill/architecture specification, this normalizes undisclosed surveillance and creates substantial privacy, consent, and compliance risk if implemented.
The skill accepts arbitrary details content and persists it first in hippocampus_logs.json and then into long-term markdown files without any filtering, minimization, or consent controls. If user interactions contain secrets, personal data, tokens, or other sensitive content, the system will retain and duplicate that data on disk, increasing exposure and making later unintended disclosure more likely.
The manifest sets a fixed language/locale value of "en-US". Under the policy, locale constraints should either be user-selectable or clearly documented as necessary for a region-specific skill, which is not indicated here.
This markdown file describes a "User Command Orchestration" source and a user request to activate "Taohuayuan Spring Mode," but it does not define any specific trigger phrases, scope limits, or exclusion conditions. The lack of explicit activation boundaries could allow the skill to be interpreted as activating on broad natural-language requests related to environment control.
The file states that the skill responds to user orchestration for smart-home IoT and adjusts HVAC settings in the physical world. Because this behavior can affect the user's environment and system state, the markdown should explicitly warn that the skill may change connected device settings and describe any safeguards or confirmation expectations.
The skill explicitly instructs logging of user interactions but does not warn users that their interactions may be stored in short-term and later consolidated into long-term memory. This creates a transparency and consent gap that can expose sensitive personal or behavioral data to retention beyond user expectations.
The instructions to 'log all daily physical reality contacts and user interactions' and then autonomously consolidate them into permanent memory create a direct data retention risk. In practice, this can capture sensitive or unnecessary user information and transform ephemeral conversations into persistent records, expanding privacy, leakage, and misuse exposure.
The skill defines autonomous triggers like entering an idle state or detecting nighttime physical parameters without clear authorization boundaries, rate limits, or user consent checks. Broad trigger language can cause unsolicited background execution and memory consolidation, increasing the chance of unintended data processing and persistence.
The text instructs that interaction logs and sensory inputs be silently captured into a cache, which is a stealthy data collection pattern. Even though this is framed as memory architecture, the operational effect is surveillance-oriented accumulation of user and environmental data without transparency, which is unsafe for any deployable agent system.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
Borrowing from the evolutionary mechanics of human REM (Rapid Eye Movement) sleep and aligning with the "Ecological Hibernation Principle," taohuayuan.md V2.0 introduces the Cyber-Zen Protocol. When an agent enters an idle state or detects specific environmental thresholds (e.g., nighttime low-wattage states), it autonomously executes an offline memory consolidation routine.
[Hippocampus Cache] ──► [Cyber-Zen Core] ──► Delta-Sync & Deduplication
The whitepaper describes autonomous offline consolidation of short-term interactions into long-term storage without any accompanying notice, consent, or retention controls. Persisting user interactions by default increases the risk of over-collection, unexpected profiling, and long-term exposure of sensitive information if the device or storage is later accessed or compromised.
The consolidation pipeline stores intercepted interactions as a permanent 'soul' or long-term memory record, implying indefinite retention of user behavior, environment, and potentially sensitive contextual data. This amplifies harm from any unauthorized access, misuse, or future repurposing of the data because transient inputs are transformed into durable, indexed records.
No suspicious patterns detected.