Which versions of aasm-history are malicious?

The following RubyGems versions of aasm-history are flagged malicious: 0.1.3. Treat any of these as compromised.

How do I remediate aasm-history if I installed it?

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

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

Yes — aasm-history is associated with the RLMA-2024-05122, RLUA-2024-09641 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-history across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for aasm-history (version 0.1.3).

Malicious package

aasm-historyRubyGems

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

Malicious code in aasm-history (RubyGems)

MAL-2024-6315

Immediate action

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

gem uninstall aasm-history

Malicious versions

1 flagged

0.1.3

Indicators of compromise (SHA-256)

bb004330f6305ff241191b26709982e7da379c4d038b8b01a5e69677066b9020

0207dfefe37cd2a45039e13cd917c3eca52f8cc875cc03a8fef99584b70346d0

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05122RLUA-2024-09641

References

blog.reversinglabs.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks aasm-history-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