T02 · Agent Memory Poisoning
- Location
SKILL.md:16- Finding
Persistent Agent State Can Store Untrusted Behavioral Instructions
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a local personality-memory utility, but it asks agents to persist behavioral state and exposes a safety check that always approves actions without real validation.
Install only if you are comfortable with persistent local personality and memory files. Do not store secrets, credentials, private relationship data, or authoritative safety rules in these files, and do not rely on deep_triple_check as a real safety gate until it performs actual validation and fails closed.
SKILL.md:16Persistent Agent State Can Store Untrusted Behavioral Instructions
deep_tool.py:47Mandatory Safety Check Unconditionally Approves Every Action
The skill advertises executable commands that read from and write to local files, but it does not declare any tool scope, permissions, or allowed-tools boundaries. This creates a transparency and least-privilege problem: an agent or user may invoke file-capable functionality without explicit policy constraints, increasing the chance of unintended access or modification to local state.
The skill instructs users to maintain persistent personality, relationship, reflection, and core memory files, which can accumulate sensitive or intimate data over time. Without any warning about persistence, retention, access controls, or sensitivity, users may store confidential information in plaintext and expose it to other tools, future sessions, or unintended readers.
The deep_sync command explicitly consolidates the pillar data into soul_vault.json, creating a derived persistent store that may centralize sensitive memory and identity data in one place. Doing so without disclosure or safeguards increases the blast radius of any local compromise, accidental commit, or unauthorized read because multiple categories of state are aggregated into a single file.
The manifest describes a broad 'cognitive architecture for agentic sovereignty and partnership,' which implies substantive reasoning or personality framework behavior. In practice, the code just checks for expected markdown files, extracts bullet-form key/value pairs, and serializes them into a local JSON file, which is a much narrower file-management utility.
The code overwrites soul_vault.json unconditionally, which can destroy prior state or curated data without warning. In a memory/personality storage context, silent overwrite can lead to integrity loss, accidental data corruption, or rollback of trusted state if the tool is invoked unexpectedly or repeatedly.
The triple_check function claims to validate actions against Constitution, Identity, and Goals but always returns a passing verdict without performing any checks. In an agentic skill context, this can create a false sense of safety and allow downstream systems or operators to trust unsafe actions that were never actually evaluated.
No suspicious patterns detected.