Which versions of wandfossiltest are malicious?

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

How do I remediate wandfossiltest if I installed it?

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

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

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

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

Malicious package

wandfossiltestRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9206

Immediate action

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

gem uninstall wandfossiltest

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3da66a0ba0865183cbdac8112b30c33dbba5a0058dc1740ce61e1bfe0730c903

0872fc757233b949e32c2a903f08d02247cd34b1646dd771068233ae4f5c7ede

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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