Which versions of swcalcalh are malicious?

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

How do I remediate swcalcalh if I installed it?

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

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

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

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

Malicious package

swcalcalhRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8926

Immediate action

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

gem uninstall swcalcalh

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a46895f273deee84cbbb91adff8429cee0c3d674aed93d88cd81ba88e94102bc

33a7a7f0b135aa30c480f5b9e5f5f8177178afbad739c1d07242b9fadb7ee670

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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