The CLI automatically installs and re-executes its latest npm release on startup without an approval prompt, creating a meaningful software update risk. The reviewed credential flows are command-triggered and target the configured API; no concrete malicious behavior was found.
Static reason
One or more suspicious static signals were detected.
Trigger
Running the CLI entry point, unless it is a development install or the internal re-execution skip flag is set.
Impact
Updates and executes newly fetched CLI code without an approval prompt, which is a user-visible software update risk.
Mechanism
Checks the package version through npm and runs npm install -g @itznexus/itznexus-cli@latest when it differs, then re-executes the CLI.
Evidence
dist/index.jsdist/lib/auto-update.js~/.itznexus/last-update-checkglobally installed @itznexus/itznexus-cli
Network endpoints2
npm registry, accessed via npm view/npm install; host is not hard-codedapi.itznex.us