Which versions of burndler are malicious?

The following RubyGems versions of burndler are flagged malicious: 1.0.66322. Treat any of these as compromised.

How do I remediate burndler if I installed it?

Remove burndler from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed burndler — how do I know if it already compromised me?

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

Yes — burndler is associated with the RLMA-2026-07840 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 burndler across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for burndler (version 1.0.66322).

Malicious package

burndlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

burndler is a confirmed malicious RubyGems package (MAL-2026-17151) that executes malicious code on install (malicious version 1.0.66322). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in burndler (RubyGems)

MAL-2026-17151

Immediate action

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

gem uninstall burndler

Malicious versions

1 flagged

1.0.66322

Indicators of compromise (SHA-256)

4e030b3222ca24fa3bb8b88e036a44c35a9f79772040cb9020abe91da58fa218

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for burndler (version 1.0.66322).
If you installed it — respond
Remove burndler from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If burndler 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. burndler on RubyGems has been identified as a malicious package (version 1.0.66322 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-07840

Credits

ReversingLabs · finder

Detect & block this

O3 blocks burndler-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database