chemx@26.9.16-1249
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe automatic install hook makes unconsented behavior-bearing changes to foreign AI-agent control surfaces by registering an executable MCP server. This meets the lifecycle control-hijack block criteria.
Decision evidence
public snapshot- package.json runs cli/postinstall.js automatically on install.
- The postinstall handler targets the consumer install directory and calls installAllMcpConfigs without a consent prompt.
- The installer creates and writes .cursor/mcp.json and .vscode/mcp.json in the consumer project.
- Those MCP entries launch chemx through npx; when an Antigravity config directory exists, the installer also writes its global MCP configuration.
- The Antigravity global configuration is changed only when its config directory already exists.
- The installer merges the named Chemical X MCP entry into the existing configuration.
Source & flagged code
9 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@26.9.16-1249.
See all versions of chemx for other recorded verdicts.
- Avoid installing chemx@26.9.16-1249. 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.