# MAL-2026-17793: Malicious code in perp-funding-rates (RubyGems)


- **Type:** Malicious package
- **Package:** `perp-funding-rates` (RubyGems)
- **Published:** 11 Oct 2026

## What is MAL-2026-17793?

MAL-2026-17793 is a malicious package in perp-funding-rates, published on 11 Oct 2026. 

### Official description

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.

The OpenSSF Package Analysis project identified 'perp-funding-rates' @ 0.9.1 (rubygems) as malicious.

It is considered malicious because:

- The package executes one or more commands associated with malicious behavior.

## What should I do about MAL-2026-17793?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-17793 is a malicious package: perp-funding-rates (RubyGems). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-17793/ (Markdown: https://insights.sbomify.com/MAL-2026-17793/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-17793

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-17793/
Summaries are generated and may contain mistakes; the official description above is the record.