The default startup path silently installs and executes a newer release without an explicit update request, creating a meaningful supply-chain risk. The update targets the package itself, so the source does not establish a malicious payload or justify blocking it as malware.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
CLI startup when at least an hour has passed since the previous check and a different latest version is available.
Impact
Newly fetched package code runs with the user's privileges and can replace the global CLI installation.
Mechanism
It checks npm for the latest version, runs a global npm install, then re-executes the original command.
Evidence
dist/index.jsdist/lib/auto-update.js~/.itznexus/last-update-checkglobal npm installation of @itznexus/itznexus-cli
Network endpoints1
npm registry selected by npm configuration