The earlier review correctly identified a reachable startup self-update: it checks registry.npmjs.org and installs a newer release. The current rules classify self-updates from npm with an off-switch as suspicious, so I downgrade the prior block; the login and metadata hints do not establish separate attacks.
Static reason
One or more suspicious static signals were detected.
Trigger
CLI startup; the update check is at most daily and runs only for an eligible global npm installation.
Impact
The installed CLI may be replaced with a newer release without a separate update command. Under the current rules, an npm self-update with an off-switch is suspicious, not a publish-blocking remote-code-execution finding.
Mechanism
A detached worker checks the npm dist-tags endpoint and invokes npm to install a newer @oxygen-agent/cli version. The update can be turned off with oxygen update --disable-auto or OXYGEN_NO_AUTO_UPDATE=1.
Evidence
dist/index.jsdist/auto-update.jsdist/cli-install.jsupdate-state.jsonglobal @oxygen-agent/cli installation