Which versions of wpment2 are malicious?

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

How do I remediate wpment2 if I installed it?

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

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

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

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

Malicious package

wpment2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9444

Immediate action

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

gem uninstall wpment2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

c3720e2017369d996139f1bd054d84217f5326266534f552be3079815f84ccbc

641377e1f900438e5c991023b16187b9ed78d3ad3a48038fed04e86b193d5254

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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