The flagged process and network behavior supports CLI version checks and an upgrade response to the service’s HTTP 426 requirement. I found no unrelated credential flow, install-time behavior, or other concrete attack.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
CLI startup checks for an available version; self-upgrade is considered after an API HTTP 426 response.
Impact
The reviewed behavior is consistent with the CLI’s update and service-client functions; no unrelated collection, credential forwarding, or harmful action was found.
Mechanism
The version check retrieves version metadata from the npm registry. The upgrade helper is restricted to global installs and installs the CLI package with npm; API credentials are sent in requests to the configured service base URL.
Network endpoints2
registry.npmjs.orgharness.infra.one