Which versions of donjon-ledger are malicious?

The following RubyGems versions of donjon-ledger are flagged malicious: 2.0.2. Treat any of these as compromised.

How do I remediate donjon-ledger if I installed it?

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

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

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

Search your lockfiles and build artifacts for donjon-ledger (version 2.0.2).

Malicious package

donjon-ledgerRubyGems

Advisory published Nov 8, 2026Updated Nov 8, 2026

donjon-ledger is a confirmed malicious RubyGems package (MAL-2026-18765) that steals credentials and exfiltrates sensitive data (malicious version 2.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in donjon-ledger (RubyGems)

MAL-2026-18765

Immediate action

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

gem uninstall donjon-ledger

What this malware does

The gemspec declares ext/mkrf_conf.rb as a native extension, causing it to execute automatically during gem install. The script ships no C/C++/Rust sources and performs no build work. Instead it collects host identifiers (hostname, username) and reads /etc/passwd, /etc/hosts, and /etc/resolv.conf, then opens a TLS connection to the hardcoded Burp Collaborator subdomain 8enejtlpqb2m1fzcaieyzjgv3m9mxcl1.oastify.com on port 443 and POSTs the collected JSON. A DNS lookup to the same subdomain is also performed. The script writes a.installed marker and exits. The extension hook exists solely as an install-time execution vector for this exfiltration payload.

Malicious versions

1 flagged

2.0.2

Indicators of compromise (SHA-256)

4ab38ebb03685b0ddfa31074b056e0a95da764170efe3026ed822ff7c8b3c247

Detection & response playbook

Credential / info stealer

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

Campaign

IN-MAL-2026-022567

References

rubygems.org

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks donjon-ledger-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