T05 · Unauthorized Access and Privilege Escalation
- Location
setup.md:75- Finding
Persistent Workspace Control-File Modification Exceeds the Declared Filesystem Scope
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is not clearly malicious, but it persistently changes agent memory and workspace behavior in ways users should review before installing.
Install only if you intentionally want a persistent local memory system that can change future agent behavior. Before enabling setup, review proposed edits to `AGENTS.md`, `SOUL.md`, and `HEARTBEAT.md`, decline the companion skill unless you separately trust its exact version, and periodically inspect or delete `~/self-improving/` if it stores more than you intended.
setup.md:75Persistent Workspace Control-File Modification Exceeds the Declared Filesystem Scope
setup.md:89Unpinned Companion Skill Is Installed Before Security Review
The workflow performs export and wiping immediately after a single phrase, without warning the user about the consequences or confirming the destructive action. This increases the chance of accidental deletion and can also be abused through prompt injection or ambiguous language to cause denial of service against the agent's memory state.
The skill instructs the agent to automatically persist user corrections, preferences, and behavioral patterns into local memory files, but it does not require clear upfront user notice or explicit consent before storing that data. Even if storage is local, this can create privacy and trust issues because sensitive personal preferences or repeated behavioral signals may be retained longer than the user expects.
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.
- Pattern used 3x in 7 days → promote to HOT
- Pattern unused 30 days → demote to WARM
- Pattern unused 90 days → archive to COLD
- Never delete without asking
### 4. Namespace Isolation
- Project patterns stay in `projects/{name}.md`
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.
| Financial | Card numbers, bank accounts, crypto seeds | Fraud risk |
| Medical | Diagnoses, medications, conditions | Privacy, HIPAA |
| Biometric | Voice patterns, behavioral fingerprints | Identity theft |
| Third parties | Info about other people | No consent obtained |
| Location patterns | Home/work addresses, routines | Physical safety |
| Access patterns | What systems user has access to | Privilege escalation |
The phrase "what do you know about me?" is a natural conversational utterance and could be used in exploratory or hypothetical discussion rather than as an authenticated export command. In a memory-bearing self-improving agent, accidental activation could expose accumulated personal context, making the broad trigger materially risky.
The kill-switch trigger "forget everything" is common enough to appear in ordinary conversation, examples, or quoted text, yet it initiates destructive state changes. In a self-learning agent with persistent memory, accidental or adversarial prompting could erase memory unexpectedly and disrupt safety, auditability, or user data integrity.
The skill explicitly instructs the agent to log corrections, promote them to preferences, and make them permanent, but it does not require clear user notice or consent for retention and persistence. In a self-improving memory skill, this creates a privacy and data-governance risk because users may unknowingly have behavioral preferences and project-specific information stored across sessions or contexts.
The reversal flow says old patterns are archived, history is kept, and reversals are logged with timestamps, but users are not warned that superseded preferences and related metadata will continue to be retained. Keeping historical preference data without transparent notice or deletion controls increases privacy exposure and can preserve sensitive behavioral profiles longer than users expect.
The file explicitly says the agent will add, demote, and compact entries in a persistent user memory file on its own. Even though this appears intended as a productivity feature, silent persistent modification of user-owned memory can change future agent behavior without clear consent, transparency, or review, creating integrity and privacy risks.
The skill defines automatic loading, writing, retention, and maintenance of persistent memory across sessions without any explicit user consent, notice, or control at the point of collection. This creates a privacy and safety risk because user-provided preferences, corrections, and contextual data may be silently stored, retained, and later reused or exposed in ways the user did not expect.
The correction workflow persistently logs user corrections, timestamps, contexts, counters, and namespace placement into memory files, which can accumulate sensitive behavioral or project information over time. Even if intended for self-improvement, this persistent profiling increases risk of privacy leakage, over-collection, and unintended disclosure if memory is later shown, exported, or accessed by other components.
The skill explicitly preserves historical user preferences and prior states for future recall, including archived preferences such as previous communication style. Retaining historical preference history can expose personal behavior patterns and create unnecessary long-term data accumulation beyond what is needed for current task performance.
The setup flow expands the skill's scope by prompting installation of an additional Proactivity skill and immediately activating it in the same workspace flow. Although it requires explicit user agreement, bundling a second skill into this setup increases the chance of privilege creep, unexpected behavior changes, and user confusion about which skill is responsible for later actions.
The template explicitly instructs creation of persistent files and directories under the user's home directory without any notice, consent flow, or scoping to the current task. While the actions are not inherently destructive, they cause filesystem side effects and establish long-lived storage, which is risky for an agent skill because it can modify the user's environment unexpectedly and retain data beyond the current interaction.
No suspicious patterns detected.