The automatic postinstall mutates agent configuration and the cleanup trusts paths from a local manifest, creating unresolved destructive risk. The inspected behavior does not establish broader malicious activity, so this warrants a warning rather than a block.
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
Trigger
Installing the package through npm or another package manager that runs postinstall.
Impact
Agent configuration is changed during installation; a crafted pre-existing manifest could cause deletion of files outside the intended command directory.
Mechanism
The postinstall launcher runs Chrome MCP setup and CosKnow cleanup. Cleanup processes manifest-listed paths and removes files, then deletes selected legacy command files and resources.
Evidence
package.jsonscripts/setup-chrome-mcp.mjsscripts/cleanup-cosknow.mjs~/.claude/commands~/.costrict/commands