Which versions of aasm-active-fedora are malicious?

The following RubyGems versions of aasm-active-fedora are flagged malicious: 0.1.2. Treat any of these as compromised.

How do I remediate aasm-active-fedora if I installed it?

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

If aasm-active-fedora 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 aasm-active-fedora part of a known attack campaign?

Yes — aasm-active-fedora is associated with the RLMA-2024-05121, RLUA-2024-09640 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 aasm-active-fedora across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for aasm-active-fedora (version 0.1.2).

Malicious package

aasm-active-fedoraRubyGems

aasm-active-fedora is a confirmed malicious RubyGems package (MAL-2024-6314) that executes malicious code on install (malicious version 0.1.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in aasm-active-fedora (RubyGems)

MAL-2024-6314

Immediate action

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

gem uninstall aasm-active-fedora

Malicious versions

1 flagged

0.1.2

Indicators of compromise (SHA-256)

754feeb9cf480801471a59b169bbc59d3d848a1976d51de7f114ad69ce172571

240ee9cdd28dd0358bd8ed4d96829553ffcb148f2dcea714fea47ce4944db409

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05121RLUA-2024-09640

References

blog.reversinglabs.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks aasm-active-fedora-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