create-chemx@26.10.4-1258
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe npm postinstall hook performs unconsented writes to AI-agent control configuration in the consumer environment. This is a concrete install-time control-surface mutation, so the package should be blocked.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Installing the package through npm runs its postinstall hook.
Impact
Configured AI agents can invoke the package's MCP server from the consumer project.
Mechanism
The hook invokes the MCP installer, which writes server configuration for Cursor and VS Code and may update the existing Antigravity configuration.
Policy narrative
During npm installation, the postinstall hook calls the MCP installer on the consumer directory. The installer writes the package's MCP server entry into Cursor and VS Code configuration and, when Antigravity configuration is present, updates that global configuration as well. These writes occur without an explicit user consent step in the inspected install path.
AI rationale
The npm postinstall hook performs unconsented writes to AI-agent control configuration in the consumer environment. This is a concrete install-time control-surface mutation, so the package should be blocked.
Evidence
package.jsoncli/postinstall.jscli/mcp/installer.js
Decision evidence
public snapshotAI identified this as a dangerous AI-agent capability at 97.0% confidence with low false-positive risk.
Evidence for policy risk
- The package declares a postinstall hook that runs its installer.
- The postinstall handler calls the MCP configuration installer for the consumer directory without asking for consent.
- The installer writes a Chemical X server entry into Cursor and VS Code MCP configuration files.
- When an Antigravity configuration directory exists, the installer also writes its MCP configuration and synchronizes agent schemas.
Evidence against
- The inspected code does not establish credential theft or secret exfiltration.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
11 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node cli/postinstall.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node cli/postinstall.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgcli/errors/errors.spec.jsView file
27patternName = github_pat
severity = critical
line = 27
Critical
Critical Secret
Package contains a critical-looking secret pattern.
cli/errors/errors.spec.jsView on unpkg · L27Findings
3 Critical6 High5 Medium5 Low
CriticalCritical Secretcli/errors/errors.spec.js
CriticalAi Agent Control Hijackcli/mcp/installer.js
CriticalSecret Patterncli/errors/errors.spec.js
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processcli/audit-preflight-git.js
HighShellcli/build/executor.js
HighSame File Env Network Executioncli/license.js
HighTrigger Reachable External Ai Agent Control Surface Mutationcli/pillars-wizard.js
HighSemantic Analysis Limitedcli/audit/ai-slop-detector.js#virtual:normalized:round1
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
Medium
Affected versions and remediation
This report applies to create-chemx@26.10.4-1258.
See all versions of create-chemx for other recorded verdicts.
- Avoid installing create-chemx@26.10.4-1258. 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.