Which versions of swmodsjabc are malicious?

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

How do I remediate swmodsjabc if I installed it?

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

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

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

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

Malicious package

swmodsjabcRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8948

Immediate action

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

gem uninstall swmodsjabc

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

15265923a478fb56a6ff0dfa5de3f7cfe76a87b45f9bf6b32aa538ec88081600

847084681176bb9dbffe4bb19ec73f44cc10345ac78663ec9e28790f1b24c93c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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