T08 · Insecure Dependencies
- Location
SKILL.md:9- Finding
Unpinned Third-Party Plugin Installation
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a coherent persistent-memory tool, but it should be reviewed carefully because it automatically stores and reinjects memories across sessions and tools with limited scoping or approval controls.
Install only if you deliberately want a shared, persistent memory layer for your agents. Review the @plur-ai/claw package source and version before installation, avoid storing secrets or sensitive operational details as memories, and make sure you understand how to inspect, delete, disable sync, and limit shared ~/.plur/ memories.
SKILL.md:9Unpinned Third-Party Plugin Installation
SKILL.md:20Uncontrolled Persistent Memory Propagation Across Sessions and Tools
The skill instructs the agent to automatically learn from user corrections and inject relevant engrams every session, which creates a memory-poisoning pathway: malicious or mistaken inputs can be persisted and later reintroduced as trusted context. In a cross-session, cross-tool memory system, poisoned memories can influence future decisions well beyond the original conversation, increasing the blast radius of bad data or adversarial instruction shaping.
## Memory Lifecycle
- **Automatic injection** runs every session start - relevant engrams appear in your context
- When you discover something worth remembering - call `plur_learn` with a clear statement
- When corrected by the user - call `plur_learn` immediately with the correction
- When an injected engram was helpful - call `plur_feedback` with signal "positive"
- When an injected engram was wrong or stale - call `plur_feedback` with signal "negative"
The skill explicitly describes storing corrections, preferences, and patterns as local YAML 'engrams' and later states that this memory is shared across tools and can sync across devices, but it does not present a prominent warning about the persistence and propagation of user-derived data. This creates a real privacy and data-governance risk because users or downstream agents may cause sensitive preferences, corrections, or operational details to be retained and redistributed without informed consent.