create-chemx@26.9.12-272
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis is a concrete arbitrary-file-write supply-chain vulnerability in an explicit user command, not an automatic install-time attack. No lifecycle hook or confirmed secret exfiltration was found.
Static reason
No blocking static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The user runs create-chemx or chemx init with a license key.
Impact
A remote service can overwrite accessible local files or place a staged payload outside the intended project.
Mechanism
Unchecked remote file paths are joined to a local target and written.
AI rationale
This is a concrete arbitrary-file-write supply-chain vulnerability in an explicit user command, not an automatic install-time attack. No lifecycle hook or confirmed secret exfiltration was found.
Evidence
cli/license.jscli/scaffold.js<scaffold-target>/<server-supplied relPath>src/chemical-x/<server-supplied relPath>
Network endpoints1
chemicalx.xophz.com/api/starter-kit/download
Decision evidence
public snapshotAI called this Suspicious at 93.0% confidence as Critical Vulnerability with low false-positive risk.
Evidence for warning
- The scaffold downloads a server-supplied file map and writes every supplied path without validating that it remains inside the chosen project directory.
- The same unchecked write loop is reachable through the init command, whose default target is inside the current project.
- The remote response can therefore overwrite or create files outside the intended target through traversal paths.
Evidence against
- package.json has no preinstall, install, or postinstall hook.
- The download and writes occur only after an explicit create or init command and license flow.
- Git hooks, CI workflow setup, and GitHub discussion publishing are explicit interactive commands.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
5 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" });
L12: } else {
High
cli/license.jsView file
3import os from 'node:os';
L4: import { spawnSync } from 'node:child_process';
L5: import {
...
L16:
L17: export const API_BASE = process.env.CHEMICAL_X_API_URL || 'https://chemicalx.xophz.com';
L18: export const URL_LEARN = 'https://chemicalx.xophz.com';
Findings
5 High2 Medium5 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/audit/social-git.js
MediumNetwork
MediumEnvironment Vars
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to create-chemx@26.9.12-272.
See all versions of create-chemx for other recorded verdicts.
- Review the evidence and your use of create-chemx@26.9.12-272 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.