The flagged reverse-shell and metadata hits are defensive detection and blocking logic. The automatic setup and npm token use serve the CLI’s browser and package-update functions, with the token sent to the configured npm registry.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
npm postinstall, CLI startup, or an explicit CLI command.
Impact
No malicious impact identified. Setup may repair the browser sandbox, and startup may update the CLI from its package registry.
Mechanism
Postinstall normalizes node-pty files and repairs the Electron Chrome sandbox helper when needed. The CLI sends an npm token to the configured package registry for its version check; the flagged metadata address is blocked by endpoint validation, and reverse-shell matches are detector rules.
Network endpoints2
registry.npmjs.orglocalhost