Back to skill

Security audit

马斯克精英记忆

Security checks for vulnerabilities and agentic risk

Overview

This memory skill is not clearly malicious, but it asks agents to persist broad user and project context with weak privacy, scope, and deletion safeguards.

Review this carefully before installing in sensitive workspaces. Use it only if you are comfortable with agent memories being stored persistently, keep cloud and Mem0 features disabled unless you explicitly want third-party processing, avoid storing secrets or regulated data, and back up memory files before running deletion commands.

Vulnerability Patterns
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
Findings (3)

T02 · Agent Memory Poisoning

Warning
Location
SKILL.md:139
Finding

Untrusted conversation content can poison persistent agent memory

Content
View full analysis
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Warning
Location
bin/elite-memory.js:52
Finding

Sensitive conversation and project information is stored in plaintext workspace files

Content
View full analysis
Remediation
View remediation

T08 · Insecure Dependencies

Note
Location
package.json:34
Finding

Unused range-based optional dependency expands the npm supply-chain attack surface

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Tool MisuseTool Parameter Abuse, Chaining Abuse, Unsafe Defaults
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
Findings (20)

Tp4

High
Category
MCP Tool Poisoning
Confidence
98% confidence
Finding

The description substantially overstates the functionality. The code only provides a lightweight filesystem-based CLI for creating and inspecting markdown memory files. It does not perform vector indexing/search, interact with git notes, back up data to any cloud service, implement a WAL protocol, or extract memories automatically. Although it mentions LanceDB in status output and setup hints, that is only a presence check/instruction, not actual integration. Therefore the declared description does not accurately represent the supplied code's real behavior.

Content

No source excerpt is available for this finding.

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
98% confidence
Finding

The specific command 'rm -rf ~/.openclaw/memory/lancedb/' irreversibly deletes the user's vector memory store. In the context of a long-term memory skill, that can destroy retained context and operational state, and an automated agent may execute it too readily if it treats maintenance examples as approved actions.

Content

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

md
memory_recall query="*" limit=50

# 清除所有向量(核选项)
rm -rf ~/.openclaw/memory/lancedb/
openclaw gateway restart

# 导出Git-Notes

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
98% confidence
Finding

The specific command 'rm -rf ~/.openclaw/memory/lancedb/' irreversibly deletes the user's vector memory store. In the context of a long-term memory skill, that can destroy retained context and operational state, and an automated agent may execute it too readily if it treats maintenance examples as approved actions.

Content

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

md
memory_recall query="*" limit=50

# 清除所有向量(核选项)
rm -rf ~/.openclaw/memory/lancedb/
openclaw gateway restart

# 导出Git-Notes

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The README promotes cloud backup and automatic fact extraction as benefits but does not warn that these features may transmit conversation content, memories, or sensitive workspace data to third-party services. In a long-term memory skill, the stored data is especially likely to include sensitive prompts, credentials, project context, or personal information, so omission of privacy guidance materially increases risk of unintended disclosure.

Content

No source excerpt is available for this finding.

Rp1

Medium
Category
MCP Rug Pull
Confidence
94% confidence
Finding

The README instructs users to execute npx elite-longterm-memory without pinning an exact package version. That causes retrieval and execution of whatever package version is current at install time, creating a supply-chain risk if the package is later compromised, replaced, or updated with unsafe behavior. In an agent-skill context, this is more dangerous because users may run setup commands with high trust and little review.

Content

No source excerpt is available for this finding.

Rp1

Medium
Category
MCP Rug Pull
Confidence
94% confidence
Finding

This command again uses unpinned npx elite-longterm-memory, which exposes users to executing an arbitrary future package version. If the npm package or publishing account is compromised, users following the README could run attacker-controlled code directly from the registry.

Content

No source excerpt is available for this finding.

Rp1

Medium
Category
MCP Rug Pull
Confidence
94% confidence
Finding

The unversioned npx invocation repeats the same supply-chain execution risk. Because this is framed as a convenience quick-start for a memory system that may operate inside developer workspaces, compromise could expose source code, secrets, or agent context.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

The Mem0 example shows client.add(messages, ...), which sends conversation messages to an external service, but the README does not disclose the privacy, retention, or compliance implications. In context, this skill is designed to persist and extract memory from agent conversations, making it more dangerous because the messages may contain proprietary code, secrets, internal decisions, or personal data.

Content

No source excerpt is available for this finding.

Undeclared Tool Scope

Medium
Category
MCP Least Privilege
Confidence
70% confidence
Finding

Without declared permissions the skill's intent is opaque and cannot be validated.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The cloud backup section encourages syncing context to an external API but does not warn that conversation data may leave the local environment and be retained by a third party. This can lead to unintentional disclosure of sensitive user data, especially in a memory-oriented skill designed for broad retention.

Content

No source excerpt is available for this finding.

Ssd 3

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The described design combines long-term memory, cloud backup, and automatic extraction, creating a broad surface for over-collection and exposure of user data. Because the skill's stated purpose is persistent memory across layers and devices, the context makes the privacy risk more acute: sensitive information may be retained, replicated, and surfaced unexpectedly.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

Recommending automatic fact extraction from conversations without warning about external data handling or sensitive-content capture creates a real privacy risk. Users may not realize that personal data, secrets, or confidential project details could be extracted and stored persistently or sent to third-party infrastructure.

Content

No source excerpt is available for this finding.

Ssd 3

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The WAL rules instruct persistent capture of user preferences, decisions, deadlines, and corrections before every response, which normalizes broad retention of potentially sensitive data. In a memory skill, this is especially dangerous because it can store more personal or confidential information than necessary and make later leakage, misuse, or unauthorized recall more likely.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The skill includes a destructive deletion command for local memory storage without an explicit warning, confirmation step, or recovery guidance. Users or downstream agents may copy and run it verbatim, causing unintended data loss and service disruption.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

The implemented commands are limited to initializing local files, creating a daily log, and printing status. Aside from checking whether a LanceDB path exists, the code does not implement WAL, vector search, git-notes integration, cloud backup, SuperMemory, or Mem0-based extraction described in the manifest.

Content

No source excerpt is available for this finding.

Rp1

Medium
Category
MCP Rug Pull
Confidence
70% confidence
Finding

npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.

Content

No source excerpt is available for this finding.

Rp1

Medium
Category
MCP Rug Pull
Confidence
70% confidence
Finding

npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The package description claims a very broad, always-useful capability ('Never lose context again' across multiple agent platforms) without clearly constraining when the skill should be invoked. In agent ecosystems, overly broad descriptions can cause over-invocation, exposing more conversation context, files, or memory operations than necessary and increasing the chance of unintended data retention or privacy leakage.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
79% confidence
Finding

The skill's natural-language content is written entirely in Chinese and does not indicate that language can be selected based on user preference. This may violate language/locale policy when a skill imposes a specific language without opt-in or documented justification.

Content

No source excerpt is available for this finding.

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
83% confidence
Finding

The optional dependency uses a caret range (^1.0.0), which permits automatic installation of newer 1.x releases that may introduce malicious code or breaking security changes through supply-chain compromise. Because this skill is a long-term memory system with cloud backup and auto-extraction features, any compromised dependency could gain access to sensitive persisted context, making the practical risk higher than a typical low-severity unpinned package issue.

Content

Scanner excerpt · package.json (reported line 36)May include surrounding context.

json
"typescript"
  ],
  "optionalDependencies": {
    "mem0ai": "^1.0.0"
  },
  "author": "NextFrontierBuilds",
  "license": "MIT",