HighAdvisory sweepRubyGems1 affected version

wallet-balance-scanner

wallet-balance-scanner has 1 version on RubyGems.org flagged in 2 incidents we track. Only the exact versions listed below were named by the source advisories.

wallet-balance-scanner was recorded in a daily advisory sweep. The write-up groups it into a cluster with the evidence available at the time; check the cluster note before treating it as a confirmed compromise.

Affected versions

Check what you actually have installed with gem list wallet-balance-scanner.

wallet-balance-scanner@0.9.1

The 2 incidents that flagged it

High13 Oct 2026

GitHub Advisory malware sweep - 2026-10-13 (Baileys/libsignal lure operator wave 3 - 60+ npm packages across `@revizahoshii/`, `@fazzcodestudio/`, `@sanzoffc/`, `@wanzlonely/`, `@mikudeveloper/`, `@modss/`, `@ikanngeming/`, `@fhkryxv/`, `@saazkira/`, `@badzz88/`, `@alipclutch/`, `@mivesensei/`, `@kanaraa/`, `@chatunity/`, `@zanta/`, `@yudzxml/`, `@zeronexcode/`, plus `baileys-xbats`/`bailslonely`/`nakkinpm`/`amprem` unscoped - all CWE-506 boilerplate takedowns against `@WhiskeySockets/Baileys` WhatsApp-automation lures; confirmed-payload carve-outs within the sweep: PyPI `npp-ml` Notepad++ impersonator deploying ADExplorer AD-recon tool, PyPI `minecraftaccfinder` Gmail/Roblox/Discord/Minecraft infostealer+RAT with keylogger/screenshots/browser-creds, RubyGems `wallet-balance-scanner` fake-native-extension reverse-shell to hardcoded endpoint; s4yhii wave 3 continuation `@s4yhiitestpoc/r2-https-b` on `collector.oob.s4yhii.com`; plus 25+ dep-confusion probes at `99.x`/`100.x`/`101.x` sentinels: `@myorder-frontend-commons/`, `risk-detection`, `unified-platform`, `@pinecone-experience/`, `@airbnb-extended/`, `@tesla-insurance/`, `@user-services/`, `app-sca-info-banking`, `com.apple.unityplugin.storekit` Apple-brand impersonator, and more)

GHSA 2026-10-12 batch (ingested 2026-10-13): ~90 fresh malware advisories, dominated by a Baileys/libsignal lure operator wave 3 of 60+ WhatsApp-automation-brand typosquats (continuation of 2026-10-10 Cluster C). Confirmed payloads: PyPI npp-ml Notepad++ impersonator deploying ADExplorer, PyPI minecraftaccfinder multi-platform infostealer+RAT, RubyGems wallet-balance-scanner fake-native-extension reverse shell. Plus @s4yhiitestpoc/r2-https-b continuing s4yhii wave 3 and 25+ dep-confusion sentinel probes.

Versions named here: 0.9.1

High12 Oct 2026

RubyGems wgkit wave 2 - 24 DeFi/MEV/wallet/NFT crypto gems at `0.9.1` drop a direct `/bin/sh` reverse shell to `45.138.12.177:8089` from `extconf.rb`, same operator as the 2026-10-05 wgkit cluster

OpenSSF/Amazon Inspector flagged 24 fresh malicious RubyGems on 2026-10-11 (ingested 2026-10-12) - all v0.9.1, all shipping an ext/<name>/extconf.rb base64-decoded Ruby payload that double-forks, sleeps 20-40 min, and pipes a TCP socket to /bin/sh against 45.138.12.177:8089. Same C2 IP, same evasion gates, same bitcoin_rpc_lite_native cover extension as the 2026-10-05 wgkit cluster - this is wave 2 of the same operator, now targeting DeFi/MEV/wallet-HD/NFT/TRC20/jetton verticals.

Versions named here: 0.9.1

What to do if you installed one of these

Treat the machine as compromised rather than simply upgrading. Packages in these incidents typically execute at install time, so the payload has already run with whatever credentials were in the environment.

1.Rotate every credential that machine or CI job could reach - registry tokens, cloud keys, SSH keys, CI secrets - from a different machine.
2.Pin to a version not listed above, then reinstall from a clean lockfile.
3.Clear caches and private mirrors. Artifactory, Nexus, Verdaccio, and devpi routinely keep serving a tarball after the public registry has pulled it.
4.Read the incident write-up above - recommended actions differ per incident, and some have specific indicators of compromise worth grepping your logs for.

Check your whole project

wallet-balance-scanner is one of many packages in these incidents, and it is usually pulled in as a transitive dependency rather than one you installed directly. We don't parse RubyGems manifests yet, but the incident write-ups list every affected package.

Browse the incident feed All flagged RubyGems packages

Other packages in the same incident

If wallet-balance-scanner is in your tree, these are worth checking too - they were published by the same campaign.

See the full incident

Version data comes from the public advisories cited on each incident page. We list only versions those advisories name - we don't infer additional ones. Think this is wrong or incomplete? Tell us.