The default startup path can silently replace the global CLI with a newer release, so this warrants a warning for automatic update risk. The source supports a self-update capability, not a confirmed malicious attack.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Running the CLI when its hourly update check is due.
Impact
A newly published release can replace and run as the installed CLI without a separate update command.
Mechanism
The entrypoint checks for updates; if a newer version is available, it runs a global npm install of the latest release and re-executes the command.
Evidence
dist/index.jsdist/lib/auto-update.js