Skip to content

← Actionable
Unrated

Malicious code in staking-apr-fetcher (RubyGems)

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • RubyGems staking-apr-fetcher

    Affected
    >= 0.9.1, <= 0.9.1
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

--- _-= 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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from osv record MAL-2026-17796

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: mal-2026-17796

Advisory: Malicious code in staking-apr-fetcher (RubyGems)
IDs: mal-2026-17796
Record: https://patchnext.com/advisories/mal-2026-17796 (revision 1, source checked 23 Oct 2026, 22:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- RubyGems staking-apr-fetcher: affected >= 0.9.1, <= 0.9.1

## Suggested inspection (read-only)
- RubyGems staking-apr-fetcher: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on staking-apr-fetcher.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/MAL-2026-17796 (OSV record MAL-2026-17796 lists affected ranges: RubyGems staking-apr-fetcher >=0.9.1 <=0.9.1)

Commands are suggestions: review each one before running it.

Loading voting…