The download and execution happen when users run the CLI, and the runner appears to be the package’s own tool fetched from its vendor’s subdomain. This does not meet the block rule for unrelated or concealed payloads, though the plain HTTP transfer presents a real code-substitution risk.
Static reason
One or more suspicious static signals were detected.
Trigger
Running the `estra7ah` CLI when its runner is absent, or when the remote version differs from the local version.
Impact
An on-path attacker could replace the downloaded executable and run code with the user’s privileges.
Mechanism
Fetches the runner from `http://premium.yetech.co:80`, saves it beside the launcher, then spawns it with the user’s arguments.
Evidence
dist/estra7ah.jspackage.json<launcher directory>/__runnerversion<launcher directory>/runner-win-x64.exe<launcher directory>/runner-linux-x64<launcher directory>/runner-linux-arm64<launcher directory>/runner-linux-armv7