@chemx/create-chemx@26.9.20-408
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 11d ago · by lpm-firewall-aiSource confirms that an npm postinstall hook automatically writes agent server configuration and, conditionally, global Antigravity schemas and instructions without a consent gate. This is an unconsented lifecycle mutation of broad AI-agent control surfaces, so the package should be blocked.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
Installing the package through npm runs its postinstall hook for a consumer project.
Impact
AI agents may receive a newly registered server and behavior-bearing instructions without the consumer explicitly invoking setup.
Mechanism
The hook calls the MCP installer without a consent prompt. The installer merges a Chemical X server entry into project agent configuration and, when Antigravity is configured, registers a global server and writes tool schemas and instructions.
Policy narrative
During npm installation, the postinstall hook modifies project MCP configuration for Cursor and VS Code without asking for consent. If Antigravity is present, it also registers a global MCP server and writes schemas and instructions. The configuration can launch a local MCP command or fall back to `npx -y chemx mcp`. This creates an unconsented agent control surface through an install hook.
AI rationale
Source confirms that an npm postinstall hook automatically writes agent server configuration and, conditionally, global Antigravity schemas and instructions without a consent gate. This is an unconsented lifecycle mutation of broad AI-agent control surfaces, so the package should be blocked.
Evidence
package.jsoncli/postinstall.jscli/mcp/installer.jscli/mcp/antigravity.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
- package.json defines a postinstall hook that launches cli/postinstall.js; that hook automatically calls installAllMcpConfigs for the consumer directory, with no consent check.
- The lifecycle installer writes MCP server configuration into project-level Cursor and VS Code files, creating those directories when needed.
- When Antigravity configuration exists, the installer registers the server globally and synchronizes MCP schemas and agent instructions under the user home directory.
- The registered server can run the local MCP command or fall back to npx -y chemx mcp; the Antigravity setup also writes behavior-bearing instructions for the agent.
Evidence against
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 Medium4 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/scaffold.js
HighPrevious Version Dangerous Deltacli/license.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
Affected versions and remediation
This report applies to @chemx/create-chemx@26.9.20-408.
See all versions of @chemx/create-chemx for other recorded verdicts.
- Avoid installing @chemx/create-chemx@26.9.20-408. 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.