Malicious code in tron-trc20-utils (RubyGems)
What to do
Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
RubyGems tron-trc20-utils
- Affected
- >= 0.9.1, <= 0.9.1
- Fixed in
- no fixed version recorded
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record MAL-2026-17798 lists affected ranges: RubyGems tron-trc20-utils >=0.9.1 <=0.9.1
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- not scored
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
--- _-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (c840b18eadc331896e56720bc9a00f1239807542202bbd4ff9636737f27d0142) 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…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from osv record MAL-2026-17798
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: mal-2026-17798 Advisory: Malicious code in tron-trc20-utils (RubyGems) IDs: mal-2026-17798 Record: https://patchnext.com/advisories/mal-2026-17798 (revision 1, source checked 23 Oct 2026, 22:04 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Unrated Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed. ## Affected components - RubyGems tron-trc20-utils: affected >= 0.9.1, <= 0.9.1 ## Suggested inspection (read-only) - RubyGems tron-trc20-utils: check the installed version with your package manager. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on tron-trc20-utils. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/MAL-2026-17798 (OSV record MAL-2026-17798 lists affected ranges: RubyGems tron-trc20-utils >=0.9.1 <=0.9.1) Commands are suggestions: review each one before running it.
Loading voting…