Which versions of living-dead are malicious?

The following RubyGems versions of living-dead are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate living-dead if I installed it?

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

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

Yes — living-dead is associated with the RLMA-2024-05780, RLUA-2024-10300, RLUA-2026-08508 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 living-dead across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for living-dead (version 0.0.1).

Malicious package

living-deadRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in living-dead (RubyGems)

MAL-2024-6974

Immediate action

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

gem uninstall living-dead

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

4cf7feb85561c810a7c9e9e9a57f983f7b8402d4e1093646098c15f322960401

aea4f32b04edab6e68ff6beb8109f0a8b7d308cd34970fc8b6d445dd77962ce3

d5df6a2f15eabf761d69a8b538403cd3f7600d65aa2d425115e3cc9e1b5ccfa4

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05780RLUA-2024-10300RLUA-2026-08508

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks living-dead-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