Which versions of wp875 are malicious?

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

How do I remediate wp875 if I installed it?

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

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

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

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

Malicious package

wp875RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9424

Immediate action

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

gem uninstall wp875

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

34e678a6106feb53d8a65d08946c38a86bbacb1a4af5a17ac3143e1f77b287cc

45a941d046d5947eb49a09583f43a1c8e3e4096f08e13de142432183117377f3

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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