chemx@26.9.24-393
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe automatic postinstall mutates consumer AI-agent control surfaces by registering a runnable MCP server without consent. This meets the lifecycle control-hijack blocking criterion even though the integration aligns with the package's starter-kit purpose.
Decision evidence
public snapshot- package.json runs cli/postinstall.js automatically; that hook targets the consuming project and calls installAllMcpConfigs without a consent check.
- The MCP installer writes a Chemical X server entry into the consumer's Cursor and VS Code configuration files and registers it in Antigravity's global MCP configuration when present.
- The injected server runs this package's MCP command, making the lifecycle mutation an active agent capability rather than inert configuration.
- The separate AGENTS.md installer adds directives steering agent file inspection and command choices; its installer is also available through the interactive wizard.
- The package presents itself as a starter kit, and the MCP server setup is consistent with that product function.
- The pillars wizard asks the user to select agent steering configuration, but that prompt does not guard the automatic postinstall MCP changes.
Source & flagged code
10 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgPackage contains a critical-looking secret pattern.
cli/errors/errors.spec.jsView on unpkg · L27Findings
Affected versions and remediation
This report applies to chemx@26.9.24-393.
See all versions of chemx for other recorded verdicts.
- Avoid installing chemx@26.9.24-393. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.