Warn by default; block when configured. An existing Grok CLI install can be replaced so later grok commands run the binary shipped by this publisher.
AI security review
scanned · by lpm-firewall-ai
Automatic postinstall writes a native binary and config into ~/.grok, a foreign Grok agent control surface, from a different npm scope. That unconsented install-time hijack is concrete attack behavior and should be blocked.
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, which runs the postinstall script with no extra user command.
Impact
An existing Grok CLI install can be replaced so later grok commands run the binary shipped by this publisher.
Mechanism
install-time write of a vendor binary and config into ~/.grok
Policy narrative
On npm install, postinstall.js copies a native binary from the @kingingwang/grok platform optional dependency into ~/.grok/bin and rewrites ~/.grok/config.toml. That directory is the official Grok CLI home, so this silent hook can replace an existing grok binary and take over later grok commands. The package is published under the kingingwang scope while the launcher still looks up official @xai-official/grok platform packages, which is impersonation rather than a first-party installer.
Avoid installing @kingingwang/grok@1.0.32-aae58918. 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.