registry / @echomem/mcp / 1.4.39
@echomem/mcp@1.4.39
EchoMem MCP bridge: cloud-first memory tools and the Agent Doctor workspace forensics report (cost ledger + 3D repo city)
AI Security Review
scanned 3mo ago · by lpm-firewall-aiNo concrete malware, unconsented install hook, credential theft, or covert exfiltration was found. Warn because explicit setup mutates broad AI-agent control surfaces and the server can auto-install future code.
Static reason
No blocking static signals were detected.
Trigger
User runs echomem-mcp init/setup/update or enables related hooks; an MCP server session triggers its update check.
Impact
Can influence configured agent behavior and execute a later npm-fetched package version in future sessions.
Mechanism
first-party agent integration plus self-updating runtime
AI rationale
No concrete malware, unconsented install hook, credential theft, or covert exfiltration was found. Warn because explicit setup mutates broad AI-agent control surfaces and the server can auto-install future code.
Evidence
package.jsondist/setup.jsdist/hud/hooks.jsdist/headless-runtime.jsdist/index.jsdist/update-check.js~/.codex/config.toml~/.codex/AGENTS.md~/.codex/hooks.json~/.claude/CLAUDE.md~/.claude/settings.json~/.echomem/mcp-runtime/launcher.mjs
Network endpoints2
echo-mem-chrome.vercel.appregistry.npmjs.org/%40echomem%2Fmcp/latest
Decision evidence
public snapshotAI called this Suspicious at 90.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- dist/setup.js: init/setup writes MCP entries and global agent guidance.
- dist/hud/hooks.js: explicit setup can register Codex/Claude command hooks.
- dist/headless-runtime.js: background update installs and imports newer package runtime.
Evidence against
- package.json has no preinstall/install/postinstall lifecycle hooks.
- Mutations are reached through explicit init/setup or HUD commands, not npm installation.
- Network use targets EchoMem APIs and npm registry; no credential-harvesting or covert exfiltration found.
- Child-process calls use fixed executables/arguments for CLI integration.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsMinifiedUrlStrings
NoLicense
Source & flagged code
6 flaggeddist/forensics.jsView file
19import path from "node:path";
L20: import { execFileSync } from "node:child_process";
L21: import { calculateContextMetrics } from "./context-metrics/calculate.js";
High
dist/headless-runtime.jsView file
65'if (!fs.existsSync(entry)) throw new Error("EchoMem MCP runtime is missing; run `npx -y @echomem/mcp@latest update --all`.");',
L66: "await import(pathToFileURL(entry).href);",
L67: "",
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/headless-runtime.jsView on unpkg · L65dist/hud/autostart.jsView file
Findings
4 High6 Medium5 Low
HighChild Processdist/forensics.js
HighShell
HighSame File Env Network Executiondist/hud/server.js
HighExternal Ai Agent Control Surface Mutationdist/hud/hooks.js
MediumDynamic Requiredist/headless-runtime.js
MediumNetwork
MediumEnvironment Vars
MediumInstall Persistencedist/hud/autostart.js
MediumShips Wasm Moduledist/city/vendor/rive.wasm
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @echomem/mcp@1.4.39.
See all versions of @echomem/mcp for other recorded verdicts.
- Review the evidence and your use of @echomem/mcp@1.4.39 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.