registry / AI-agent control-surface risk / @shuv1337/shuvgrok
@shuv1337/shuvgrok
ShuvGrok: bring Grok into your terminal
This report shows the evidence for @shuv1337/shuvgrok@1.0.6. 3 of 4 known versions are blocked or flagged. The newest version, 1.0.7, is flagged. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe automatic lifecycle hook modifies the shared ~/.grok executable and configuration surface, including registry selection. No direct exfiltration is present in the inspected JavaScript, but the install-time control-surface mutation is concrete and sufficient to block.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
npm installation or update
Impact
Can alter the executable and registry configuration used in ~/.grok without an explicit setup command.
Mechanism
Postinstall deployment and shared AI-client configuration mutation
Policy narrative
Installing the package invokes postinstall automatically. That code materializes an opaque platform binary under ~/.grok/bin and modifies ~/.grok/config.toml, a location it identifies as shared with the upstream Grok client. It also persists a registry setting derived from GROK_NPM_REGISTRY or npm configuration. This is an unconsented install-time mutation of a foreign/shared AI-agent control surface.
AI rationale
The automatic lifecycle hook modifies the shared ~/.grok executable and configuration surface, including registry selection. No direct exfiltration is present in the inspected JavaScript, but the install-time control-surface mutation is concrete and sufficient to block.
Evidence
package.jsonbin/postinstall.js~/.grok/bin/shuvgrok-<version>~/.grok/bin/shuvgrok~/.grok/config.toml
Decision evidence
public snapshotAI identified this as a dangerous AI-agent capability at 94.0% confidence with low false-positive risk.
Evidence for policy risk
- Installation automatically runs a Node postinstall program.
- The postinstall program creates a shared ~/.grok bin directory and installs an executable there.
- It rewrites ~/.grok/config.toml and records a registry value from the environment or npm configuration.
- The shared config location is explicitly described as compatible with the upstream Grok installation.
Evidence against
- The inspected JavaScript contains no direct network request or credential-exfiltration code.
- The platform payload is resolved from fixed optional dependencies rather than a runtime download.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemShell
Source & flagged code
8 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node bin/postinstall.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•stage = ast_semantic_analysis; reason = ast_parse_error; limitedFiles = 1
High
Semantic Analysis Limited
A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
package.jsonView on unpkg25"scripts": {
"postinstall": "node bin/postinstall.js"
}
High
Suspicious Lifecycle Evidence
Installation automatically runs a Node postinstall program.
package.jsonView on unpkg · L25•scripts.postinstall = node bin/postinstall.js
Medium
Ambiguous Install Lifecycle Script
Findings
7 High2 Medium2 Low
HighInstall Time Lifecycle Scriptspackage.json
HighSemantic Analysis Limitedpackage.json
HighKnown Malware Source Similaritybin/postinstall.js
HighSuspicious Lifecycle Evidencepackage.json
HighSuspicious Lifecycle Evidencebin/postinstall.js
HighAi Review Evidencebin/postinstall.js
HighAi Review Evidencebin/postinstall.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumEnvironment Vars
LowScripts Present
LowFilesystem
Affected versions and remediation
This report applies to @shuv1337/shuvgrok@1.0.6.
The versions list below shows the verdict for each recorded version.
- Avoid installing @shuv1337/shuvgrok@1.0.6. 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.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.
Versions
4 known versions1.0.7latestSuspiciousAgent extension lifecycle riskWarnPublishedAug 31, 2026, 9:39 AM1.0.6shownMaliciousSoft block: AI-agent control surfaceBlockPublishedAug 31, 2026, 6:12 AM1.0.5MaliciousSoft block: AI-agent control surfaceBlockPublishedAug 17, 2026, 11:35 PM1.0.4MaliciousSoft block: AI-agent control surfaceBlockPublished