The postinstall hook modifies existing kimi command shims during global installation, including unlinking matches. This is a real destructive-action risk, though the scan is marker-based and limited to global installs, so the evidence supports a warning rather than a malicious verdict.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
Installing nori-code globally through a supported package manager, when matching Python `kimi` shims are found and the new command is reachable.
Impact
This can remove existing `kimi` command entries and change which CLI runs, without a clear request to modify that separate command.
Mechanism
The hook scans PATH entries for executable `kimi` files containing the `kimi_cli` marker, renames the first actionable shim to `kimi-legacy`, and may unlink additional matches.
Evidence
package.jsonscripts/postinstall.mjsscripts/postinstall/migrate.mjsPATH entries named `kimi` or `kimi-legacy`