Which versions of sometestproxyywayle are malicious?

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

How do I remediate sometestproxyywayle if I installed it?

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

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

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

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

Malicious package

sometestproxyywayleRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8820

Immediate action

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

gem uninstall sometestproxyywayle

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f2435f079941905c406133f95b5893c415769a26942da0e2cb0aa53118dc6163

ffb58b06ed791218adb30e26e97995d757b7ad9ffe23fbc666cafd025a9cd5d3

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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