@chemx/create-chemx@26.10.7-1061
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe automatic postinstall mutates foreign AI-agent control configuration without consent. This meets the policy for blocking an unconsented install-time control-surface mutation.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Installing the package through npm runs its postinstall hook.
Impact
The configured agents can launch the registered MCP server in the consumer's project or global environment.
Mechanism
The hook calls the installer, which writes project-level Cursor and VS Code MCP config and, when available, Antigravity's global MCP config without prompting for consent.
Policy narrative
During npm installation, the postinstall hook registers the package's MCP server in consumer agent configuration without requesting consent. It writes project-level Cursor and VS Code config and may also update Antigravity's global config.
AI rationale
The automatic postinstall mutates foreign AI-agent control configuration without consent. This meets the policy for blocking an unconsented install-time control-surface mutation.
Evidence
package.jsoncli/postinstall.jscli/mcp/installer.js
Decision evidence
public snapshotAI identified this as a dangerous AI-agent capability at 98.0% confidence with low false-positive risk.
Evidence for policy risk
- package.json runs cli/postinstall.js automatically during installation.
- The postinstall resolves the consumer directory and calls installAllMcpConfigs without a consent check.
- The installer writes an MCP server entry into project-level Cursor and VS Code configuration files.
- When the Antigravity config directory exists, the installer also writes its global MCP config and registers a Chemical X server.
Evidence against
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 @chemx/create-chemx@26.10.7-1061.
See all versions of @chemx/create-chemx for other recorded verdicts.
- Avoid installing @chemx/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.