Which versions of sa62b50d0b are malicious?

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

How do I remediate sa62b50d0b if I installed it?

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

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

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

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

Malicious package

sa62b50d0bRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8562

Immediate action

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

gem uninstall sa62b50d0b

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

26a95f16e2014efeab79e04dc9adf4542be5aaa05a24faa656cacb71168f3703

1aa84dd14ae5b6a6891b8c6f7fbf45331f69287faf5d18e686eb958bfad709e8

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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