M8M – See what your AI remembers about you and detect memory poisoning A tool called m8m has launched to give users visibility into what AI agents remember about them, detecting memory poisoning and tracking memory provenance through a local SQLite database with an MCP server, file watcher, and CLI. The project cites Microsoft Security's identification of 50 memory poisoning attempts across 31 companies in 60 days as of February 2026, and notes that GPT-5.4 showed an 87.5% injection success rate. Phase 1 runs entirely locally with zero LLM or network calls in the analyzer, installed via npm install -g @th0t3p/m8m. AI memory observability, provenance & security. Eight eyes. Nothing gets past. m8m monitors what your AI agents remember about you — where each memory came from, what changed, and whether anything looks suspicious. The core pieces share one local SQLite database: - MCP server — live memory operations as your agent works - File watcher — tracks local memory files MEMORY.md , CLAUDE.md , … ; it runs automatically inside the MCP server and can also run standalone via m8m watch - Security analysis — pattern-based scanning of every memory for credentials, instructions, URLs/emails, and hidden characters - Snapshots & rollback — point-in-time baselines to diff drift and roll back - CLI — query and audit memory state from the terminal - Local dashboard — a dark, browser-based visualization Phase 1 is entirely local: SQLite storage, pattern-based analysis, and zero LLM or network calls in the analyzer itself. Your AI remembers everything about you — preferences, habits, work patterns, relationships. But do you know what it remembers? Can you tell if those memories have been tampered with? - Microsoft Security identified 50 memory poisoning attempts across 31 companies in just 60 days Feb 2026 - A single email can silently rewrite your AI agent's memory MemGhost, Jul 2026 https://arxiv.org - More capable models are more vulnerable , not less — GPT-5.4 showed 87.5% injection success rate m8m gives you visibility and control. Think of it as git log for your AI's memory. npm install -g @th0t3p/m8m ./scripts/install.sh That installs dependencies, builds, and runs npm link so m8m is on your PATH . Equivalent manual steps: npm install then npm install -g . . node dist/cli/index.js --help npx tsx src/cli/index.ts --help The first command requires npm run build first; the second runs TypeScript directly with no build. Data location: everything lives in ~/.m8m/ by default. If ~ is read-only e.g. some sandboxes , set M8M HOME to a writable directory: export M8M HOME=/path/to/m8m-data . m8m init m8m import ./MEMORY.md --platform local file m8m status m8m list --flagged m8m audit | Command | Description | |---|---| | m8m init | Initialize config + database | | m8m status | Overview of agent + file memories, flags, security events | | m8m list --platform