Nowledge Mem for OpenClaw
Security checks across malware telemetry and agentic risk
Overview
This appears to be a legitimate memory plugin, but it is designed to automatically store and reuse OpenClaw conversations and may use a configured remote server/API key.
Before installing, decide whether you want automatic persistent memory for OpenClaw. Prefer local mode unless you intentionally want a remote/shared memory server, verify any configured apiUrl and apiKey, and review capture/exclusion settings so sensitive conversations are not retained or reused unexpectedly.
VirusTotal
62/62 vendors flagged this plugin as clean.
Risk analysis
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent may search or save memories even when the user did not explicitly ask on that turn.
The plugin adds system-level behavioral guidance on every turn to encourage proactive search and saving. This is consistent with a memory plugin, but it materially changes default agent behavior.
Search proactively with memory_search when past context would improve your answer. Do not wait to be asked... Save autonomously with nowledge_mem_save...
Install only if you want proactive memory behavior, and review plugin settings for capture and recall controls.
Private conversation details may be stored in the memory backend and later resurfaced to the agent.
The plugin is explicitly designed to persist conversation history and reuse it across sessions and tools. That is purpose-aligned, but it means sensitive or incorrect stored content can influence future agent context.
Every OpenClaw conversation is captured as a searchable thread... knowledge from Claude, Cursor, web chats, and imported threads stays searchable inside OpenClaw.
Use local mode unless you intend remote sharing, avoid entering secrets you do not want retained, and configure capture exclusions or deletion workflows where available.
Anyone controlling the configured backend or API key could access or modify the associated memory store.
Remote mode sends a user-configured Nowledge Mem API key to the configured backend. This is expected for remote access, but it is sensitive delegated access.
headers.authorization = `Bearer ${this._apiKey}`; headers["x-nmem-api-key"] = this._apiKey;Verify the apiUrl before enabling remote mode, protect the API key, and rotate it if it may have been exposed.
Memory operations depend on the trusted Nowledge Mem CLI package available in the user environment.
The plugin can use a locally installed nmem command or fall back to uvx running nmem-cli. This is central to its operation, but uvx may resolve an external package at runtime unless the user controls that environment.
const candidates = [["nmem"], ["uvx", "--from", "nmem-cli", "nmem"]];
Install the Nowledge Mem CLI from a trusted source and consider pinning or managing the helper package in controlled environments.