chemx@26.9.26-253
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe install lifecycle automatically writes an active MCP server entry into consumer agent configuration without consent. This is an unconsented install-time mutation of a foreign AI-agent control surface.
Decision evidence
public snapshot- The package runs cli/postinstall.js during installation, and that hook automatically invokes the MCP installer for the consumer directory.
- The MCP installer registers a server command and merges it into project Cursor and VS Code configuration files during postinstall, without a consent check.
- If no local Chemx executable is found, the registered server command uses npm exec to fetch and run chemx.
- The hook skips when the target directory is the package's own starter kit.
- The installer preserves existing MCP configuration while adding the Chemical X server entry.
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 chemx@26.9.26-253.
See all versions of chemx for other recorded verdicts.
- Avoid installing chemx@26.9.26-253. 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.