Which versions of curly-lib are malicious?

The following RubyGems versions of curly-lib are flagged malicious: 0.0.0, 0.1.0. Treat any of these as compromised.

How do I remediate curly-lib if I installed it?

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

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

Yes — curly-lib is associated with the RLMA-2024-05652, RLUA-2024-10171, RLUA-2026-07950 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 curly-lib across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for curly-lib (2 malicious versions).

Malicious package

curly-libRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

curly-lib is a confirmed malicious RubyGems package (MAL-2024-6846) that executes malicious code on install (malicious versions 0.0.0, 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in curly-lib (RubyGems)

MAL-2024-6846

Immediate action

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

gem uninstall curly-lib

Malicious versions

2 flagged

0.0.00.1.0

Indicators of compromise (SHA-256)

5d0f3c2e8268facff63418e486ef6790e0c73e7cc94d8302f180c83031e4fec4

44b748e1feca16bedc17e246378819233948cb9fe4ef5763c835cc191ae5e0b1

c58ef94465230e207ab285add6aa9f445df7afe9a365b141a8baeebfcbbe6c5b

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05652RLUA-2024-10171RLUA-2026-07950

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks curly-lib-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