The source schedules a global self-update check automatically on CLI exit; when npm reports a newer release, it installs that release globally. This is a meaningful automatic code replacement risk, but the evidence does not establish a malicious payload, so downgrade to warn.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
On CLI process exit, when installed in the detected global node_modules path and the update check is due.
Impact
The executable may change without a separate update command, so a future package release can run under the user's account.
Mechanism
A detached worker queries npm for the latest version and, if newer, installs it globally.
Evidence
dist/index.cjs~/.cache/neta-cli/self-update.json~/.cache/neta-cli/self-update.lock/tmp/neta-cli-install.lock
Network endpoints2
api.cohub.liveapi-dev.cohub.live