@chem-x/create-chemx@26.10.4-235
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe package automatically changes consumer Cursor and VS Code MCP settings during postinstall, registering an AI-agent server without a separate consent step. This is an unconsented install-time mutation of an agent control surface, supporting a block under the stated policy.
Decision evidence
public snapshot- The package runs cli/postinstall.js automatically after installation.
- The postinstall handler calls installAllMcpConfigs for the consumer directory without a consent check.
- The MCP installer writes a chemical-x server entry into the consumer's Cursor configuration.
- The server command may fall back to npm exec -y -- chemx mcp when no local executable is found.
- The installer and wizard also contain the indicated agent-configuration code; the wizard writes files only when selected pillars exist and the operation is not a dry run.
- The installer test verifies that the MCP configuration creates a chemical-x server entry.
- The package's postinstall excludes installation into its own source directory.
- The available excerpts show an MCP server setup, not credential collection or exfiltration.
Source & flagged code
11 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 @chem-x/create-chemx@26.10.4-235.
See all versions of @chem-x/create-chemx for other recorded verdicts.
- Avoid installing @chem-x/create-chemx@26.10.4-235. 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.