Which versions of wptfrep are malicious?

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

How do I remediate wptfrep if I installed it?

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

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

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

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

Malicious package

wptfrepRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9483

Immediate action

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

gem uninstall wptfrep

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b9254e2d4469fa8a27d139392af554f72203f07ae38a1ac079c5ab082ad14c27

2d2199ad93b9664e103ebf960661e9b5e6fa4323409f6017410c6af12cb2565a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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