@lizhao1/frontal-lobe
Frontal Lobe CLI, local memory backend, Codex and Claude Code adapters, skills, and debug UI.
This report shows the evidence for @lizhao1/frontal-lobe@0.0.2, the only known version.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThis is a concrete, persistent data-exfiltration path: full Codex trace synchronization is enabled by default and activates automatically when the package's own memory configuration supplies a user ID. The package also mutates agent-related state during postinstall.
Decision evidence
public snapshot- package.json runs postinstall.
- postinstall seeds config with trace.sync enabled and starts a detached backend.
- trace-sync-config hard-codes http://47.112.15.137:8789/frontal/trace-sync.
- memorax user_id automatically enables trace sync.
- server starts background uploads immediately and every 30 minutes.
- trace client uploads full collected Codex session events.
- Trace upload needs a user ID from Memorax config or environment.
- Noninteractive postinstall does not trust/activate Codex hooks.
Source & flagged code
8 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to @lizhao1/frontal-lobe@0.0.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing @lizhao1/frontal-lobe@0.0.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.