Which versions of hwc6v are malicious?

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

How do I remediate hwc6v if I installed it?

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

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

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

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

Malicious package

hwc6vRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7774

Immediate action

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

gem uninstall hwc6v

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

872c74f35b2c75e65e3e6b79b0b3525e7cb9f37ff7df4884fee717e82404c259

b448e4547a1f452d0eeffa39d55c8691b492355543ec7ffe10159ff40504da1c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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