create-chemx@26.9.28-1234
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe active npm postinstall trigger performs unconsented writes to consumer AI-agent control configuration, meeting the policy for blocking an AI-agent control hijack. The package-aligned server identity does not remove the install-time mutation risk.
Decision evidence
public snapshot- package.json runs cli/postinstall.js during installation.
- The postinstall uses INIT_CWD or the process directory as its target and calls installAllMcpConfigs without a consent check.
- installAllMcpConfigs invokes project and Antigravity MCP configuration installers.
- The project installer writes MCP server configuration into consumer .cursor/mcp.json and .vscode/mcp.json.
- When no local ChemX executable is found, the registered server command falls back to npm exec -y -- chemx mcp.
- The registered MCP server is identified as Chemical X and resolves to a local create-chemx executable when present.
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 create-chemx@26.9.28-1234.
See all versions of create-chemx for other recorded verdicts.
- Avoid installing create-chemx@26.9.28-1234. 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.