Which versions of slg12549 are malicious?

The following RubyGems versions of slg12549 are flagged malicious: 0.0.2. Treat any of these as compromised.

How do I remediate slg12549 if I installed it?

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

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

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

Search your lockfiles and build artifacts for slg12549 (version 0.0.2).

Malicious package

slg12549RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in slg12549 (RubyGems)

MAL-2026-8635

Immediate action

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

gem uninstall slg12549

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

dba39b4692a8332114ed18c3e1f030d89c17b473a8307b7b16492be182235ae9

36e78c69fbe4f52bdd5e7b672eecfd2b293ba8f73dce521fc3d1da3906eb050b

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-03286RLUA-2026-09184

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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