Which versions of moving-average are malicious?

The following RubyGems versions of moving-average are flagged malicious: 0.1.1. Treat any of these as compromised.

How do I remediate moving-average if I installed it?

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

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

Yes — moving-average is associated with the RLMA-2024-05796, RLUA-2024-10317, RLUA-2026-08601 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 moving-average across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for moving-average (version 0.1.1).

Malicious package

moving-averageRubyGems

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

Malicious code in moving-average (RubyGems)

MAL-2024-6990

Immediate action

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

gem uninstall moving-average

Malicious versions

1 flagged

0.1.1

Indicators of compromise (SHA-256)

4291e8096ff71cf136bd4cc22ec2af339a5d9cb040a3067c21bb6ddb84d92f1b

a6cd81953e58a961f0ce1136099e1b5439b681aa8575d3acd90edb88aa799219

ff5ad4d04edec1f391b5b1d4e8142ed9272e081dbb874a02b6a17b5ade067b58

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05796RLUA-2024-10317RLUA-2026-08601

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks moving-average-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