Which versions of slwproxy174pom are malicious?

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

How do I remediate slwproxy174pom if I installed it?

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

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

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

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

Malicious package

slwproxy174pomRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8797

Immediate action

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

gem uninstall slwproxy174pom

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9ec624ae3fb3253301ce88fabfcfe2fc275cff7793eeb2a0e25e3a1f81f21eb8

58d1d366bca33284fa07454e9b9ad7d3891b58921ce772dfde36e00853f03615

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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