Loading npm security reports…

@kingingwang/grok@1.0.32-aae58918: AI-agent control-surface risk | LPM Firewall

registry / @kingingwang/grok / 1.0.32-aae58918

@kingingwang/grok@1.0.32-aae58918

Bring Grok into your terminal

AI Security Review

scanned 20d ago · by lpm-firewall-ai

LPM flags this version as an AI-agent control-surface risk. On npm install, postinstall drops a native grok binary into the official Grok CLI home and rewrites its config. That is an unconsented change to a foreign AI-agent control surface from a non-official scope.

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.

AI rationale

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.

Evidence

package.jsonbin/postinstall.jsbin/grok-bootstrap.js~/.grok/bin/grok~/.grok/config.tomlbin/grok

Source & flagged code

9 flagged · loading source

package.jsonView file

•scripts.postinstall = node bin/postinstall.js

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

21"scripts": { "postinstall": "node bin/postinstall.js" },

High

Suspicious Lifecycle Evidence

Automatic postinstall runs node bin/postinstall.js on npm install.

package.jsonView on unpkg · L21

•scripts.postinstall = node bin/postinstall.js

Medium

Ambiguous Install Lifecycle Script

Install-time lifecycle script is not statically allowlisted and needs review.

package.jsonView on unpkg

bin/postinstall.jsView file

•matchType = normalized_sha256 matchedPackage = @kingingwang/grok@1.0.35-7096013f matchedPath = bin/postinstall.js matchedIdentity = npm:QGtpbmdpbmd3YW5nL2dyb2s:1.0.35-7096013f similarity = 1.000 summary = normalized source hash matched finalized malicious source

High

Known Malware Source Similarity

Source file is highly similar to a previously finalized malicious package; route for source-aware review.

bin/postinstall.jsView on unpkg

•matchType = malicious_source_fingerprint_signature signature = 830396dc7d8ac054 signatureType = suspicious_hashes sourceLabel = final_verdict:malicious matchedPackage = @kingingwang/grok@1.0.35-7096013f matchedPath = bin/postinstall.js matchedIdentity = npm:QGtpbmdpbmd3YW5nL2dyb2s:1.0.35-7096013f similarity = 1.000 shingleOverlap = 3 summary = package final verdict is malicious

High

Known Malware Source Fingerprint Signature

Source fingerprint signature matches a known malicious package signature; route for source-aware review.

bin/postinstall.jsView on unpkg

•matchType = previous_version_dangerous_delta matchedPackage = @kingingwang/grok@1.0.12-8d051d60 matchedIdentity = npm:QGtpbmdpbmd3YW5nL2dyb2s:1.0.12-8d051d60 similarity = 0.500 summary = stored previous version shares package body but lacks this dangerous source file

High

Previous Version Dangerous Delta

This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.

bin/postinstall.jsView on unpkg

22function defaultGrokHome() { const home = os.homedir(); try { return path.join(fs.realpathSync(home), '.grok'); } catch { return path.join(home, '.grok'); } } const GROK_HOME = process.env.GROK_HOME ?? defaultGrokHome(); const CANONICAL_DIR = path.join(GROK_HOME, 'bin');

High

Suspicious Lifecycle Evidence

Postinstall extracts a native grok binary into the user home .grok/bin directory, which is the official Grok CLI location.

bin/postinstall.jsView on unpkg · L22

215if (installBinary('grok', platformDir, `grok${EXE}`)) { installBinLink(platformDir); }

High

Suspicious Lifecycle Evidence

Postinstall extracts a native grok binary into the user home .grok/bin directory, which is the official Grok CLI location.

bin/postinstall.jsView on unpkg · L215

bin/grok-bootstrap.jsView file

•matchType = normalized_sha256 matchedPackage = @kingingwang/grok@1.0.35-7096013f matchedPath = bin/grok-bootstrap.js matchedIdentity = npm:QGtpbmdpbmd3YW5nL2dyb2s:1.0.35-7096013f similarity = 1.000 summary = normalized source hash matched finalized malicious source

High

Known Malware Source Similarity

Source file is highly similar to a previously finalized malicious package; route for source-aware review.

bin/grok-bootstrap.jsView on unpkg

Source & flagged code

9 flagged

package.jsonView file

Lines 1-42json

1{

2 "name": "@kingingwang/grok",

3 "version": "1.0.32-aae58918",

4 "description": "Bring Grok into your terminal",

5 "license": "Apache-2.0",

6 "bin": {

7 "grok": "bin/grok"

8 },

9 "files": [

10 "bin/"

11 ],

12 "os": [

13 "darwin",

14 "linux",

15 "win32"

16 ],

17 "cpu": [

18 "arm64",

19 "x64"

20 ],

21 "scripts": {

22 "postinstall": "node bin/postinstall.js"

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg · L22

Medium

Ambiguous Install Lifecycle Script

Install-time lifecycle script is not statically allowlisted and needs review.

package.jsonView on unpkg · L22

23 },

High

Suspicious Lifecycle Evidence

Automatic postinstall runs node bin/postinstall.js on npm install.

package.jsonView on unpkg · L21

24 "publishConfig": {

25 "access": "public"

26 },

27 "engines": {

28 "node": ">=20"

29 },

30 "dependencies": {

31 "@iarna/toml": "^3.0.0"

32 },

33 "optionalDependencies": {

34 "@kingingwang/grok-darwin-arm64": "1.0.32-aae58918",

35 "@kingingwang/grok-darwin-x64": "1.0.32-aae58918",

36 "@kingingwang/grok-linux-arm64": "1.0.32-aae58918",

37 "@kingingwang/grok-linux-x64": "1.0.32-aae58918",

38 "@kingingwang/grok-win32-arm64": "1.0.32-aae58918",

39 "@kingingwang/grok-win32-x64": "1.0.32-aae58918"

40 }

41}

42

bin/postinstall.jsView file

Lines 2-42javascript

2// Runs once after npm install/update. Reads the grok binary from the

3// matching per-platform optional dependency (@kingingwang/grok-<platform>)

4// and installs it to ~/.grok/bin/ using versioned filenames:

5//

6// Unix: grok-<version> + grok (symlink)

7// Windows: grok-<version>.exe + grok.exe (copy)

8//

9// Versioned files ensure running processes are never disrupted on macOS

10// (replacing a binary that a running process has mmap'd causes SIGKILL

11// because the kernel can no longer verify the code signature).

bin/grok-bootstrap.jsView file

•matchType = normalized_sha256 matchedPackage = @kingingwang/grok@1.0.35-7096013f matchedPath = bin/grok-bootstrap.js matchedIdentity = npm:QGtpbmdpbmd3YW5nL2dyb2s:1.0.35-7096013f similarity = 1.000 summary = normalized source hash matched finalized malicious source

High

Known Malware Source Similarity

Source file is highly similar to a previously finalized malicious package; route for source-aware review.

bin/grok-bootstrap.jsView on unpkg