The package has no install lifecycle hook; its manifest exposes a CLI launcher. On invocation, the launcher fetches a platform binary from the project’s versioned GitHub release and runs it, which is consistent with the package’s bootstrap purpose. No concrete attack behavior was found in the inspected source.
Static reason
No blocking static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
A user invokes the apex command and the binary is not already present in the user’s Apex directory.
Impact
The launcher installs and runs the CLI’s remote release binary; inspected source did not establish an unrelated recipient, credential collection, or other attack behavior.
Mechanism
The launcher downloads the platform-specific binary from the matching versioned GitHub release, stores it under the user’s home directory, and starts it with the supplied command-line arguments.
Evidence
~/.apex/bin/apex~/.apex/natives/16.3.6/pi_natives.win32-x64-baseline.node~/.apex/apex-verify