Which versions of zwcalx7 are malicious?

The following RubyGems versions of zwcalx7 are flagged malicious: 0.0.492. Treat any of these as compromised.

How do I remediate zwcalx7 if I installed it?

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

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

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

Search your lockfiles and build artifacts for zwcalx7 (version 0.0.492).

Malicious package

zwcalx7RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

zwcalx7 is a confirmed malicious RubyGems package (MAL-2026-9850) that executes malicious code on install (malicious version 0.0.492). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in zwcalx7 (RubyGems)

MAL-2026-9850

Immediate action

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

gem uninstall zwcalx7

Malicious versions

1 flagged

0.0.492

Indicators of compromise (SHA-256)

495de067a7e4cf242e8e34a79952e44338122980bba8b26b910334dea2568962

46c350309c8fbe2ad799b015d6045d3e82acb55b22dcaa282d598fb5ecc11c00

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for zwcalx7 (version 0.0.492).
If you installed it — respond
Remove zwcalx7 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 zwcalx7 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. zwcalx7 on RubyGems has been identified as a malicious package (version 0.0.492 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-04501RLUA-2026-10439

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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