The install hook triggers first-party agent integration refreshes and a limited shipped-plugin configuration patch, with per-agent prior-install gates. This is a guarded agent integration lifecycle risk, not evidence of a confirmed attack.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A global npm install or upgrade that runs postinstall; the same refresh also runs after an explicit kcap update.
Impact
Previously installed integrations may be refreshed, and canonical MCP commands may be redirected to the resolved native kcap binary.
Mechanism
The hook launches the kcap CLI with per-agent `--if-installed` refresh options and patches canonical MCP command entries in the shipped plugin configuration.
Evidence
package.jsonbin/postinstall.jsbin/refresh.jsbin/kcap.jskcap/.mcp.json