@catalyst-cloud/cli@0.16.44
Set up Catalyst Cloud, check your tickets and manage your account from the command line.
AI Security Review
scanned 4d ago · by lpm-firewall-aiRunner custody failures trigger telemetry containing the machine hostname, sent to the configured Catalyst service. The request is scoped to the saved account and matching onboarding journal, so this is a warning-level telemetry concern rather than credential exfiltration.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A user-run runner onboarding flow refuses custody; the event is attempted unless the operation is aborted.
Impact
The configured Catalyst service receives identifying host information and onboarding failure metadata.
Mechanism
The CLI uses the saved Catalyst login to mint a short-lived telemetry token, then posts an event containing host.name and failure details.
AI rationale
Runner custody failures trigger telemetry containing the machine hostname, sent to the configured Catalyst service. The request is scoped to the saved account and matching onboarding journal, so this is a warning-level telemetry concern rather than credential exfiltration.
Evidence
dist/onboard-runner.jsdist/onboard-runner-telemetry.js
Network endpoints2
Configured Catalyst base URL: /api/v1/telemetry/tokenConfigured Catalyst base URL: /api/v1/telemetry/v1/logs
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- Runner setup sends a custody failure event when it refuses custody.
- The event includes the machine hostname and onboarding failure details.
- Telemetry is sent only when the saved Catalyst account, membership, and base URL match the onboarding journal.
Evidence against
- The postinstall updater runs only for global installs and can be disabled with CATALYST_NO_AGENT_REPOINT=1.
- The updater skips unrecognized agents and agents already on an equal or newer Catalyst CLI.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
9 flaggedpackage.jsonView file
•scripts.postinstall = node bin/postinstall.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node bin/postinstall.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgbin/launch.jsView file
61const noticeLast = deprecated && !noticeFirst;
L62: import("../dist/cli.js")
L63: .then((m) => m.main(argv))
Medium
Dynamic Require
Package source references dynamic require/import behavior.
bin/launch.jsView on unpkg · L61Findings
1 Critical4 High7 Medium5 Low
CriticalAi Agent Control Hijackdist/agent-repoint.js
HighInstall Time Lifecycle Scriptspackage.json
HighTrigger Reachable Persistencedist/agent-repoint.js
HighSemantic Analysis Limiteddist/codex-env.js#virtual:string-array:round1
HighPrevious Version Dangerous Deltadist/onboard-runner.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Requirebin/launch.js
MediumNetwork
MediumEnvironment Vars
MediumInstall Persistencedist/codex-attribution.js
MediumShips Build Helpervendor/self-host/host-disk-sample.py
MediumStructural Risk Force Deep Review
Affected versions and remediation
This report applies to @catalyst-cloud/cli@0.16.44.
See all versions of @catalyst-cloud/cli for other recorded verdicts.
- Review the evidence and your use of @catalyst-cloud/cli@0.16.44 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.