registry / @spikewang/grok-cli / 0.2.105-1

@spikewang/grok-cli@0.2.105-1

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

AI Security Review

scanned 3h ago · by lpm-firewall-ai

LPM treats this as warn-only first-party agent extension lifecycle risk. Install-time code mutates the shared `~/.grok/bin` directory. Runtime launches the locally resolved vendored binary.

Static reason

One or more suspicious static signals were detected.

Trigger

npm postinstall or explicit `grok-cli` execution

Impact

A package install can persist a package-supplied executable in the user's Grok home; no source-confirmed exfiltration or remote execution is present.

Mechanism

local binary installation, symlink replacement, and child-process launch

Rationale

The source establishes a real install-time persistence-like binary placement in `~/.grok/bin`, which warrants a warning under the lifecycle-control-surface policy. No concrete malicious chain is evidenced by the inspected package source.

Evidence

package.jsonbin/postinstall.jsbin/grok-cliREADME.md~/.grok/bin/grok-cli-<version>~/.grok/bin/grok-cli

Decision evidence

public snapshot

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

Evidence for warning

`package.json` runs `node bin/postinstall.js` during installation.

@spikewang/grok-cli@0.2.105-1

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Source & flagged code