registry  /  fcell2  /  0.0.7

fcell2@0.0.7

Coding agent CLI with read, bash, edit, write tools and session management

AI Security Review

scanned 2d ago · by lpm-firewall-ai

LPM treats this as warn-only first-party agent extension lifecycle risk. Install-time lifecycle code installs a package-supplied agent extension into the user's global ~/.cell agent extension directory. The extension can affect future CELL sessions by injecting local memory/context into prompts and managing active tools.

Static reason
High-risk behavior combination matched malicious policy.
Trigger
npm install or package lifecycle postinstall
Impact
Persistent package-owned agent behavior under ~/.cell; no confirmed exfiltration or foreign agent hijack.
Mechanism
first-party global agent extension installation
Policy narrative
On install, package.json runs node -e code that creates ~/.cell/agent/extensions and copies .pi/extensions/fivo.ts there. The copied extension is then discoverable by the CELL agent runtime and can inject memory/context before agent starts, redact input, register slash commands, switch tool sets, and write CELL-local state files. This is lifecycle agent-extension setup, but it is confined to the package's own .cell namespace and shows no network exfiltration or foreign agent control-surface mutation.
Rationale
The package performs unprompted lifecycle installation of an agent extension, which is risky enough to warn, but source inspection shows it targets its own configured ~/.cell namespace and lacks confirmed malicious exfiltration or foreign AI-agent hijacking. Under the policy this fits first-party agent extension lifecycle risk rather than publish-block malware.
Evidence
package.json.pi/extensions/fivo.tsdist/config.jsdist/core/extensions/loader.js~/.cell/agent/extensions/fivo.ts~/.cell/memory.json~/.cell/vault.json~/.cell/mode.json~/.cell/themes/cell-orange.json

Decision evidence

public snapshot
AI called this Suspicious at 87.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
  • package.json postinstall copies .pi/extensions/fivo.ts into ~/.cell/agent/extensions/fivo.ts without prompting.
  • package.json piConfig sets configDir to .cell; dist/config.js getAgentDir resolves to ~/.cell/agent.
  • .pi/extensions/fivo.ts registers an always-loaded extension that alters prompts with stored memory/context and changes active tools by mode.
  • .pi/extensions/fivo.ts persists memory, vault, mode, and theme files under ~/.cell.
Evidence against
  • No evidence of network exfiltration in the lifecycle script or fivo extension.
  • The lifecycle destination is the package's own configured app namespace, not Claude/Codex/Cursor/MCP or another foreign agent surface.
  • Vault writes are user-invoked slash commands and displayed values are masked.
  • The extension redacts common API tokens from input before agent processing.
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}=require('fs');const{join}=require('path');const{homedir}=require('os');const d=join(homedir(),'.cell','agent','extensions');mkdirSync(d,{recursive:...
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}=require('fs');const{join}=require('path');const{homedir}=require('os');const d=join(homedir(),'.cell','agent','extensions');mkdirSync(d,{recursive:...
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