The earlier review correctly identified a reachable background self-update, and the source confirms the update is for HyperFrames itself from npm. The current self-update rule makes this warning-only because HYPERFRAMES_NO_AUTO_INSTALL=1 disables it, so the earlier remote-code-execution block does not apply.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Ordinary CLI startup launches a background update check; a later ordinary CLI invocation can schedule installation when the cached version is newer.
Impact
The installed CLI can change without an explicit upgrade command. Under the current self-update rule, an update of the same package from npm with an off-switch is suspicious, even if the notice comes after installation.
Mechanism
A detached process invokes the detected package manager to install a newer HyperFrames version globally. HYPERFRAMES_NO_AUTO_INSTALL=1 disables the install.
Evidence
dist/cli.jsdist/backgroundChecks-LWPXRQOH.jsdist/backgroundChecksWorker.jsdist/autoUpdate-7DNCFECS.jsdist/chunk-TXYE5K6Y.jsHyperFrames user config (update state)global HyperFrames installation