The flagged process execution is a package-specific upgrade flow, gated by an API upgrade-required response and limited to global installs; npm is invoked with scripts ignored. The update check retrieves version metadata, and the reviewed code shows no unrelated collection or concealed payload behavior.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
CLI startup performs the version check; an API upgrade-required response can trigger self-upgrade for an eligible global install.
Impact
The observed behavior supports package updates and normal CLI/API use; no credential or unrelated user data collection was identified.
Mechanism
The version check retrieves package-version metadata. The upgrade path runs npm install for the installed package with lifecycle scripts ignored, then re-executes the CLI.
Evidence
package.jsondist/cli.jsdist/chunk-3H55RUXT.js
Network endpoints3
registry.npmjs.orgapi.infra.oneharness.infra.one