registry / @catalyst-cloud/cli / 0.16.42
@catalyst-cloud/cli@0.16.42
Set up Catalyst Cloud, check your tickets and manage your account from the command line.
AI Security Review
scanned 8d ago · by lpm-firewall-aiAlthough the package has a postinstall hook, it is limited to global installs and a narrowly recognized Catalyst runner updater. The inspected behavior is a same-product updater migration, and the remaining flagged runtime paths show no concrete attack surface.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A global npm install, unless CATALYST_NO_AGENT_REPOINT is set to 1.
Impact
The runner's existing scheduled updates continue through the newer CLI. No unrelated agent configuration or credential transfer was identified.
Mechanism
The hook recognizes the Catalyst runner scheduler and updates it only when its CLI is older or missing; it preserves a backup and checks write access.
AI rationale
Although the package has a postinstall hook, it is limited to global installs and a narrowly recognized Catalyst runner updater. The inspected behavior is a same-product updater migration, and the remaining flagged runtime paths show no concrete attack surface.
Evidence
bin/postinstall.jsdist/agent-repoint.jsdist/runner-auto-update.js
Decision evidence
public snapshotAI called this Clean at 88.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The postinstall hook runs only for global installs and can be disabled; it attempts a runner-agent repoint.
- The repoint logic recognizes Catalyst runner update agents and skips agents already using this install and runtime; it only replaces an older Catalyst CLI and checks write access.
- Inspected credential-related runtime paths use local account identity and configured Catalyst service destinations for their intended telemetry, onboarding, or attribution operations.
- Repository agent setup is dispatched as an explicit CLI command, and the cloud plugin updater rejects scopes other than user scope.
- The inspected SDK and formatting dependency source serves client, string-width, and ANSI-wrapping functions.
- The runner updater consumes an approved release, while replica commands are an optional local feature; no concrete attack behavior was identified.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystem
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/runner-update.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.42.
See all versions of @catalyst-cloud/cli for other recorded verdicts.
- Review the evidence and your use of @catalyst-cloud/cli@0.16.42 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.