No lifecycle script executes on npm install, and the risky configuration occurs through the interactive CLI. The package nevertheless broadens AI-agent execution and mutates user-level agent configuration, so it warrants a warning rather than a block.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
User runs the CLI, completes its configuration prompt, or runs migrate/sync actions.
Impact
Configured agent sessions may execute bundled hooks and run with reduced approval prompts.
Mechanism
Agent configuration and hook deployment with permissive agent launch options.
Evidence
package.jsondist/index.jsdist/setup.jsdist/installer.jsdist/targets/hooks-export.jsdist/targets/grok-user-config.js.claude/settings.json.claude/hooks/*.ts.kimi-code/local.toml~/.kimi-code/config.toml.grok/hooks/svs.json~/.grok/config.toml