Which versions of hgwcal1 are malicious?

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

How do I remediate hgwcal1 if I installed it?

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

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

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

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

Malicious package

hgwcal1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7754

Immediate action

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

gem uninstall hgwcal1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

4c24fa706ee0d456d92e1126225cc81bec1cf1c3e0b4b1158fe108ecc611020c

a2015295738e6d1405489e97361d25b2c664a80893ffe1ea75e5bef6a8f01a94

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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