@chemx/starter-kit@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 configuration and registers an executable MCP server without a consent guard. This is an unconsented install-time control-surface change, so it meets the blocking policy.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Installing the package through npm triggers its postinstall script.
Impact
Configured agents can invoke the package’s MCP command in consumer projects after installation.
Mechanism
The hook calls the installer, which merges a Chemical X server entry into Cursor and VS Code project configs and an existing Antigravity user config.
Policy narrative
An npm installation runs the postinstall handler, which automatically registers the package’s MCP server in consumer agent configuration. The installer writes project-level Cursor and VS Code files and may also update the user’s Antigravity configuration, enabling those agents to invoke the package without a separate consent step.
AI rationale
The automatic postinstall mutates foreign AI-agent configuration and registers an executable MCP server without a consent guard. This is an unconsented install-time control-surface change, so it meets the blocking policy.
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 98.0% confidence with low false-positive risk.
Evidence for policy risk
- The package runs cli/postinstall.js automatically after installation.
- The postinstall handler calls installAllMcpConfigs for the consumer project without a consent check.
- The installer writes MCP server configuration into the consumer’s Cursor and VS Code project files and, when present, the user’s Antigravity configuration.
- The configured server can run the package’s MCP command, creating an agent control surface as an install-time side effect.
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/starter-kit@26.10.7-1061.
See all versions of @chemx/starter-kit for other recorded verdicts.
- Avoid installing @chemx/starter-kit@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.