Which versions of hwc4v are malicious?

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

How do I remediate hwc4v if I installed it?

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

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

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

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

Malicious package

hwc4vRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7772

Immediate action

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

gem uninstall hwc4v

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

77473b6979660c383fd6828b34defa75c98c119e91107b4d0f544bf82c7eea83

5ab4a55c2dc2ed4408c1c87afc1ce3f63a38bcdfc4a786aa24345b613a1b77f0

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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