@chem-x/create-chemx@26.9.20-1298
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe postinstall-triggered writes to multiple AI agent configuration surfaces are unconsented lifecycle mutations. This meets the blocking policy for AI agent control-surface hijacking, although the configured server is package-aligned and the inspected source does not establish credential theft.
Decision evidence
public snapshot- The package defines a postinstall hook that runs its installer.
- The hook calls MCP setup for the installing project without a consent check.
- MCP setup writes configuration for Cursor and VS Code, and adds a server entry to an existing global Antigravity configuration when that configuration directory exists.
- The setup adds a package-aligned Chemical X MCP server entry; inspected code does not show credential collection or unrelated data transmission.
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 @chem-x/create-chemx@26.9.20-1298.
See all versions of @chem-x/create-chemx for other recorded verdicts.
- Avoid installing @chem-x/create-chemx@26.9.20-1298. 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.