Which versions of wallet-balance-scanner are malicious?

The following RubyGems versions of wallet-balance-scanner are flagged malicious: 0.9.1. Treat any of these as compromised.

How do I remediate wallet-balance-scanner if I installed it?

wallet-balance-scanner is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed wallet-balance-scanner — how do I know if it already compromised me?

If wallet-balance-scanner was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is wallet-balance-scanner part of a known attack campaign?

Yes — wallet-balance-scanner is associated with the IN-MAL-2026-021358 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find wallet-balance-scanner across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for wallet-balance-scanner (version 0.9.1).

Malicious package

wallet-balance-scannerRubyGems

Advisory published Oct 11, 2026Updated Oct 13, 2026

wallet-balance-scanner is a confirmed malicious RubyGems package (MAL-2026-17799) that steals credentials and exfiltrates sensitive data (malicious version 0.9.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in wallet-balance-scanner (RubyGems)

MAL-2026-17799

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

gem uninstall wallet-balance-scanner

What this malware does

The gem declares a native extension at ext/wallet_balance_scanner/extconf.rb but ships no C/C++/Rust sources; the extconf.rb is itself the payload rather than a build script, and runs automatically during gem install. The script decodes a base64 blob and launches it inside a detached, delayed forked process which opens a TCPSocket to the hardcoded bare-IP C2 45.138.12.177:8089 and pipes /bin/sh to it, handing a shell on the installer's host to the operator of that endpoint. Execution is gated by developer-workstation heuristics: it checks for ~/.ssh, ~/.gitconfig, ~/.npmrc, ~/.gem/credentials and ~/.bundle, requires host uptime over 1800 seconds, and bails out on CI, ephemeral hostnames, generated usernames, and known analysis/sandbox path prefixes, so the backdoor fires only on real developer machines. The lib/wallet_balance_scanner.rb entry and README (which refers to an unrelated bitcoin_rpc_lite library) are stubs with no relation to the declared wallet-scanning purpose, consistent with a cover-story gem whose only functional component is the install-time reverse shell.

The OpenSSF Package Analysis project identified 'wallet-balance-scanner' @ 0.9.1 (rubygems) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

0.9.1

Indicators of compromise (SHA-256)

1506ac4eca059796d3f029e96fcfcafc24ffc6ad0b454ae831c06edef4064055

c307a3154873fc791254b5f8fd91803e64e5b49c8ec114a2eadcee895614ab42

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for wallet-balance-scanner (version 0.9.1).
If you installed it — respond
wallet-balance-scanner is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If wallet-balance-scanner was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. wallet-balance-scanner on RubyGems has been identified as a malicious package (version 0.9.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021358

References

rubygems.org

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks wallet-balance-scanner-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database