The obfuscated, automatic update execution path leaves a concrete code execution risk unresolved. The inspected source does not establish a malicious payload, so this warrants a warning rather than a block.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Starting the launcher, which calls its update check before running the requested operation.
Impact
A remotely obtained update may execute code locally; whether the updater validates or restricts that code remains unresolved.
Mechanism
The launcher checks for a newer release and starts a detached Node process with an embedded script; the script’s behavior could not be resolved from the inspected source.