registry / @spikewang/grok-cli / 0.1.224

@spikewang/grok-cli@0.1.224

Grok coding agent CLI fork (command: grok-cli; does not replace official grok)

AI Security Review

scanned 2h ago · by lpm-firewall-ai

LPM treats this as warn-only first-party agent extension lifecycle risk. Install-time code writes and symlinks an executable into the shared `~/.grok/bin` directory. Runtime then executes that canonical binary with inherited environment variables. No confirmed network or data-exfiltration behavior appears in reviewed source.

Static reason

One or more suspicious static signals were detected.

Trigger

npm postinstall; later `grok-cli` invocation

Impact

A package-supplied native binary becomes the preferred executable for `grok-cli`; its opaque optional-dependency payload was not available to inspect.

Mechanism

install-time binary persistence in a Grok home directory

Rationale

The package has a concrete lifecycle persistence surface in `~/.grok/bin`, but its reviewed JavaScript is otherwise package-aligned and lacks a confirmed malicious chain. Flag as warn because the native binary it installs and executes is outside the extracted source available for inspection.

Evidence

package.jsonbin/postinstall.jsbin/grok-cliREADME.md@spikewang/grok-cli-darwin-*/bin/grok-cli[.br]~/.grok/bin/grok-cli-<version>~/.grok/bin/grok-cli

Decision evidence

public snapshot

AI called this Suspicious at 85.0% confidence as Dangerous Capability with false-positive risk.

@spikewang/grok-cli@0.1.224

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Source & flagged code