Which versions of wgsfosmgcal2 are malicious?

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

How do I remediate wgsfosmgcal2 if I installed it?

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

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

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

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

Malicious package

wgsfosmgcal2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9342

Immediate action

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

gem uninstall wgsfosmgcal2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

13c7ecaf2a882343fb3584d34c6aab675970ca56714cbd5e4e105754edd0fc0c

30ab2eb55a496d991426d1a6a9c640d6a80b743c4b5d14e23b62104b6e102326

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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