Which versions of current-weather are malicious?

The following RubyGems versions of current-weather are flagged malicious: 0.0.4. Treat any of these as compromised.

How do I remediate current-weather if I installed it?

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

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

Yes — current-weather is associated with the RLMA-2024-05653, RLUA-2024-10172, RLUA-2026-07951 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 current-weather across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for current-weather (version 0.0.4).

Malicious package

current-weatherRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in current-weather (RubyGems)

MAL-2024-6847

Immediate action

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

gem uninstall current-weather

Malicious versions

1 flagged

0.0.4

Indicators of compromise (SHA-256)

726d31b20bf0fceede13e57b2e29dd3acd46a214e56f61a8925a72430f19e9a5

7849c2e5f5b0f36eb5c969c162d4e8153e5f33a557ca505e6b5f69f7f16c6803

78440568f1bd26032ea38643f66a9965db1fb4b41ff238b84b54cfa75f1b5776

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05653RLUA-2024-10172RLUA-2026-07951

References

Credits

ReversingLabs · finder

Detect & block this

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