@hs-x/cli@0.4.12
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 package’s deployment flow sends identifying project and worker metadata to the vendor control plane as runtime telemetry, beyond the fields described by its telemetry notice. The event is tied to a user-confirmed deploy and uses an HS-X machine credential, so this is a warning-level telemetry concern rather than credential exfiltration.
Static reason
No blocking static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user runs a mutating deploy that successfully deploys a Cloudflare worker; plan and dry-run paths do not send this event.
Impact
HS-X receives deployment and project metadata associated with the machine identity. No credential theft or unrelated-host transfer was identified.
Mechanism
The CLI POSTs an event authenticated with its HS-X machine secret. The payload includes project and deploy identifiers, environment, and worker URL. The event-specific fields are not covered by the inspected CLI telemetry notice or its opt-out controls.
AI rationale
The package’s deployment flow sends identifying project and worker metadata to the vendor control plane as runtime telemetry, beyond the fields described by its telemetry notice. The event is tied to a user-confirmed deploy and uses an HS-X machine credential, so this is a warning-level telemetry concern rather than credential exfiltration.
Evidence
dist/commands/deploy.jsdist/machine-id.jsdist/telemetry.js
Network endpoints1
api.hs-x.dev/v1/machines/{machineId}/events (default control plane; configurable)
Decision evidence
public snapshotAI called this Suspicious at 88.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- After a successful, non-dry-run unlinked Cloudflare deployment, the CLI sends a deploy event.
- The event is POSTed to the configured HS-X control plane and authenticated with the machine secret.
- The event includes project and deploy identifiers, environment, and the deployed worker URL.
- The event uses an HS-X machine secret described as a local bearer capability.
Evidence against
- The event only runs after a user-triggered deployment succeeds; deploy mutations require consent or --yes.
- The machine secret is generated and stored locally for pre-link HS-X machine events; the inspected flow does not send a HubSpot or Cloudflare credential to a foreign host.
- The CLI discloses and provides opt-outs for its separate, basic command telemetry, but that notice does not describe the deploy event’s identifying fields.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
Source & flagged code
6 flaggeddist/dev/compat-shim.jsView file
67export async function loadDevStack() {
L68: const portManager = await import('@hubspot/local-dev-lib/portManager');
L69: const config = await import('@hubspot/local-dev-lib/config');
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/dev/compat-shim.jsView on unpkg · L6771const loggerMod = await import('@hubspot/local-dev-lib/logger');
L72: const importRuntime = new Function('specifier', 'return import(specifier)');
L73: 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 · L71dist/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';
...
L64: const explicitFlag = resolveFlag(input.argv, '--account-id');
L65: const fromFlag = explicitFlag ?? process.env.HSX_ACCOUNT_ID;
L66: if (fromFlag && fromFlag.length > 0) {
...
L144: }
L145: return { exitCode: 10 };
L146: }
...
L244: 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/compat-shim.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.12.
See all versions of @hs-x/cli for other recorded verdicts.
- Review the evidence and your use of @hs-x/cli@0.4.12 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.