Warn by default; block when configured. Later grok invocations can run the publisher's binary, and an existing official CLI install under ~/.grok can be overwritten.
AI security review
scanned · by lpm-firewall-ai
This is a cloned official Grok CLI wrapper published as @kingingwang/grok. Its postinstall automatically plants a native binary and config into ~/.grok, hijacking another vendor's Grok CLI control surface.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
npm install of @kingingwang/grok runs the postinstall script.
Impact
Later grok invocations can run the publisher's binary, and an existing official CLI install under ~/.grok can be overwritten.
Mechanism
Install-time drop of a native grok binary and config into the official Grok home directory
Policy narrative
This package impersonates the official Grok CLI while publishing as @kingingwang/grok. After npm install, postinstall.js extracts a native binary from @kingingwang/grok platform packages, installs it to ~/.grok/bin, and rewrites ~/.grok/config.toml. That directory belongs to the official Grok CLI, so an existing grok install can be replaced with no extra command. README and grok-bootstrap.js still name @xai-official/grok, showing a cloned official launcher under another npm scope. Running grok then executes the dropped binary.
Avoid installing @kingingwang/grok@1.0.35-7096013f. 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, check your AI agents' configuration and instruction files (the files this report lists) for changes you did not make, and remove them. This finding does not by itself establish malware intent.