@chem-x/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-aiStatic source confirms an unconsented npm postinstall mutation of project and global AI-agent configuration. The server command is package-aligned, but that does not make the automatic control-surface writes opt-in.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Installing the package through npm, which runs its postinstall hook.
Impact
Agent clients may subsequently launch the registered MCP server from project or global configuration without the consumer having explicitly opted into the registration.
Mechanism
The hook targets the consumer directory and writes MCP configuration for Cursor and VS Code; it also writes global Gemini MCP configuration when that configuration directory exists.
Policy narrative
The package's postinstall hook automatically registers its MCP server in project-level Cursor and VS Code configuration. It also updates global Gemini configuration when that configuration directory exists. These writes happen without a consent prompt, so agent clients may later launch the registered server based on configuration created during dependency installation.
AI rationale
Static source confirms an unconsented npm postinstall mutation of project and global AI-agent configuration. The server command is package-aligned, but that does not make the automatic control-surface writes opt-in.
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 93.0% confidence with low false-positive risk.
Evidence for policy risk
- The package manifest runs cli/postinstall.js during installation.
- The postinstall handler targets the consumer directory and calls the MCP installer without a consent prompt.
- The installer writes MCP configuration into the consumer project's Cursor and VS Code directories.
- If a Gemini config directory already exists, the installer also writes its global MCP configuration.
Evidence against
- The configured MCP command launches the package's own MCP command, locally when available or through npm exec.
- The global Gemini write is guarded by the presence of its configuration directory.
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 @chem-x/create-chemx@26.10.7-1061.
See all versions of @chem-x/create-chemx for other recorded verdicts.
- Avoid installing @chem-x/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.