@echomem/mcp@1.4.41
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 was confirmed. The package is suspicious because explicit setup installs broad AI-agent behavior and runtime auto-update capability, warranting a warning rather than a block.
Static reason
No blocking static signals were detected.; previous stored version diff introduced dangerous source
Trigger
User runs `echomem-mcp init` or `setup`; later MCP startup receives an update-available status.
Impact
Future Codex/Claude sessions may invoke package-controlled commands and follow EchoMem-preference guidance.
Mechanism
Explicit agent-control-surface configuration plus background self-update.
AI rationale
No concrete malicious chain was confirmed. The package is suspicious because explicit setup installs broad AI-agent behavior and runtime auto-update capability, warranting a warning rather than a block.
Evidence
package.jsondist/setup.jsdist/hud/hooks.jsdist/headless-runtime.jsdist/index.js~/.codex/config.toml~/.codex/AGENTS.md~/.codex/hooks.json~/.claude/CLAUDE.md~/.claude/settings.json~/.echomem/mcp-runtime
Network endpoints2
registry.npmjs.orgecho-mem-chrome.vercel.app
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- `init` configures every installed coding agent and writes global guidance by default.
- Global guidance tells agents to prefer EchoMem and automatically save qualifying work.
- Setup installs Codex/Claude lifecycle hooks that execute package commands on session events.
- Running MCP code auto-installs an update after an npm-registry update check.
Evidence against
- package.json has no preinstall, install, or postinstall hook.
- Config, guidance, and hooks are reached through explicit `init`/`setup` commands.
- Hook commands point to this package's own CLI; no credential harvesting or unrelated-file overwrite was confirmed.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsMinifiedUrlStrings
Source & flagged code
10 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
8 High6 Medium5 Low
HighChild Processdist/forensics.js
HighShell
HighSame File Env Network Executiondist/hud/server.js
HighCredential Redirect Persistencedist/setup.js
HighEntrypoint Foreign Package Code Overwritedist/setup.js
HighExternal Ai Agent Control Surface Mutationdist/hud/hooks.js
HighTrigger Reachable External Ai Agent Control Surface Mutationdist/hud/hooks.js
HighPrevious Version Dangerous Deltadist/setup.js
MediumDynamic Requiredist/headless-runtime.js
MediumNetwork
MediumEnvironment Vars
MediumInstall Persistencedist/hud/autostart.js
MediumShips Wasm Module
Affected versions and remediation
This report applies to @echomem/mcp@1.4.41.
See all versions of @echomem/mcp for other recorded verdicts.
- Review the evidence and your use of @echomem/mcp@1.4.41 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.