Which versions of wptask2 are malicious?

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

How do I remediate wptask2 if I installed it?

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

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

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

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

Malicious package

wptask2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9482

Immediate action

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

gem uninstall wptask2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f69d5a986603ccccbdcf23cc6bd719d989a32d45125c40bb43011b97425b786d

b094eba3cd562c9cb013b7264d8840c7c08a0b187fce25806f9a2c437c8f6a70

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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