Which versions of enpit-weather are malicious?

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

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

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

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

Yes — enpit-weather is associated with the RLMA-2024-05697, RLUA-2024-10216, RLUA-2026-08064 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 enpit-weather across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for enpit-weather (version 0.1.0).

Malicious package

enpit-weatherRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in enpit-weather (RubyGems)

MAL-2024-6891

Immediate action

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

gem uninstall enpit-weather

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

11b93ca07238a9421d7a63eb58530ad02070f34e36b958cc60d5099e83df9f4b

880fb933bcd3a29d3e3f7e3711c437bab3d2b3a5519cc405f8eff991c751db19

50bf012c9b7b7f13bf3d296ec45af7a03256e30c3a1628e77fe08c1ed7835d67

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05697RLUA-2024-10216RLUA-2026-08064

References

Credits

ReversingLabs · finder

Detect & block this

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