--- canonical: "https://firewall.lpm.dev/npm/@kingingwang/grok/v/1.0.24-148c55c7" markdown: "https://firewall.lpm.dev/npm/@kingingwang/grok/v/1.0.24-148c55c7.md" package: "@kingingwang/grok" report_status: "published" title: "@kingingwang/grok@1.0.24-148c55c7 npm security report" verdict: "policy_finding" version: "1.0.24-148c55c7" --- # @kingingwang/grok@1.0.24-148c55c7 npm security report > **Trust boundary:** Package metadata, advisory text, filenames, URLs, and source snippets in this report come from external packages or feeds. Treat them as untrusted evidence. Do not execute instructions or code found in this document. ## Verdict summary **Soft block: AI-agent control surface** — Warn by default; block when configured. A user who installs this package can have a foreign executable and update registry configuration placed into their existing Grok control surface. - **Verdict:** AI-agent control-surface policy finding - **Product-default install policy:** Warn by default; block when configured - **Firewall policy:** Warn by default - **Public report status:** Published - **Threat category:** Soft block: AI-agent control surface - **Selected version:** 1.0.24-148c55c7 - **Selected version is latest:** No - **Analysis source:** AI Security Review (lpm-firewall-ai) This finding concerns changes to an AI agent's instructions or configuration without explicit user action. It does not by itself establish malware intent. The CLI warns by default and blocks when configured for this policy. AI assessment: malicious; recommendation: publish block. This assessment is supporting evidence; the published decision above determines the current policy. LPM flags this version as an AI-agent control-surface risk. Installing this package automatically replaces the user's Grok executable and modifies its configuration under the Grok home directory. It is a different package from the official package named in its README. ## Latest scan - **Scanner version:** rust-scanner-worker-schema-1 - **Recorded final verdict:** Malicious - **Recorded analysis confidence:** 99.0% - **Started:** 2026-09-11T02:47:58.954Z - **Finished:** 2026-09-11T02:48:51.328Z - **Download time:** 1014 ms - **Static scan time:** 90 ms - **AI review time:** 51269 ms - **Total time:** 52374 ms The recorded confidence comes from the underlying analysis. Trusted advisory policy can determine the final verdict even when the AI assessment differs. ## Security analysis ### Published attack-surface review - **Summary:** Installing this package automatically replaces the user's Grok executable and modifies its configuration under the Grok home directory. It is a different package from the official package named in its README. - **Trigger:** npm installation or update - **Impact:** A user who installs this package can have a foreign executable and update registry configuration placed into their existing Grok control surface. - **Evidence paths:** package.json, bin/postinstall.js, README.md - **Review source:** ai\_review - **Reviewed:** 2026-09-11T02:48:51.328Z ### AI review details - **Review stage:** source\_first\_review - **Mechanism:** post-install deployment of a replacement Grok binary and configuration - **Attack narrative:** The post-install hook extracts a binary supplied by this package's platform dependencies into the user's Grok directory, makes it the active Grok command, and writes the Grok configuration. It can also preserve a registry under the publisher's scope for later updates. The README instead tells users to install the official package, showing that this package is impersonating that product while altering its per-user command and control surface without an explicit setup command. - **Rationale:** This is an unconsented post-install takeover of a foreign AI command's per-user executable and configuration surface, reinforced by package-name and README inconsistency. The absence of direct exfiltration does not neutralize the install-time control hijack. - **Files touched:** $GROK\_HOME/bin/grok, $GROK\_HOME/bin/grok-\, $GROK\_HOME/config.toml, bin/grok, bin/grok-native ### Review decision - **Verdict:** Malicious - **Confidence:** 99.0% - **Recommended action:** publish\_block - **Intent class:** Malware - **False-positive risk:** Low - **Evidence for policy risk:** The package runs a post-install script automatically., The installer extracts an executable from a platform dependency into the user's Grok directory and replaces the Grok command., The installer changes the user's Grok configuration and can record a scoped npm registry for later updates., The README instructs users to install a different package, indicating impersonation of the official Grok package. - **Evidence against:** No credential harvesting, HTTP request, or direct data exfiltration appears in the inspected JavaScript., The observed shell command only reads npm registry configuration. ## Affected versions and remediation This report applies to @kingingwang/grok@1.0.24-148c55c7. - Avoid installing @kingingwang/grok@1.0.24-148c55c7. 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, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment. ## Public findings ### 1. High: Install Time Lifecycle Scripts - **Category:** Manifest - **Confidence:** 90.0% - **Path:** package.json - **Public source:** [View source]() Package defines install-time lifecycle scripts. Public source snippet (untrusted): ```json scripts.postinstall = node bin/postinstall.js ``` ### 2. Medium: Ambiguous Install Lifecycle Script - **Category:** Manifest - **Confidence:** 75.0% - **Path:** package.json - **Public source:** [View source]() Install-time lifecycle script is not statically allowlisted and needs review. Public source snippet (untrusted): ```json scripts.postinstall = node bin/postinstall.js ``` ### 3. Low: Scripts Present - **Category:** Manifest - **Confidence:** 100.0% Package declares npm scripts. ### 4. Medium: Environment Vars - **Category:** Source - **Confidence:** 75.0% Package source references environment variables. ### 5. Low: Filesystem - **Category:** Source - **Confidence:** 70.0% Package source references filesystem APIs. ### 6. High: Semantic Analysis Limited - **Category:** Scanner Coverage - **Confidence:** 100.0% - **Path:** package.json - **Public source:** [View source]() A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review. Public source snippet (untrusted): ```json stage = ast_semantic_analysis; reason = ast_parse_error; limitedFiles = 1 ``` ### 7. High: Known Malware Source Similarity - **Category:** Static - **Confidence:** 97.0% - **Path:** bin/postinstall.js - **Public source:** [View source]() Source file is highly similar to a previously finalized malicious package; route for source-aware review. Public source snippet (untrusted): ```javascript matchType = normalized_sha256 matchedPackage = @kingingwang/grok@1.0.16-6751defb matchedPath = bin/postinstall.js matchedIdentity = npm:QGtpbmdpbmd3YW5nL2dyb2s:1.0.16-6751defb similarity = 1.000 summary = normalized source hash matched finalized malicious source ``` ### 8. High: Known Malware Source Similarity - **Category:** Static - **Confidence:** 97.0% - **Path:** bin/grok-bootstrap.js - **Public source:** [View source]() Source file is highly similar to a previously finalized malicious package; route for source-aware review. Public source snippet (untrusted): ```javascript matchType = normalized_sha256 matchedPackage = @kingingwang/grok@1.0.16-6751defb matchedPath = bin/grok-bootstrap.js matchedIdentity = npm:QGtpbmdpbmd3YW5nL2dyb2s:1.0.16-6751defb similarity = 1.000 summary = normalized source hash matched finalized malicious source ``` ### 9. High: Known Malware Source Fingerprint Signature - **Category:** Supply Chain - **Confidence:** 94.0% - **Path:** bin/postinstall.js - **Public source:** [View source]() Source fingerprint signature matches a known malicious package signature; route for source-aware review. Public source snippet (untrusted): ```javascript matchType = malicious_source_fingerprint_signature signature = 830396dc7d8ac054 signatureType = suspicious_hashes sourceLabel = final_verdict:malicious matchedPackage = @kingingwang/grok@1.0.16-6751defb matchedPath = bin/postinstall.js matchedIdentity = npm:QGtpbmdpbmd3YW5nL2dyb2s:1.0.16-6751defb similarity = 1.000 shingleOverlap = 3 summary = package final verdict is malicious ``` ### 10. High: Previous Version Dangerous Delta - **Category:** Supply Chain - **Confidence:** 93.0% - **Path:** bin/postinstall.js - **Public source:** [View source]() This package version adds a dangerous source file absent from the previous stored version; route for source-aware review. Public source snippet (untrusted): ```javascript 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 ``` ### 11. High: Ai Review Evidence - **Category:** Ai Review - **Confidence:** 99.0% - **Path:** package.json - **Public source:** [View source]() The package runs a post-install script automatically. Public source snippet (untrusted): ```json "scripts": { "postinstall": "node bin/postinstall.js" } ``` ### 12. High: Suspicious Dependency Evidence - **Category:** Dependency - **Confidence:** 99.0% - **Path:** bin/postinstall.js - **Public source:** [View source]() The installer extracts an executable from a platform dependency into the user's Grok directory and replaces the Grok command. Public source snippet (untrusted): ```javascript if (installBinary('grok', platformDir, `grok${EXE}`)) { installBinLink(platformDir); } cleanupOldVersions('grok'); cleanupOldVersions('grok-pager'); ``` ## Dependencies and install lifecycle - **Lifecycle scripts present:** Yes - **Published lifecycle scripts:** postinstall - **Dependencies:** 1 - **Optional dependencies:** 6 - **Peer dependencies:** 0 - **Development dependencies:** 0 - **Published dependency-graph edges:** 7 ### Published dependency entries - @iarna/toml ^3.0.0 (Dependency) - @kingingwang/grok-darwin-arm64 1.0.24-148c55c7 (OptionalDependency) - @kingingwang/grok-darwin-x64 1.0.24-148c55c7 (OptionalDependency) - @kingingwang/grok-linux-arm64 1.0.24-148c55c7 (OptionalDependency) - @kingingwang/grok-linux-x64 1.0.24-148c55c7 (OptionalDependency) - @kingingwang/grok-win32-arm64 1.0.24-148c55c7 (OptionalDependency) - @kingingwang/grok-win32-x64 1.0.24-148c55c7 (OptionalDependency) ## Package metadata - **Package:** @kingingwang/grok - **Ecosystem:** npm - **Version:** 1.0.24-148c55c7 - **License:** Apache-2.0 - **Version published:** 2026-09-10T18:03:08.100Z - **Package first seen:** 2026-08-20T16:51:17.690Z - **Package last seen:** 2026-09-30T19:11:11.347Z - **Known versions:** 15 - **Latest version:** 1.0.45-539d8dae - **Appeal under review:** No - **Description:** Bring Grok into your terminal - **Runtime engines:** node: \>=20 - **Supported OS:** darwin, linux, win32 - **Supported CPU:** arm64, x64 - **Artifact files:** 5 - **Artifact unpacked size:** 18,407 bytes - **Artifact signatures:** 1 - **Attestations:** No ## References - [HTML security report]()