The package’s dependency automatically registers the package’s own MCP servers in project-level agent configs during installation, which is an agent extension lifecycle risk. The inspected code preserves existing settings and shows no broader agent control changes or data transmission from this setup.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
Package installation, through the @threenative/core dependency’s postinstall hook.
Impact
Configured coding agents can access ThreeNative tools without a separate setup request.
Mechanism
The hook adds ThreeNative MCP entries to project-scoped configuration files by default; THREENATIVE_SKIP_MCP_SETUP disables this behavior.
Evidence
package.jsonscripts/install-prebuilt.mjs.lpm-dependency-evidence-051d62c0-fb84-4954-be62-23014c4b8bc2/1/npm-linux/scripts/postinstall.mjs.lpm-dependency-evidence-051d62c0-fb84-4954-be62-23014c4b8bc2/1/npm-linux/scripts/ensure-mcp.mjs.lpm-dependency-evidence-051d62c0-fb84-4954-be62-23014c4b8bc2/1/npm-linux/mcp/install.mjs