Which versions of md_confluence are malicious?

The following RubyGems versions of md_confluence are flagged malicious: 5.0.1. Treat any of these as compromised.

How do I remediate md_confluence if I installed it?

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

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

Yes — md_confluence is associated with the RLMA-2025-06620, RLUA-2026-08585 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 md_confluence across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for md_confluence (version 5.0.1).

Malicious package

md_confluenceRubyGems

Advisory published Dec 23, 2025Updated Sep 24, 2026

md_confluence is a confirmed malicious RubyGems package (MAL-2025-192911) that executes malicious code on install (malicious version 5.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in md_confluence (RubyGems)

MAL-2025-192911

Immediate action

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

gem uninstall md_confluence

Malicious versions

1 flagged

5.0.1

Indicators of compromise (SHA-256)

3d82836f30846a4b6b926ae78913f46d467cdb36fc374066f26919a1ff612b8a

8cca1eecd793399f856938147cea8d489af9146e803be355d0f1ff14eda77525

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-06620RLUA-2026-08585

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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