Which versions of wwk2601txtabcde are malicious?

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

How do I remediate wwk2601txtabcde if I installed it?

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

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

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

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

Malicious package

wwk2601txtabcdeRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9508

Immediate action

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

gem uninstall wwk2601txtabcde

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

4ff12c54a843b65ddc6b813b1206d5e43ecdef49e60707b47af269399d8fbf6e

aae955cda09843f8808c0f7435c77c5a7849eaca1fe488db49010b0a295f49fd

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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