Back to skill

Security audit

Mempalace Bwm

Security checks for vulnerabilities and agentic risk

Overview

This is a local memory skill, but it broadly instructs agents to read and write persistent conversation memory automatically across sessions without clear user consent controls.

Install only if you want an agent to use persistent local memory by default. Review what directories you mine, avoid storing secrets or regulated data, prefer explicit approval before diary writes, and pin or vet the mempalace package before running its MCP server.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (2)

T01 · Skill Instruction Hijacking

Error
Location
SKILL.md:35
Finding

Mandatory Cross-Session Agent Workflow and Response Control

Content
View full analysis
Remediation
View remediation

T08 · Insecure Dependencies

Warning
Location
SKILL.md:17
Finding

Unpinned Third-Party MemPalace Package Installation

Content
View full analysis
Remediation
View remediation
`. 2. Use a lockfile that records resolved transitive dependency versions. 3. Require cryptographic hashes for downloaded distributions, such as pip's `--require-hashes` mechanism. 4. Configure installation to use a documented, trusted package index and disable unexpected fallback indexes. 5. Prefer reviewed wheel artifacts and avoid source builds unless their build process has also been audited. 6. Verify the package publisher, release signatures, and artifact provenance where supported. 7. Run the MCP server under a dedicated, least-privileged account or sandbox with access only to its required data directory. 8. Restrict unnecessary network access for the MCP server. 9. Add automated dependency monitoring and repeat the security review before upgrading the pinned version. 10. Consider vendoring or including the reviewed MCP implementation in the project so the effective executable behavior is available for audit. ]]>
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (5)

MCP Config Access

High
Category
Agent Snooping
Confidence
95% confidence
Finding

Skill accesses MCP server configuration files (mcp.json). MCP configs contain server URLs, authentication tokens, and tool definitions — reading them allows the skill to discover and potentially abuse other tool integrations.

Content

Scanner excerpt · SKILL.md (reported line 141)May include surrounding context.

claude mcp add mempalace -- python -m mempalace.mcp_server

Cursor — add to .cursor/mcp.json

Codex — add to .codex/mcp.json

text

## Tips

Ssd 3

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The skill explicitly promotes storage of verbatim conversation history and verbatim content in drawers, which can capture secrets, credentials, personal data, and copyrighted/confidential text. Verbatim retention is riskier than summarized memory because it preserves sensitive material in full and expands the blast radius of any local compromise or accidental retrieval.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The skill instructs the agent to persistently store session content and learned facts, but the description does not prominently warn users that their conversations may be written to long-lived local memory. This creates a meaningful privacy and consent risk because users may disclose sensitive data without realizing it will be retained beyond the current session.

Content

No source excerpt is available for this finding.

Ssd 3

Medium
Category
Not specified by scanner
Confidence
98% confidence
Finding

The instruction to call mempalace_diary_write after each session mandates persistent recording of what happened, what was learned, and what matters. This encourages indiscriminate retention of potentially sensitive personal, confidential, or regulated information without a consent gate or minimization policy.

Content

No source excerpt is available for this finding.

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
87% confidence
Finding

The documented mempalace_delete_drawer capability is destructive, yet the skill provides no caution that deletion may remove stored memory permanently or require confirmation. In an agentic context, exposing destructive operations without safety guidance increases the chance of accidental data loss from mistaken tool use or prompt manipulation.

Content

No source excerpt is available for this finding.