@hs-x/cli@0.4.1
HS-X CLI — init, validate, connect, dev, deploy, promote, rollback, doctor, sync. Installs the `hs-x` command.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe flagged credential flow is not theft of HubSpot or Cloudflare credentials: the request goes to HS-X and uses an HS-X machine secret. However, successful unlinked deployments automatically send project and worker identifiers as runtime telemetry, which is not clearly disclosed, so this warrants a warning rather than a publish block.
Static reason
No blocking static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A successful, explicitly requested unlinked Cloudflare deployment.
Impact
The HS-X service receives identifying deployment metadata as undisclosed runtime telemetry.
Mechanism
Posts a deploy event using a locally generated machine bearer secret; the event includes project ID, deploy ID, environment, and worker URL.
AI rationale
The flagged credential flow is not theft of HubSpot or Cloudflare credentials: the request goes to HS-X and uses an HS-X machine secret. However, successful unlinked deployments automatically send project and worker identifiers as runtime telemetry, which is not clearly disclosed, so this warrants a warning rather than a publish block.
Evidence
dist/commands/deploy.jsdist/machine-id.jsdist/commands/account.jsstatePath('machine-id')statePath('machine-secret')
Network endpoints1
api.hs-x.dev/v1/machines/{machineId}/events
Decision evidence
public snapshotAI called this Suspicious at 89.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The package manifest has no install, preinstall, or postinstall hook; its scripts are build and clean.
- The deploy command requests consent before making mutations.
- After an unlinked Cloudflare deployment succeeds, the command sends a deploy event to the HS-X control plane with project and deployment identifiers and the worker URL.
- The event uses a locally generated machine secret as a bearer token; the default control-plane host is api.hs-x.dev.
- The package describes unlinked deploys as using HubSpot and Cloudflare tokens, and says to log in only for dashboard, deploy history, or team features.
Evidence against
- The network request is tied to an explicit deploy command and successful deployment, not package installation or import.
- The machine secret is generated for HS-X machine events; no discovered HubSpot or Cloudflare credential is sent to an unrelated host.
- Deploy mutations require confirmation or an explicit --yes in non-interactive mode.
Behavioral surface
ChildProcessCrypto
Source & flagged code
6 flaggeddist/dev/compat-shim.jsView file
36const loggerMod = await import('@hubspot/local-dev-lib/logger');
L37: const importRuntime = new Function('specifier', 'return import(specifier)');
L38: const parsing = await importRuntime('@hubspot/project-parsing-lib/translate');
Low
Eval
Package source references a known benign dynamic code generation pattern.
dist/dev/compat-shim.jsView on unpkg · L36dist/dev/invoke.jsView file
174try {
L175: mod = (await import(pathToFileURL(path).href));
L176: }
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/dev/invoke.jsView on unpkg · L174dist/commands/deploy.jsView file
1import { spawn } from 'node:child_process';
L2: import { createHash, randomBytes } from 'node:crypto';
L3: import { lstat, mkdir, readFile, readdir, realpath, rename, rmdir, stat, unlink, writeFile, } from 'node:fs/promises';
L4: import { createServer } from 'node:http';
L5: import { basename, dirname, isAbsolute, join, relative, resolve } from 'node:path';
...
L58: const explicitFlag = resolveFlag(input.argv, '--account-id');
L59: const fromFlag = explicitFlag ?? process.env.HSX_ACCOUNT_ID;
L60: if (fromFlag && fromFlag.length > 0) {
...
L138: }
L139: return { exitCode: 10 };
L140: }
...
L217: headers: { 'content-type': 'application/x-www-form-urlencoded' },
Findings
1 Critical3 High3 Medium5 Low
CriticalPrevious Version Dangerous Deltadist/hubspot-auth.js
HighCredential Exfiltrationdist/commands/deploy.js
HighTrigger Reachable Credential Exfiltrationdist/commands/deploy.js
HighSemantic Analysis Limiteddist/commands/doctor.js#virtual:normalized:round1
MediumDynamic Requiredist/dev/invoke.js
MediumNetwork
MediumEnvironment Vars
LowScripts Present
LowEvaldist/dev/compat-shim.js
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @hs-x/cli@0.4.1.
See all versions of @hs-x/cli for other recorded verdicts.
- Review the evidence and your use of @hs-x/cli@0.4.1 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.