# MAL-2026-17795: Malicious code in sol-mint-utils (RubyGems)


- **Type:** Malicious package
- **Package:** `sol-mint-utils` (RubyGems)
- **Published:** 11 Oct 2026

## What is MAL-2026-17795?

MAL-2026-17795 is a malicious package in sol-mint-utils, published on 11 Oct 2026. 

### Official description

The gem ships a native-extension stub (extconf.rb) that `gem install` executes automatically, but no C/C++ sources accompany it and lib/sol_mint_utils.rb is an inert stub (defines VERSION and returns 'ok'). The README advertises an unrelated package name (`bitcoin-rpc-lite`), confirming the gem's declared purpose is a cover. extconf.rb base64-decodes a Ruby payload and eval's it inside a forked/detached process; the decoded payload opens a TCPSocket to the hardcoded host 45.138.12.177 on port 8089 and bridges a /bin/sh session over the socket via IO.popen and IO.copy_stream, granting the operator an interactive reverse shell on the installer's machine. Execution is gated by anti-analysis checks: CI environment variables, hostname patterns (uvm/firecracker/sandbox/vagrant), generated usernames, analysis working directories (/opt/rubygems, /tmp, /workspace), and short /proc/uptime values all suppress the payload, which fires only when developer artifacts such as ~/.ssh, ~/.gitconfig, and ~/.gem/credentials are present on the host.

The OpenSSF Package Analysis project identified 'sol-mint-utils' @ 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-17795?

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-17795 is a malicious package: sol-mint-utils (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-17795/ (Markdown: https://insights.sbomify.com/MAL-2026-17795/index.md)
```

## Sources

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

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