Which versions of mega-clean-sys are malicious?

The following RubyGems versions of mega-clean-sys are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate mega-clean-sys if I installed it?

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

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

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

Search your lockfiles and build artifacts for mega-clean-sys (version 0.0.1).

Malicious package

mega-clean-sysRubyGems

Advisory published Aug 24, 2026Updated Sep 1, 2026

mega-clean-sys is a confirmed malicious RubyGems package (MAL-2026-15712) that executes malicious code on install (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mega-clean-sys (RubyGems)

MAL-2026-15712

Immediate action

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

gem uninstall mega-clean-sys

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5e983042616e2a8c1d382394900066a3603e7545309906920b8218352ee01170

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05678

Credits

ReversingLabs · finder

Detect & block this

O3 blocks mega-clean-sys-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