Which versions of hwc7v are malicious?

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

How do I remediate hwc7v if I installed it?

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

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

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

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

Malicious package

hwc7vRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7775

Immediate action

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

gem uninstall hwc7v

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

06061c4d245d16087f6a88490aba182035dedb5921a24416a6e23c61c58b189c

af54564db1f95fe12f962ed1a280b5bf3ed14740e046e5f39c55749f2cd761f7

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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