# MAL-2026-17798: Malicious code in tron-trc20-utils (RubyGems)


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

## What is MAL-2026-17798?

MAL-2026-17798 is a malicious package in tron-trc20-utils, published on 11 Oct 2026. 

### Official description

The gem's extconf.rb contains a base64-encoded Ruby payload that is decoded and eval'd inside a detached double-forked child during `gem install`. The decoded code opens a TCP connection to 45.138.12.177:8089 and bridges it to /bin/sh, giving the remote operator an interactive shell on the installer's machine. Execution is gated by sandbox/CI-evasion checks: it skips if common CI environment variables are set, if the hostname or username matches sandbox/analyst patterns (uvm/firecracker/sandbox/vagrant/tester/analys/scanner), if the working directory is under /tmp, /opt/rubygems, or /workspace, if /proc/uptime is under 1800 seconds, and it additionally requires developer artifacts such as ~/.ssh, ~/.gitconfig, ~/.gem/credentials, ~/.npmrc, or ~/.bundle to be present. The gem's advertised identity does not match its contents: the gemspec names it `tron-trc20-utils`, the README is for `bitcoin-rpc-lite`, extconf.rb calls `create_makefile('bitcoin_rpc_lite_native')`, and the shipped library is a trivial stub exposing only VERSION, build_id, and healthy? — the install-time reverse shell is the package's only real functionality.

The OpenSSF Package Analysis project identified 'tron-trc20-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-17798?

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-17798 is a malicious package: tron-trc20-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-17798/ (Markdown: https://insights.sbomify.com/MAL-2026-17798/index.md)
```

## Sources

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

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