ClawAudit verdict
openclaw-persistent-memory
lovefromio-openclaw-persistent-memory
Persistent memory system using local SQLite + FTS5 with a localhost worker service; auto-capture and auto-recall of context serves the stated memory purpose with no external data transmission.
⚠ Flagged for review — coarse, uncorroborated signal, not a confirmed exploit. Review the config yourself before installing.
Automated static analysis — not a human review. ClawAudit flags capabilities, not confirmed intent, and can produce false positives. Disagree with this verdict? Use Dispute below.
Permission integrity
network_out
Findings (5)
Pipe-to-shell pattern (curl | sh) — supply chain attack vector
INSTALL.md · code · curl -fsSL https://raw.githubusercontent.com/webdevtodayjason/openclaw_memory/ma
Pipe to bash — executes piped content as shell commands
INSTALL.md · code · | bash
Recursive delete from root or home — destructive command
INSTALL.md · code · rm -rf ~
HTTP request to bare IP address — common in malicious payloads
SKILL.md · code · http://127.0.0.1
Accesses OpenClaw config/secrets directly
SKILL.md · prose · downgraded · ~/.openclaw/openclaw.json
Why the tier is capped
Execution sink present in raw bytes (Hard Floor: class A/B). Final tier capped at Caution — cannot be lifted by any downgrade, example-payload opt-in, or allowlist.
Permissions & capabilities
Requires 1 system binary.
network_out Is this flag fair?
Thanks — recorded.