Which versions of hwc1v are malicious?

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

How do I remediate hwc1v if I installed it?

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

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

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

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

Malicious package

hwc1vRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7769

Immediate action

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

gem uninstall hwc1v

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a093ff2af5a58d05bbf18d2e5615f2ea14f1d16db118bed8f1827b48d2d67692

ad607f94cf9d837c13928ba03a93a8cb3af406eada7ffe4161156df5fcdfb35f

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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