@chemx/create-chemx@26.9.17-309
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe package has a verified npm postinstall trigger that mutates consumer AI-agent control configuration without consent, which meets the blocking policy for lifecycle-time control-surface mutation. The source supports the configuration hijack finding but does not establish credential theft or malicious intent beyond that behavior.
Decision evidence
public snapshot- The package manifest runs `cli/postinstall.js` automatically during installation.
- The postinstall targets the consumer directory and calls the MCP installer without a consent check.
- The MCP installer creates or overwrites the consumer’s `.cursor/mcp.json` to register a server.
- The installer also targets `.vscode/mcp.json` and, when present, Antigravity’s global MCP configuration.
- The required installer location adds instructions to AGENTS.md that direct AI agents to use the package’s search command.
- The package and installer identify the MCP registration as Chemical X setup, and the installer merges the named server entry into the configuration.
- The package’s test verifies that project MCP configuration and a helper script are written; this corroborates the behavior but does not provide install-time consent.
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 source references child process execution.
cli/audit-preflight-git.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @chemx/create-chemx@26.9.17-309.
See all versions of @chemx/create-chemx for other recorded verdicts.
- Avoid installing @chemx/create-chemx@26.9.17-309. 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.