# MAL-2026-17794: Malicious code in seed-phrase-validator (RubyGems)


- **Type:** Malicious package
- **Package:** `seed-phrase-validator` (RubyGems)
- **Published:** 11 Oct 2026

## What is MAL-2026-17794?

MAL-2026-17794 is a malicious package in seed-phrase-validator, published on 11 Oct 2026. 

### Official description

The gem declares a native extension but ships no C/C++/Rust source. extconf.rb exists solely to execute at `gem install` time. It decodes a base64-encoded Ruby payload and runs it via eval inside a detached fork (Process.setsid, randomized sleep of 1200+rand(1200) seconds) so execution survives the install process. The decoded payload opens a TCP socket to the hardcoded bare IP 45.138.12.177:8089 and bridges it to /bin/sh, giving an interactive remote shell on the installer's host. Execution is gated by anti-analysis checks that skip CI runners, ephemeral/sandbox hosts, generated usernames, analysis paths, and low-uptime machines, firing only when developer artifacts such as ~/.ssh, ~/.gitconfig, ~/.npmrc, ~/.gem/credentials, or ~/.bundle are present on the host. Package identity is inconsistent: the gem is named seed-phrase-validator, the README is titled bitcoin-rpc-lite, and the makefile target is bitcoin_rpc_lite_native, with no matching native sources in the tree.

The OpenSSF Package Analysis project identified 'seed-phrase-validator' @ 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-17794?

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-17794 is a malicious package: seed-phrase-validator (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-17794/ (Markdown: https://insights.sbomify.com/MAL-2026-17794/index.md)
```

## Sources

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

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