Which versions of wtestjsmfurlb are malicious?

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

How do I remediate wtestjsmfurlb if I installed it?

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

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

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

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

Malicious package

wtestjsmfurlbRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9489

Immediate action

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

gem uninstall wtestjsmfurlb

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f8b3ed898b99c81e969e6d19f8d9f5b229e6821c3cc30bfa1ecb99d132b24533

97cefaaee97d312c8c8b9d31147ba09853273b87c35c6e7e7ae887ae7a97ecef

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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