@echomem/mcp@1.4.37
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 malicious chain or npm lifecycle abuse was found. Automatic remote runtime replacement and optional agent-hook installation remain material dangerous capabilities requiring a warning.
Static reason
No blocking static signals were detected.
Trigger
Run the MCP server; an available registry update triggers the background installer.
Impact
A newer registry package can become executable in a later MCP session without a separate update command.
Mechanism
automatic remote package staging and dynamic entry import
AI rationale
No concrete malicious chain or npm lifecycle abuse was found. Automatic remote runtime replacement and optional agent-hook installation remain material dangerous capabilities requiring a warning.
Evidence
package.jsondist/index.jsdist/headless-runtime.jsdist/update-check.jsdist/hud/hooks.jsdist/hud/autostart.js$ECHO_CONFIG_DIR/mcp-runtime/active.json$ECHO_CONFIG_DIR/mcp-runtime/launcher.mjs~/.codex/hooks.json~/.claude/settings.json~/Library/LaunchAgents/com.echomem.hud.plist
Network endpoints2
registry.npmjs.org/%40echomem%2Fmcp/latestecho-mem-chrome.vercel.app
Decision evidence
public snapshotAI called this Suspicious at 88.0% confidence as Unknown with low false-positive risk.
Evidence for warning
- dist/index.js auto-installs a newer package after its background update check.
- dist/headless-runtime.js runs npm install and creates a launcher that dynamically imports the installed entry.
- dist/hud/hooks.js can add executable hooks to ~/.codex and ~/.claude.
Evidence against
- package.json has no preinstall, install, or postinstall lifecycle hook.
- Hook and autostart writes are reached only through named HUD CLI/UI actions.
- Network API calls target the declared EchoMem service and use the stored bearer token.
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.37.
See all versions of @echomem/mcp for other recorded verdicts.
- Review the evidence and your use of @echomem/mcp@1.4.37 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.