registry / AI-agent control-surface risk / create-chemx
create-chemx
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
This report shows the evidence for create-chemx@26.10.7-1061. 18 of 42 known versions are blocked or flagged. The newest version, 26.10.19-530, is allowed. See all versions.
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe package automatically mutates project and conditional global AI-agent configuration during npm postinstall without a consent gate. This meets the policy for blocking unconsented install-time mutation of a foreign or broad AI-agent control surface.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Installing create-chemx through npm outside its own source directory.
Impact
Agents may receive a newly registered MCP server in project or global configuration as a side effect of package installation.
Mechanism
The hook calls an installer that writes Cursor and VS Code project MCP configuration and may write Antigravity's global MCP configuration, without an explicit consent gate.
Policy narrative
On npm installation, `postinstall` runs `cli/postinstall.js`, which calls `installAllMcpConfigs` for the consumer directory. The installer writes MCP server entries to Cursor and VS Code project files and, when Antigravity's config directory exists, its global MCP configuration. No consent prompt guards these writes, so this is unconsented install-time modification of AI-agent control configuration.
AI rationale
The package automatically mutates project and conditional global AI-agent configuration during npm postinstall without a consent gate. This meets the policy for blocking unconsented install-time mutation of a foreign or broad AI-agent control surface.
Evidence
package.jsoncli/postinstall.jscli/mcp/installer.js.cursor/mcp.json.vscode/mcp.json~/.gemini/config/mcp_config.json
Decision evidence
public snapshotAI identified this as a dangerous AI-agent capability at 96.0% confidence with low false-positive risk.
Evidence for policy risk
- The npm postinstall hook invokes the MCP installer for the consumer project without a consent check.
- The installer writes MCP server configuration into the consumer project's Cursor and VS Code configuration files.
- The installer also writes Antigravity's global MCP configuration when its config directory exists.
- The registered MCP server can be invoked through a project-local package path or an npm exec fallback.
Evidence against
- The installer registers this package's named Chemical X MCP server and preserves existing configuration fields.
- No credential collection or exfiltration is established by the inspected installer behavior.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
8 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/audit-preflight-git.jsView file
1import fs from 'node:fs';
L2: import { spawnSync } from 'node:child_process';
L3:
High
Child Process
Package source references child process execution.
cli/audit-preflight-git.jsView on unpkg · L1Findings
1 Critical5 High5 Medium5 Low
CriticalAi Agent Control Hijackcli/mcp/installer.js
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processcli/audit-preflight-git.js
HighShellcli/build/executor.js
HighSame File Env Network Executioncli/license.js
HighSemantic Analysis Limitedcli/audit/ai-slop-detector.js#virtual:normalized:round1
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperscripts/pre-commit.sh
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
Affected versions and remediation
This report applies to create-chemx@26.10.7-1061.
The versions list below shows the verdict for each recorded version.
- Avoid installing create-chemx@26.10.7-1061. 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.