Which versions of ligbtning-invoice are malicious?

The following RubyGems versions of ligbtning-invoice are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate ligbtning-invoice if I installed it?

ligbtning-invoice 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 ligbtning-invoice — how do I know if it already compromised me?

If ligbtning-invoice 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 ligbtning-invoice part of a known attack campaign?

Yes — ligbtning-invoice is associated with the IN-MAL-2026-021052 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 ligbtning-invoice across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for ligbtning-invoice (version 1.0.0).

Malicious package

ligbtning-invoiceRubyGems

Advisory published Oct 5, 2026Updated Oct 6, 2026

ligbtning-invoice is a confirmed malicious RubyGems package (MAL-2026-17605) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ligbtning-invoice (RubyGems)

MAL-2026-17605

Immediate action

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

gem uninstall ligbtning-invoice

What this malware does

RubyGems runs this gem's native extension script ext/ligbtning-invoice/extconf.rb during gem install. The script exits without action on CI runners and sandboxes, based on CI environment variables, the hostname, the username and the working directory. It continues if the system uptime is over 30 minutes and the home directory holds .ssh, .gitconfig, .npmrc, .gem/credentials or .bundle. It then decodes a Base64 Ruby payload and forks twice into a detached process. After 20 to 40 minutes the payload downloads http://45.138.12.177:8092/wgkit.tar.gz to /tmp/.w1.tgz with curl, extracts it to /tmp/.w1/, runs wg_install.sh with bash and deletes both. The payload stores the URL XOR-encoded with the key usv\x9a. The Ruby code in lib/ is a decoy. The RubyGems account reqthrottle_3474 published this gem and 41 others with the same loader on 2026-10-05.

The gem's native extension script extconf.rb, which RubyGems executes automatically during gem install, base64-decodes an embedded Ruby payload and evaluates it inside a double-forked, detached background process. The payload XOR-decodes a hardcoded plain-HTTP URL at 45.138.<redacted>:8092/wgkit.tar.gz, downloads the tarball to /tmp/.w1.tgz, extracts it, and executes the embedded wg_install.sh via bash, then removes traces. The payload is gated by environment fingerprinting that suppresses execution in CI, sandbox, and analysis environments: it checks CI env vars, hostnames matching firecracker/sandbox/vagrant/uvm, auto-generated usernames, analysis working-directory prefixes (/opt/rubygems, /tmp, /workspace), machine uptime, and the presence of developer artifacts (~/.ssh, ~/.gitconfig, ~/.npmrc, ~/.gem/credentials, ~/.bundle), then sleeps a randomized 20-40 minutes before firing. The shipped library is a hollow stub exposing only a trivial word list (LigbtningInvoice.words/word_at/index_of) and an empty C extension (Init_LigbtningInvoice is a no-op), while the gem name transposes letters relative to a legitimate Lightning/BOLT11 package, indicating a typosquat lure whose sole purpose is delivering the extconf.rb dropper.

The OpenSSF Package Analysis project identified 'ligbtning-invoice' @ 1.0.0 (rubygems) as malicious.

It is considered malicious because:

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

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

86fdee6169e308a4849aae46edf725272a04cc0fe706f18006dcde8f54f86e2a

3c9674944c77b8c371e9f2aad6933c99db3f3ccc19e8b2e9a28f8ef1c7d681c3

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for ligbtning-invoice (version 1.0.0).
If you installed it — respond
ligbtning-invoice 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 ligbtning-invoice 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. ligbtning-invoice on RubyGems has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021052

References

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder
SafeDep · finder

Detect & block this

O3 blocks ligbtning-invoice-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