Which versions of swcalcalg are malicious?

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

How do I remediate swcalcalg if I installed it?

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

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

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

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

Malicious package

swcalcalgRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8925

Immediate action

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

gem uninstall swcalcalg

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

af4cc04ad01448674672b9ee4be60bfbca032fbacb6bd99e9ba7c71068c3e199

6822cd39343b710d0d2da4becc97e26469e93f64c30ea482e79a90cdeb827d1c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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