Rite Aid Corporation
bd_e574aa49cc367deb · schema v1 · pii pii-v1
Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group RansomHub on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jul 11, 2024
Claim posted
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (10) · sorted by filing gap
- Montana State AGbd_207d49685b6d18df2024-07-15 · +4dVerified
- California State AGbd_4ecedaca9ccb33242024-07-15 · +4dVerified
- South Carolina State AGbd_5dc09de29a4959d72024-07-15 · +4dVerified
- Massachusetts State AGbd_666fbc5335615f552024-07-15 · +4dVerified
Show 6 more filings ↓Show fewer ↑up to 4d gap
- Oregon State AGbd_889db9b4ae4e89f72024-07-15 · +4dVerified
- Vermont State AGbd_a417384d21d4f0c12024-07-15 · +4dVerified
- Washington State AGbd_b4a3decb3cef61212024-07-15 · +4dVerified
- Indiana State AGbd_c885a91972cf27f32024-07-15 · +4dVerified
- Delaware State AGbd_e9b3a4c075cb2fda2024-07-15 · +4dVerified
- New Hampshire State AGbd_eefa59da13cd37842024-07-15 · +4dVerified
Showing first 10 of 12 linked disclosures.
Filing propagation · 11 filings · 10 states
View merged incident ↗Cascade drawn from the first 10 linked disclosures of 12 — the full spread may be wider.
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.
ransomhub
According to ransomware.live, The group emerged in mid-February 2024 and has already listed several organizations as alleged victims of their attacks, resulting from extortion through encryption and data leaks. The announcement of the sale of the new Ransomware-as-a-Service (RaaS) by RansomHub was published on one of the Russian-origin forums used by cybercrime to advertise malicious services, known as RAMP4U (or RAMP). A user with the nickname and persona of 'koley' announced the affiliate program on February 2, 2024. In the new RaaS announcement, it was mentioned that the money laundering operation of the paid ransoms is the responsibility of the affiliate. This means that all communication and sending of the decryptor to the victim are done through chat. The split of this RaaS would be 90% of the value for the affiliate and 10% for the developer, who in this case would be the persona of Koley. Furthermore, according to the publication, the ransomware payload is written in Golang language, uses the asymmetric algorithm based on x25519, and encryption algorithms AES256, ChaCha20, and xChaCha20, standing out for its speed. The encryption is obfuscated using AST. The payload would support network propagation and encryption of data both in secure and local mode. According to Koley, the ransomware is designed to operate on platforms such as Windows, Linux, and ESXi, as well as other architectures such as ARM and MIPS. As pointed out by the panel and already highlighted by the intelligence team, Koley stated that the panel uses a .onion domain, allowing the affiliate to organize and manage targets and chat rooms, view access logs, automatically respond when offline, and create private blog pages. Source: https://github.com/crocodyli/ThreatActors-TTPs