@chemx/create-chemx@26.9.11-631
Chemical X Protocol: Private drop-in architecture starter kit and capsule generator
AI Security Review
scanned 1mo ago · by lpm-firewall-aiNo install lifecycle hook or automatic payload execution was found, so the package does not meet the blocking install-hook policy. The unchecked remote file writer is nevertheless a concrete unresolved supply-chain risk.
Static reason
No blocking static signals were detected.; source closely matched a different package identity; previous stored version diff introduced dangerous source
Trigger
Running the create or init CLI command with a license key.
Impact
A compromised service could supply paths or content that overwrite files outside the intended project directory or stage malicious project files.
Mechanism
Remote file-map download followed by unchecked filesystem writes.
AI rationale
No install lifecycle hook or automatic payload execution was found, so the package does not meet the blocking install-hook policy. The unchecked remote file writer is nevertheless a concrete unresolved supply-chain risk.
Evidence
cli/license.jscli/scaffold.js.chemical-x/config.json.chemical-x/device_id<targetDir>/<server-supplied relPath><targetDir>/.cursorrules
Network endpoints2
chemicalx.xophz.com/api/starter-kit/downloadapi.github.com/graphql
Decision evidence
public snapshotAI called this Suspicious at 96.0% confidence as Unknown with low false-positive risk.
Evidence for warning
- The explicit scaffolding command fetches a server-controlled file map and writes each returned path without path validation or integrity checking.
- The scaffold creates a Cursor rules file in the generated project.
- The optional audit-sharing feature can use a GitHub token to post to GitHub GraphQL.
- Git and browser subprocess calls use fixed executable names and argument arrays.
Evidence against
- package.json exposes CLI entry points and contains no preinstall, install, or postinstall hook.
- Network download, project writes, token use, and sharing are reached through user-invoked CLI features, not package installation.
- No source evidence of secret harvesting, shell interpolation, or automatic execution of downloaded files.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
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
9} else if (platform === "win32") {
L10: spawnSync("cmd.exe", ["/c", "start", '""', url], { stdio: "ignore" });
L11: } 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
6 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
HighPackage Source Clone Identity Mismatchcli/audit/social-git.js
HighPrevious Version Dangerous Deltacli/license.js
MediumNetwork
MediumEnvironment Vars
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @chemx/create-chemx@26.9.11-631.
See all versions of @chemx/create-chemx for other recorded verdicts.
- Review the evidence and your use of @chemx/create-chemx@26.9.11-631 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.