The reachable postinstall path configures the package’s Chrome bridge automatically, which is an agent integration lifecycle risk. Its cleanup also trusts manifest-supplied deletion paths; the evidence supports a warning, not 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
Trigger
Package installation runs the postinstall hook.
Impact
Installation can change browser integration settings without a separate command. A crafted or corrupted legacy manifest could also cause deletion outside the intended commands directory.
Mechanism
The hook starts scripts in parallel; setup registers the Chrome Native Messaging host, while cleanup trusts paths from a home-directory manifest when deleting files.
Evidence
package.jsonscripts/setup-chrome-mcp.mjs.lpm-dependency-evidence-aed07062-6c0b-4de3-8dda-e46ce592428c/0/npm-linux/dist/scripts/utils.jsscripts/cleanup-cosknow.mjsscripts/postinstall.cjs~/.claude/commands~/.costrict/commands