The postinstall performs guarded, package-owned skill setup in a specific Bot account library, so the scanner's control-hijack label overstates the inspected behavior. Because the setup still changes agent workflows automatically during global installation, a warning is appropriate.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Installing the package globally with npm on a qualified Grok Bot Linux account.
Impact
The agent's available workflow skills are modified without a separate setup command.
Mechanism
The postinstall hook invokes the package's add command for bundled skills when the verified account library has no existing managed roots.
Evidence
package.jsonbin/grokbot-postinstall.jsdist/cli/grokbot-postinstall.jsdist/hosts/index.jsdist/catalog/index.js/home/box/agent-data/workflows