staking-apr-fetcher
Affected
- Versions:
0.9.1
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: None
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in staking-apr-fetcher (RubyGems)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (405ab5b9651b8e8817ae91290042ec22673c5c99c1b58f45747e47cbb85aeacf)
The gem declares a native extension whose build script (extconf.rb) decodes a base64-embedded Ruby payload and executes it via eval during gem install. The payload double-forks a detached background process that opens a TCP connection to the hardcoded host 45.138.12.177:8089 and bidirectionally copies between that socket and a locally spawned /bin/sh, giving the operator of that endpoint interactive shell access on the installer's machine. Execution is gated by anti-analysis checks: the payload only fires when the environment does not look like CI, an ephemeral/sandbox VM (patterns matching uvm/firecracker/sandbox/vagrant), a generated analyst user (patterns matching uA\d+/sandbox/tester/analys/scanner), or a known analysis path (/opt/rubygems, /tmp/, /workspace/), and only when system uptime exceeds 1800 seconds and developer-identifying files exist (~/.ssh, ~/.gitconfig, ~/.gem/credentials, ~/.bundle, ~/.npmrc). The gem's advertised identity is a cover story: it is published as staking-apr-fetcher with a staking-related summary, but the README is titled bitcoin-rpc-lite, the extension's generated makefile is bitcoin_rpc_lite_native, no C sources are shipped for that native target, and the Ruby library (lib/staking_apr_fetcher.rb) is an inert stub defining only VERSION/build_id/healthy?. The package has no legitimate functionality; its sole purpose is to deliver the install-time backdoor.
Source: ossf-package-analysis (77e16e0b65be41b278edbb76b9a9d73b9567d78d302a6b568dc037ced7efce7f)
The OpenSSF Package Analysis project identified 'staking-apr-fetcher' @ 0.9.1 (rubygems) as malicious.
It is considered malicious because:
Not rated by the source.
0.9.1None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0