memoryrouter-codex@1.8.2
Automatic MemoryRouter memory for OpenAI Codex: one vault shared by every session, repo and tool, including Claude Code
AI Security Review
scanned 1d ago · by lpm-firewall-aiA normal hook event can start paid `codex exec` work in the background by default, based on a server response and without per-run approval. The behavior is disclosed and bounded, but opting out is required; the review rules classify automatic spending as malicious.
Decision evidence
public snapshot- Normal Codex hook events automatically start consolidation when the service reports debt; it is enabled by default.
- The hook starts a detached `reflect-auto` process without asking for per-run approval.
- That process runs `codex exec` to consolidate memories, consuming the user's inference quota.
- The README confirms this uses the user's paid inference and says users must opt out in config.
- The package has no install, preinstall, or postinstall lifecycle script.
- Memory API requests send the key and memory data to the package's own MemoryRouter service.
- The automatic run is disclosed, limited to three batches per trigger, and can be disabled in config.
Source & flagged code
6 flaggedPackage source references child process execution.
runtime/project.cjsView on unpkg · L29A single source file combines environment access, network access, and code or shell execution; review context before blocking.
lib/installer.cjsView on unpkg · L174Manifest-trigger-reachable source writes behavior-bearing configuration into a user or project AI-agent control surface.
lib/installer.cjsView on unpkgNormal Codex hook events automatically start consolidation when the service reports debt; it is enabled by default.
runtime/hook.cjsView on unpkg · L110The hook starts a detached `reflect-auto` process without asking for per-run approval.
runtime/auto.cjsView on unpkg · L147That process runs `codex exec` to consolidate memories, consuming the user's inference quota.
runtime/reflect.cjsView on unpkg · L88Findings
Affected versions and remediation
This report applies to memoryrouter-codex@1.8.2.
See all versions of memoryrouter-codex for other recorded verdicts.
- Avoid installing memoryrouter-codex@1.8.2. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.