Which versions of swcossjabc are malicious?

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

How do I remediate swcossjabc if I installed it?

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

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

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

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

Malicious package

swcossjabcRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8930

Immediate action

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

gem uninstall swcossjabc

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8a9e1ea2c930cada7faa359a619ef47eeab0c327cd02a93f6d01ca9d25408647

c066453a17ad99fd6d7876cf8036904f527569ec4422af2f3fe1d86a06a7f1d7

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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