@chem-x/starter-kit@26.9.14-1358
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe installer can change project agent instructions and scripts when a user invokes the setup wizard, so this merits a warning for agent capability abuse. The source inspected does not establish an automatic install-time attack or other concrete malicious behavior.
Static reason
No blocking static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user runs the CLI hooks or setup-ci command and selects the agent query-machine setup option.
Impact
The project’s AI agents may be steered to invoke this package’s search commands, and project scripts may be changed.
Mechanism
The installer appends instructions to AGENTS.md and writes q and search scripts into the target project’s package.json.
AI rationale
The installer can change project agent instructions and scripts when a user invokes the setup wizard, so this merits a warning for agent capability abuse. The source inspected does not establish an automatic install-time attack or other concrete malicious behavior.
Evidence
cli/index.jscli/installer.jsAGENTS.mdpackage.json
Decision evidence
public snapshotAI called this Suspicious at 88.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The manifest exposes the CLI through cli/index.js and defines no install lifecycle hook.
- The explicit hooks/setup-ci command starts an interactive installation wizard.
- The query-machine option adds a directive to AGENTS.md telling AI agents to use the package’s search commands before broad searches.
- The same installer option adds q and search scripts to the consumer project’s package.json.
- License validation sends the supplied license key to the configured Chemical X service; the inspected code does not establish unrelated credential exfiltration.
- The shell calls in the inspected terminal and sharing code support browser opening and interactive prompts.
Evidence against
- Agent configuration changes are reachable through an explicit CLI setup command, not an npm install hook.
- No inspected source established an unconsented broad agent-control write or a concrete malicious attack chain.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetwork
Source & flagged code
6 flagged · loading sourcecli/navigator-share.jsView file
2import path from 'node:path';
L3: import { spawnSync } from 'node:child_process';
L4: import {
High
Child Process
Package source references child process execution.
cli/navigator-share.jsView on unpkg · L2cli/terminal.jsView file
10} else if (platform === "win32") {
L11: spawnSync("cmd.exe", ["/c", "start", '""', url], { stdio: "ignore", timeout: 3000 });
L12: } else {
High
cli/license.jsView file
3import os from 'node:os';
L4: import { spawnSync } from 'node:child_process';
L5: import {
...
L17:
L18: export const API_BASE = process.env.CHEMICAL_X_API_URL || 'https://chemicalx.xophz.com';
L19: export const GATEKEEPER_API_URL = process.env.COMPASS_GATEKEEPER_URL || 'https://mycompassconsulting.com/wp-json/compass/v1/gatekeeper';
Findings
5 High3 Medium4 Low
HighChild Processcli/navigator-share.js
HighShellcli/terminal.js
HighSame File Env Network Executioncli/license.js
HighTrigger Reachable External Ai Agent Control Surface Mutationcli/scaffold.js
HighPrevious Version Dangerous Deltacli/license.js
MediumNetwork
MediumEnvironment Vars
MediumSuspicious Lifecycle Evidencepackage.json
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @chem-x/starter-kit@26.9.14-1358.
See all versions of @chem-x/starter-kit for other recorded verdicts.
- Review the evidence and your use of @chem-x/starter-kit@26.9.14-1358 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.