The inspected entrypoint acts as a user-invoked launcher for a package-aligned release binary, with no source evidence of a concrete attack. Because it executes an unverified remote binary and the configured release version differs from the package version, warn about the unresolved payload trust risk rather than blocking.
Static reason
One or more suspicious static signals were detected.
Trigger
Running the `apex` command when its cached binary is absent.
Impact
The release binary can run with the invoking user's permissions; the launcher source does not verify its signature or hash.
Mechanism
The launcher downloads the platform-specific release asset over HTTPS, stores it in the user's home directory, then starts it with the original arguments and environment.
Evidence
apex.cjs~/.apex/bin/apex~/.apex/bin/apex.exe
Network endpoints1
github.com/Apex-Accelerator/apexcli/releases/download/