The package’s account credentials are passed through explicit connect commands to its configured API, and no install-time exfiltration was identified. However, every eligible CLI startup can silently install and execute a newer release, which is a meaningful automatic update risk; the source does not establish malicious intent.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Starting the CLI, unless running in development mode, the update check ran within the last hour, or ITZNEXUS_SKIP_UPDATE is set.
Impact
A CLI invocation can replace and execute newer package code without a separate update command or confirmation.
Mechanism
It invokes npm to check the package version and install the latest release globally, records the check time in ~/.itznexus/last-update-check, and re-executes the CLI after an update.
Evidence
dist/index.jsdist/lib/auto-update.js~/.itznexus/last-update-check
Network endpoints2
npm registry selected by npm configurationapi.itznex.us