# MAL-2026-17784: Malicious code in dex-router-abis (RubyGems)


- **Type:** Malicious package
- **Package:** `dex-router-abis` (RubyGems)
- **Published:** 11 Oct 2026

## What is MAL-2026-17784?

MAL-2026-17784 is a malicious package in dex-router-abis, published on 11 Oct 2026. 

### Official description

The gem's extconf.rb (executed automatically during `gem install`) decodes a base64-encoded Ruby payload and executes it via a double-forked, detached process that sleeps 20-40 minutes before opening a TCP reverse shell from /bin/sh to the hardcoded remote host 45.138.12.177:8089. Execution is gated by environment checks that look for CI/sandbox/analysis indicators and probe for developer-secret artifacts (~/.ssh, ~/.gitconfig, ~/.gem/credentials, ~/.npmrc, ~/.bundle) so the payload fires only on real developer workstations with credentials present. The create_makefile stub in extconf.rb is a cover: no matching native source exists in the gem tree, and README/metadata identify the package as 'bitcoin-rpc-lite' (makefile target bitcoin_rpc_lite_native) while the published gem name is dex-router-abis, indicating a reused dropper template. Installing this gem grants the operator at 45.138.12.177:8089 interactive shell access to the installer's host with access to local SSH keys, RubyGems publishing credentials, and other developer secrets.

The OpenSSF Package Analysis project identified 'dex-router-abis' @ 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-17784?

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-17784 is a malicious package: dex-router-abis (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-17784/ (Markdown: https://insights.sbomify.com/MAL-2026-17784/index.md)
```

## Sources

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

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