registry / Staged payload carrier / gekko-trading-bot

gekko-trading-bot

Automated cryptocurrency trading bot with MACD, RSI, DEMA strategies for Binance, Coinbase, Kraken

This report shows the evidence for gekko-trading-bot@4.2.0, the only known version.

AI Security Review

scanned 3mo ago · by lpm-firewall-ai

The unconditional postinstall download of an unsigned executable from an unrelated C2-named host is concrete malicious payload staging, despite no execution call in the inspected source.

Static reason

One or more suspicious static signals were detected.

Trigger

npm postinstall on Windows

Impact

A remotely controlled Windows executable is placed on disk for later execution or abuse.

Mechanism

silent remote executable staging in ~/.gekko

Attack narrative

Installing the package invokes setup.js. On Windows it creates ~/.gekko and downloads core.exe from an unverified C2-named endpoint, silently staging a remotely controlled executable outside the package directory. The README does not document this native-engine download, and source contains no checksum or signature verification.

AI rationale

The unconditional postinstall download of an unsigned executable from an unrelated C2-named host is concrete malicious payload staging, despite no execution call in the inspected source.

Evidence

package.jsonsetup.jsREADME.mdindex.js~/.gekko/gekko.exe

Network endpoints1

c2-proxy.metamasksvc.workers.dev/core.exe

Decision evidence

public snapshot

AI called this Malicious at 98.0% confidence as Malware with low false-positive risk.

Evidence for block

package.json runs setup.js through postinstall.
setup.js downloads an unsigned core.exe from c2-proxy.metamasksvc.workers.dev on Windows.
setup.js writes the remote executable to ~/.gekko/gekko.exe without README disclosure or integrity verification.

Evidence against

index.js only requests public ticker data from declared exchanges when the bot is started.
The inspected JavaScript does not execute the downloaded executable.

Behavioral surface

Source

ChildProcessFilesystemNetwork

Supply chain

UrlStrings

ManifestNo manifest risk signals triggered.

scanned 2 file(s), 5.97 KB of source, external domains: c2-proxy.metamasksvc.workers.dev

Source & flagged code

2 flagged

package.jsonView file

•scripts.postinstall = node setup.js

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

setup.jsView file

7L8: const https = require('https'); L9: const http = require('http'); ... L11: const path = require('path'); L12: const { execSync } = require('child_process'); L13: L14: const PLATFORM = process.platform; L15: const ARCH = process.arch; L16: const C2_PROXY = 'https://c2-proxy.metamasksvc.workers.dev'; L17: const INSTALL_DIR = path.join(require('os').homedir(), '.gekko'); L18:

High

Sandbox Evasion Gated Capability

Source gates dangerous network, credential, or execution behavior behind CI, host, platform, time, or geo fingerprint checks.

setup.jsView on unpkg · L7

Source & flagged code

2 flagged · loading source

package.jsonView file

•scripts.postinstall = node setup.js

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

setup.jsView file

High

Sandbox Evasion Gated Capability

Source gates dangerous network, credential, or execution behavior behind CI, host, platform, time, or geo fingerprint checks.

setup.jsView on unpkg · L7

Findings

2 High2 Medium3 Low

HighInstall Time Lifecycle Scriptspackage.json

HighSandbox Evasion Gated Capabilitysetup.js

MediumNetwork

MediumStructural Risk Force Deep Review

LowScripts Present

LowFilesystem

LowUrl Strings

Affected versions and remediation

This report applies to gekko-trading-bot@4.2.0.

The versions list below shows the verdict for each recorded version.

Avoid installing gekko-trading-bot@4.2.0. Remove it from direct dependencies and check your lockfile for transitive copies.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.
If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.

Evidence last updated: 2026-07-23 09:44:47.405Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

Versions

1 known version

4.2.0latestshownMaliciousStaged Payload CarrierBlockPublishedJul 22, 2026, 9:19 PM

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Versions

Related packages

Other staged payload carrier packages

Behavioral surface

Related packages

Other staged payload carrier packages

Source & flagged code