Which versions of lightinng-invoice are malicious?

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

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

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

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

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

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

Malicious package

lightinng-invoiceRubyGems

Advisory published Oct 5, 2026Updated Oct 6, 2026

lightinng-invoice is a confirmed malicious RubyGems package (MAL-2026-17607) 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 lightinng-invoice (RubyGems)

MAL-2026-17607

Immediate action

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

gem uninstall lightinng-invoice

What this malware does

RubyGems runs this gem's native extension script ext/lightinng-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 lightinng-invoice is a typosquat of the Lightning/BOLT11 ecosystem (duplicated 'n', homepage lightinng-invoice.dev) whose advertised functionality is a decoy: lib/lightinng-invoice.rb exposes only a static word list and the declared native extension's C source is an empty 55-byte stub (Init_LightinngInvoice(void) {}). The sole operational code is in ext/lightinng-invoice/extconf.rb, which RubyGems auto-executes during gem install. That script evaluates a base64-encoded Ruby payload that XOR-decodes a hardcoded C2 URL (http://45.138.122.177:8092/wgkit.tar.gz), curls the tarball to /tmp/.w1.tgz, extracts it, and runs bash /tmp/.w1/wg_install.sh inside a double-forked detached child so execution survives the installer process. The dropper is gated with explicit anti-analysis checks: it refuses to fire in CI, on ephemeral/sandbox hostnames, under generated analyst usernames, in analysis paths (/tmp, /opt/rubygems, /workspace), when uptime is under 1800 seconds, or when developer-signal files are absent — it specifically requires the presence of ~/.ssh, ~/.gitconfig, ~/.npmrc, ~/.gem/credentials, and ~/.bundle before proceeding, then sleeps 1200+rand(1200) seconds before executing. The targeting pattern and secret-adjacent gating identify developer workstations with credentials as the intended victims.

The OpenSSF Package Analysis project identified 'lightinng-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)

38a3cbc58408f7b8e0edb2aa678ba4765867b535513e8609be0d87e93687eca3

cde76db725f1a356a4594636391e02715ee39cf1a4691ba1b6165099cd6a4978

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for lightinng-invoice (version 1.0.0).
If you installed it — respond
lightinng-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 lightinng-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. lightinng-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-021050

References

Credits

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

Detect & block this

O3 blocks lightinng-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