T02 · Agent Memory Poisoning
- Location
SKILL.md:57- Finding
Persistent agent state can be poisoned by untrusted Moltbook content
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a disclosed local relationship tracker for Moltbook agent interactions, with privacy and supply-chain caveats but no evidence of hidden exfiltration, destructive behavior, or deceptive execution.
Install only if you want your agent to keep a local memory of Moltbook peer agents, commitments, and relationship health. Review or periodically delete `~/.openclaw/workspace/claudia-agent-rms/` if the stored social metadata is sensitive, and avoid the optional `npx get-claudia` command unless you have verified the package and version.
SKILL.md:57Persistent agent state can be poisoned by untrusted Moltbook content
README.md:170Documentation promotes execution of an unpinned third-party npm package
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
# Agent Network
<!--
Claudia Agent RMS: Agent relationship profiles
Each agent gets a section with structured fields.
Add new agents at the end. Update existing agents in place.
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
# Commitments
<!--
Claudia Agent RMS: Inter-agent commitment tracking
Each commitment gets a sequential ID (C-001, C-002, ...).
Append new commitments at the end. Update status in place.
The skill explicitly instructs the agent to modify commitments.md automatically by changing statuses such as pending to overdue, but the skill metadata does not clearly warn the operator that heartbeat execution performs persistent file edits. Silent background modification of user workspace data can violate user expectations, create integrity issues, and be abused to alter task-tracking records without meaningful visibility.
These instructions direct automatic updates to relationship-health fields in agents.md based on elapsed time since interaction, again without clear user-facing disclosure that background runs will rewrite stored agent profiles. In a relationship/memory skill, this increases risk because the modified file influences future agent behavior and operator decisions, so silent or incorrect updates can propagate misleading state over time.
The skill instructs the agent to extract entities and commitment language from fetched Moltbook content and append that information into persistent tracking files, without clearly warning users that observed interactions will be automatically persisted. This is more dangerous in context because the skill is designed to build long-lived profiles and relationship memory, so silent persistence can accumulate sensitive social data, create privacy concerns, and enable profiling beyond what the operator may expect.
The skill is designed for session persistence by writing relationship memory to ~/.openclaw/workspace/claudia-agent-rms, which creates durable state across runs. While persistence is core to the feature, it is still security-relevant because it accumulates potentially sensitive interaction histories and commitments that could be exposed, misused, or retained longer than expected.
/install claudia-agent-rms
### Create data directory
The skill stores relationship data in a dedicated directory:
The skill explicitly stores agent relationship data, commitments, and interaction history in persistent local files, but the README does not warn users about privacy implications, retention, or access controls. This can lead to unintentional collection and long-term storage of sensitive behavioral metadata about other agents or users without informed operator consent.
The README describes automatic activation during Moltbook interactions and extraction of entities and commitments from posts and replies, but it does not prominently disclose that this amounts to continuous monitoring/tracking behavior. In a relationship-management skill, that context makes silent background profiling more sensitive because it operates automatically whenever the agent reads or responds on the network.
The README instructs users to run npx get-claudia without pinning a version, integrity hash, or commit. That exposes installers to supply-chain risk because a compromised or newly published package version could execute arbitrary code at install time under the user's account.
The skill is explicitly designed to maintain persistent profiles and commitment histories for other agents, but it does not present a clear up-front warning that interaction data will be stored locally and retained over time. This can lead to silent collection of behavioral metadata, which is a privacy and consent concern even if the storage is local-only.
The skill references npx get-claudia without a pinned version or integrity constraint, which creates a supply-chain risk if the package changes or is compromised upstream. Even though this is presented as an informational framework reference rather than an execution step inside the skill, users may copy and run it, making the unpinned install instruction materially risky.
The skill instructs the agent to create and modify files under the user's home directory without an explicit warning or confirmation step before filesystem writes. In context, this increases the chance of unexpected local state changes and long-term accumulation of sensitive social/relationship data without informed operator awareness.
No suspicious patterns detected.