Which versions of swcalcalb are malicious?

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

How do I remediate swcalcalb if I installed it?

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

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

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

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

Malicious package

swcalcalbRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8922

Immediate action

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

gem uninstall swcalcalb

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

0799bc77d5f3d7c3a4002f9ad299d7137c068817bfe5859476efdc8ca4ca3390

8336f46fc33ae1f3e9dd4981d5fc71206e0a6ab76c7d5327be960ed562df704e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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