aasm-history (RubyGems) · Malicious Code
Affects aasm-historySource GCVE Database
Malicious package : remove aasm-history and rotate any secrets on hosts that installed it.
Data as of 18 Jul 2026, 19:25 UTC
Malicious package
Published to RubyGems · OSV MAL-2024-6315
What to do
Remove aasm-history from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
RubyGemsaasm-historypkg:gem/aasm-historyOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: ghsa-malware (8aafb886e7062b5dcce8799a264500766a916c3cb0047d39ab3e1490858442a4) --- Credit: [OpenSSF](https://github.com/ossf/malicious-packages) ([source](https://github.com/ossf/malicious-packages/blob/9fbb5fba02ba2f02395d3d2d43c31b2c482b7a9d/osv/malicious/rubygems/aasm-history/MAL-2024-6315.json))