Which versions of wphra2 are malicious?

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

How do I remediate wphra2 if I installed it?

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

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

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

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

Malicious package

wphra2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9441

Immediate action

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

gem uninstall wphra2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d4176e338888239f743b5660726e65b7511c51b3e40db716923ffa47835954a4

ddac78b3122180f2d6310a2ed3dd3126176791d73e53d69bb2c37a1ba52219fe

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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