Which versions of hgwcal2 are malicious?

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

How do I remediate hgwcal2 if I installed it?

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

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

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

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

Malicious package

hgwcal2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7755

Immediate action

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

gem uninstall hgwcal2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

38313e69fc9a1320aeaa5049db5d6e5b681340f5fcddb011de0fad8546ffec5e

6748c7c3f5ef8145dcc4fe3f39c38731ab6c3c21e5854f88f5cd70b64c4b8ebc

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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