The automatic user-profile registration warrants a warning for agent extension lifecycle risk, though the reviewed behavior is package-aligned bridge setup rather than a confirmed attack. Offline analysis also leaves bundled native artifacts unresolved, which limits assurance but does not establish malicious behavior.
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
The Chrome extension can connect to the installed local bridge host without a separate user-invoked registration command.
Mechanism
The setup script invokes the bridge’s Chrome registration command, which writes a Native Messaging manifest for the bridge and its specific extension ID.
Evidence
package.jsonscripts/setup-chrome-mcp.mjs.lpm-dependency-evidence-69c6ea90-89ee-4820-a9fe-146209bf88d3/2/npm-linux/dist/cli.js.lpm-dependency-evidence-69c6ea90-89ee-4820-a9fe-146209bf88d3/2/npm-linux/dist/scripts/utils.js.lpm-dependency-evidence-69c6ea90-89ee-4820-a9fe-146209bf88d3/2/npm-linux/dist/scripts/browser-config.js