Source: amazon-inspector (123418539e0264e9d58c8b51976723aff3eceec10520c231d7bc847edd51d691)
The gem's native-extension script ext/perp_funding_rates/extconf.rb contains no real build logic: it declares create_makefile('bitcoin_rpc_lite_native') but ships no C/C++/Rust sources, and the gemspec/library name (perp-funding-rates / PerpFundingRates) does not match the README (bitcoin-rpc-lite) — the extension exists solely to execute code at install time. During gem install, extconf.rb base64-decodes a Ruby payload and eval()s it inside a double-forked, detached, delayed child process. The decoded payload opens a TCP socket to the hardcoded bare-IP C2 at 45.138.12.177:8089 and bridges it to /bin/sh, giving the operator an interactive shell on the installer's machine. Execution is gated by sandbox/CI/user/path/uptime heuristics and only triggers when developer-signal files such as ~/.ssh, ~/.gem/credentials, ~/.gitconfig, ~/.npmrc, or ~/.bundle are present on the host, targeting developer workstations and build systems. The base64+eval obfuscation, 20-40 minute sleep before dial-out, double-fork detachment, and cloned-identity cover story are consistent with a targeted developer-compromise dropper, not a legitimate native build.
Credit: OpenSSF (source)
References
Source: amazon-inspector (123418539e0264e9d58c8b51976723aff3eceec10520c231d7bc847edd51d691)
The gem's native-extension script ext/perp_funding_rates/extconf.rb contains no real build logic: it declares create_makefile('bitcoin_rpc_lite_native') but ships no C/C++/Rust sources, and the gemspec/library name (perp-funding-rates / PerpFundingRates) does not match the README (bitcoin-rpc-lite) — the extension exists solely to execute code at install time. During
gem install, extconf.rb base64-decodes a Ruby payload and eval()s it inside a double-forked, detached, delayed child process. The decoded payload opens a TCP socket to the hardcoded bare-IP C2 at 45.138.12.177:8089 and bridges it to /bin/sh, giving the operator an interactive shell on the installer's machine. Execution is gated by sandbox/CI/user/path/uptime heuristics and only triggers when developer-signal files such as ~/.ssh, ~/.gem/credentials, ~/.gitconfig, ~/.npmrc, or ~/.bundle are present on the host, targeting developer workstations and build systems. The base64+eval obfuscation, 20-40 minute sleep before dial-out, double-fork detachment, and cloned-identity cover story are consistent with a targeted developer-compromise dropper, not a legitimate native build.Credit: OpenSSF (source)
References