Which versions of wurl-aws-s3 are malicious?

The following RubyGems versions of wurl-aws-s3 are flagged malicious: 0.3.1. Treat any of these as compromised.

How do I remediate wurl-aws-s3 if I installed it?

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

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

Yes — wurl-aws-s3 is associated with the RLMA-2024-05851, RLUA-2024-10372, RLUA-2026-10073 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 wurl-aws-s3 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for wurl-aws-s3 (version 0.3.1).

Malicious package

wurl-aws-s3RubyGems

wurl-aws-s3 is a confirmed malicious RubyGems package (MAL-2024-7047) that executes malicious code on install (malicious version 0.3.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in wurl-aws-s3 (RubyGems)

MAL-2024-7047

Immediate action

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

gem uninstall wurl-aws-s3

Malicious versions

1 flagged

0.3.1

Indicators of compromise (SHA-256)

f6900e5cc4a57014ac725c0fe73fc33e49b3ab1a465e03923f1b95d854e77f06

c6fb1a65108ed9e66c1bf4b26172f69d67ec354e016e5ba78325bf9b5f67b900

2a177db4d55afdb735daa26977f1af6600ebe3a7174281db966f402538dd2e5a

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for wurl-aws-s3 (version 0.3.1).
If you installed it — respond
Remove wurl-aws-s3 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 wurl-aws-s3 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. wurl-aws-s3 on RubyGems has been identified as a malicious package (version 0.3.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-05851RLUA-2024-10372RLUA-2026-10073

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks wurl-aws-s3-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