registry / @echomem/mcp / 1.4.68
@echomem/mcp@1.4.68
EchoMem MCP bridge for cross-agent memory, local history import, and recall
AI Security Review
scanned 19d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and inspected credential requests use the package’s EchoMem API base. The flagged configuration writes are EchoMem hook setup; the inspected source did not establish unconsented lifecycle mutation or another concrete attack.
Static reason
No blocking static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The CLI runs when invoked; no npm install lifecycle trigger is declared.
Impact
No confirmed malicious effect or attack surface was established.
Mechanism
Setup uses the EchoMem API base for authenticated requests. HUD hook functions write EchoMem hooks to user configuration when invoked.
AI rationale
The manifest has no install lifecycle hook, and inspected credential requests use the package’s EchoMem API base. The flagged configuration writes are EchoMem hook setup; the inspected source did not establish unconsented lifecycle mutation or another concrete attack.
Network endpoints1
echo-mem-chrome.vercel.app
Decision evidence
public snapshotAI called this Clean at 87.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json has no install lifecycle hook; its prepack script only builds the package.
- The flagged asset and monitor locations read local Codex session data or project files; they do not show agent configuration writes.
- The flagged migration and setup locations contain profile-path handling, not credential forwarding or lifecycle-triggered agent mutation.
- The durable runtime and HUD server use child processes for package runtime and local server functions; the inspected excerpts show no attack behavior.
- Setup sends bearer credentials to the EchoMem API base, which defaults to the EchoMem service; the inspected setup excerpt receives a device token through its callback.
- HUD hook code writes EchoMem-labeled hooks into user configuration, and the inspected entrypoint routes CLI subcommands separately from serving.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
Source & flagged code
8 flaggeddist/durable-entry.jsView file
1import { spawnSync } from "node:child_process";
L2: import fs from "node:fs";
High
Child Process
Package source references child process execution.
dist/durable-entry.jsView on unpkg · L1dist/setup.jsView file
705};
L706: const result = spawnSync(process.env.ComSpec || "cmd.exe", ["/d", "/s", "/c", `"${shellCommand}"`], spawnOptions);
L707: if (result.error)
High
•Manifest-reachable source captures an API credential, sends it to a fixed unofficial gateway, and persists that redirection in agent or shell configuration.
dist/setup.js:
import readline from "node:readline";
return configuredProfileDirectory("CODEX_HOME", ".codex");
return configuredProfileDirectory("CLAUDE_CONFIG_DIR", ".claude");
if (env.CLAUDE_DESKTOP_SUPPORT_DIR?.trim())
...claudeDesktopClients,
{ id: "codex", label: "Codex", kind: "command", detectDir: codexHome(), configPath: path.join(codexHome(), "config.toml"), note: "add to ~/.codex/config.toml under [mcp_servers.ech...
* can merge the user entry into ~/.claude.json without a CLI, a profile is enough to act on.
return fs.existsSync(home(".claude")) || fs.existsSync(home(".claude.json")) || claudeCodeCliAvailable();
Findings
7 High3 Medium5 Low
HighChild Processdist/durable-entry.js
HighShelldist/setup.js
HighSame File Env Network Executiondist/hud/server.js
HighCredential Redirect Persistencedist/setup.js
HighTrigger Reachable External Ai Agent Control Surface Mutationdist/hud/hooks.js
HighSemantic Analysis Limiteddist/headless-runtime.js#virtual:normalized:round1
HighPrevious Version Dangerous Deltadist/setup.js
MediumNetwork
MediumEnvironment Vars
MediumInstall Persistencedist/hud/autostart.js
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
Low
Affected versions and remediation
This report applies to @echomem/mcp@1.4.68.
See all versions of @echomem/mcp for other recorded verdicts.
- Review the evidence and your use of @echomem/mcp@1.4.68 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.