registry  /  fcell2  /  1.0.5

fcell2@1.0.5

FIVO CELL — Unlimited memory AI coding assistant with BM25+TF-IDF retrieval, PII redaction, cost tracking, 3 modes, vault & vibe

AI Security Review

scanned 1d ago · by lpm-firewall-ai

LPM treats this as warn-only first-party agent extension lifecycle risk. Install-time code registers a packaged FIVO extension under the CELL agent's own home config namespace. This is agent extension lifecycle risk, but not a confirmed foreign agent hijack or malware payload.

Static reason
High-risk behavior combination matched malicious policy.
Trigger
npm install postinstall; later CELL agent session events load/use the extension
Impact
Enables memory/vault/mode/theme behavior for CELL and can read AGENTS.md/CLAUDE.md during runtime context construction.
Mechanism
package-owned agent extension copy
Policy narrative
On installation, fcell2 creates ~/.cell/agent/extensions and copies its bundled .pi/extensions/fivo.ts into that directory, while deleting an older ~/.cell/extensions/fivo.ts path. The extension is agent-facing: it stores memory/vault/mode/theme data under ~/.cell, registers slash commands, redacts common secrets from user input, and appends memory/project context to prompts. I found no install-time network fetch, exfiltration endpoint, or mutation of Claude/Codex/Cursor/MCP control surfaces.
Rationale
The lifecycle write is unconsented, but it targets the declared first-party CELL config namespace rather than a foreign/broad AI-agent control surface. Under the provided policy this fits guarded/package-owned agent extension lifecycle risk, not publish-block malware.
Evidence
package.json.pi/extensions/fivo.tsdist/core/extensions/loader.jsdist/cli.jsdist/index.js~/.cell/agent/extensions/fivo.ts~/.cell/extensions/fivo.ts~/.cell/memory.json~/.cell/vault.json~/.cell/vibe.md~/.cell/mode.json~/.cell/themes/cell-orange.jsonAGENTS.mdCLAUDE.md

Decision evidence

public snapshot
AI called this Suspicious at 86.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
  • package.json postinstall creates ~/.cell/agent/extensions and copies .pi/extensions/fivo.ts there
  • postinstall removes legacy ~/.cell/extensions/fivo.ts if present
  • copied extension reads/writes ~/.cell memory/vault/mode/theme files and injects memory/project context on agent events
Evidence against
  • package.json declares piConfig.configDir='.cell', so lifecycle target is the package's own app namespace
  • no postinstall network fetch or remote payload execution found
  • bin/import entrypoints are normal CLI/library entrypoints; dynamic extension loading is runtime platform functionality
Behavioral surface
Source
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell
Supply chain
HighEntropyStringsMinifiedUrlStrings
ManifestNo manifest risk signals triggered.
scanned 263 file(s), 2.30 MB of source, external domains: 127.0.0.1, api.anthropic.com, api.github.com, claude.ai, cli.github.com, cloud.gitlab.com, console.anthropic.com, distro.ibiblio.org, getcell.dev, git-scm.com, github.com, gitlab.com, mariozechner.at, mistral.ai

Source & flagged code

6 flagged · loading source
package.jsonView file
•scripts.postinstall = node -e "const{cpSync,mkdirSync,rmSync,existsSync}=require('fs');const{join}=require('path');const{homedir}=require('os');const d=join(homedir(),'.cell','agent','extensions');mkdir...
Critical
Red Install Lifecycle Script

Install-time lifecycle script matches a deterministic static-gate block pattern.

package.jsonView on unpkg
•scripts.postinstall = node -e "const{cpSync,mkdirSync,rmSync,existsSync}=require('fs');const{join}=require('path');const{homedir}=require('os');const d=join(homedir(),'.cell','agent','extensions');mkdir...
High
Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg
examples/extensions/doom-overlay/doom-engine.tsView file
64const nativeRequire = createRequire(doomJsPath); L65: const moduleFunc = new Function("module", "exports", "__dirname", "__filename", "require", doomJsCode); L66: moduleFunc(moduleExports, moduleExports.exports, buildDir, doomJsPath, nativeRequire);
Low
Eval

Package source references a known benign dynamic code generation pattern.

examples/extensions/doom-overlay/doom-engine.tsView on unpkg · L64
dist/core/extensions/loader.jsView file
52}; L53: const require = createRequire(import.meta.url); L54: /**
Medium
Dynamic Require

Package source references dynamic require/import behavior.

dist/core/extensions/loader.jsView on unpkg · L52
examples/extensions/doom-overlay/doom/build/doom.wasmView file
•path = examples/extensions/doom-overlay/doom/build/doom.wasm kind = wasm_module sizeBytes = 380169 magicHex = [redacted]
Medium
Ships Wasm Module

Package ships WebAssembly modules.

examples/extensions/doom-overlay/doom/build/doom.wasmView on unpkg
examples/extensions/doom-overlay/doom/build.shView file
•path = examples/extensions/doom-overlay/doom/build.sh kind = build_helper sizeBytes = 3366 magicHex = [redacted]
Medium
Ships Build Helper

Package ships non-JavaScript build or shell helper files.

examples/extensions/doom-overlay/doom/build.shView on unpkg

Findings

1 Critical1 High6 Medium6 Low
CriticalRed Install Lifecycle Scriptpackage.json
HighInstall Time Lifecycle Scriptspackage.json
MediumDynamic Requiredist/core/extensions/loader.js
MediumNetwork
MediumEnvironment Vars
MediumShips Wasm Moduleexamples/extensions/doom-overlay/doom/build/doom.wasm
MediumShips Build Helperexamples/extensions/doom-overlay/doom/build.sh
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowEvalexamples/extensions/doom-overlay/doom-engine.ts
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings