Which versions of sad01504db are malicious?

The following RubyGems versions of sad01504db are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate sad01504db if I installed it?

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

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

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

Search your lockfiles and build artifacts for sad01504db (version 0.0.1).

Malicious package

sad01504dbRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

sad01504db is a confirmed malicious RubyGems package (MAL-2026-8571) 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 sad01504db (RubyGems)

MAL-2026-8571

Immediate action

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

gem uninstall sad01504db

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b1ac115d4f264c9932f133d1546f8315f2c41a87fead1d967b974d6fd86b790d

757798220ed7c88fba706ce54f5b6b842724a435ce0a240870cdd1f6c1b2968c

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for sad01504db (version 0.0.1).
If you installed it — respond
Remove sad01504db 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 sad01504db 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. sad01504db 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-03222RLUA-2026-09116

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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