Which versions of deriving-license are malicious?

The following RubyGems versions of deriving-license are flagged malicious: 0.3.1. Treat any of these as compromised.

How do I remediate deriving-license if I installed it?

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

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

Yes — deriving-license is associated with the RLMA-2024-05667, RLUA-2024-10186, RLUA-2026-07972 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 deriving-license across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for deriving-license (version 0.3.1).

Malicious package

deriving-licenseRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

deriving-license is a confirmed malicious RubyGems package (MAL-2024-6861) that executes malicious code on install (malicious version 0.3.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in deriving-license (RubyGems)

MAL-2024-6861

Immediate action

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

gem uninstall deriving-license

Malicious versions

1 flagged

0.3.1

Indicators of compromise (SHA-256)

17b8f79b94191ab1d7fa9e78f569e9127ee10ac889a88bb3fb40cda8ec0a6b2f

b1d5e0562d4144736e0eb22a10d40b9b9e4381b56e9b1507e592808bd2a7e289

fac8c26d8208213e4fea746954880bc50f6824ae2e171612a3bfd949fa753081

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05667RLUA-2024-10186RLUA-2026-07972

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks deriving-license-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