The default startup path silently installs and runs the latest package release, which creates an unrequested remote-code execution risk. The inspected credential flows are explicit connect commands to the configured API, and the update behavior itself does not establish hostile payload intent, so this warrants a warning rather than a block.
Static reason
One or more suspicious static signals were detected.
Trigger
Runs on ordinary CLI startup before command parsing; the update attempt is limited to once per hour.
Impact
New package code may run during a normal CLI invocation without the user choosing to update first.
Mechanism
Queries npm for the latest version, silently runs a global npm install when it differs, and re-executes the original command using the installed code.
Evidence
dist/index.jsdist/lib/auto-update.js~/.itznexus/last-update-checkglobal @itznexus/itznexus-cli installation
Network endpoints1
npm registry (via npm CLI default)