Which versions of damn_weather are malicious?

The following RubyGems versions of damn_weather are flagged malicious: 0.1.3. Treat any of these as compromised.

How do I remediate damn_weather if I installed it?

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

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

Yes — damn_weather is associated with the RLMA-2024-05657, RLUA-2024-10176, RLUA-2026-07955 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 damn_weather across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for damn_weather (version 0.1.3).

Malicious package

damn_weatherRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

damn_weather is a confirmed malicious RubyGems package (MAL-2024-6851) that executes malicious code on install (malicious version 0.1.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in damn_weather (RubyGems)

MAL-2024-6851

Immediate action

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

gem uninstall damn_weather

Malicious versions

1 flagged

0.1.3

Indicators of compromise (SHA-256)

feb65a69b628188e01e526cacaabab1a8345b889662f49ac7b73363a64d727dc

d1a99860e008a2c90a210cbd6cf1c0766b1b32e11889e80824fa566e3637df7d

fb1d7e631e3e7e3a8442b4f8ba3925d26d16bbac0b43a691a3e412196eafe1bf

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05657RLUA-2024-10176RLUA-2026-07955

References

Credits

ReversingLabs · finder

Detect & block this

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