Find Great People
bd_6d28c5dcd24524d4 · schema v1 · pii pii-v1
Full breach record for Find Great People →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Akira 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
Post text · scraped from the leak site
Find Great People is a talent acquisition and human resources con sulting firm. Confidentiality agreements, confidential clients da ta, employment documents filled with full set of personal inform ation and other interesting files. Everything is about 32Gb.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jul 31, 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?Ransomware claims (1)
- Leak Siteakirabd_7b0bad9a0e3cd7cd2024-11-19 · +110dVerified by operator
Regulatory filings (5) · sorted by filing gap
- Indiana State AGbd_4c0137f919d783fb2024-10-01 · +61dVerified
- Maine State AGbd_8d05af71016c21892024-10-01 · +61dVerified by operator
- Massachusetts State AGbd_8f4ddefd26404c1f2024-10-01 · +61dVerified by operator
- South Carolina State AGbd_b83954dd660831512024-10-02 · +62dVerified
Show 1 more filing ↓Show fewer ↑up to 67d gap
- New Hampshire State AGbd_9a7dc2cc6d1fc9562024-10-07 · +67dVerified
Filing propagation · 6 filings · 5 states
View merged incident ↗Pattern: first filing Jul 31, last Oct 7 (NH) — a 67-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
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.
akira
According to ransomware.live, The Akira ransomware group is said to have emerged in March 2023, and there's much speculation about its ties to the former CONTI ransomware group. It's worth noting that with the end of CONTI's operation, several affiliates migrated to independent campaigns such as Royal, BlackBasta, and others. According to some reports, Akira affiliates also work with other ransomware operations, such as Snatch and BlackByte, as an open directory of tools used by an Akira operator was identified, which also had connections to the Snatch ransomware. The first version of the Akira ransomware was written in C++ and appended files with the '.akira' extension, creating a ransom note named 'akira_readme.txt,' partially based on the Conti V2 source code. However, on June 29, 2023, a decryptor for this version was reportedly released by Avast. Subsequently, a version was released that fixed the decryption flaw on July 2, 2023. Since then, the new version is said to be written in Rust, this time called 'megazord.exe,' and it changes the extension to '.powerranges' for encrypted files. Most of Akira's initial access vectors use brute-force attempts on Cisco VPN devices (which use single-factor authentication only). Additionally, exploitation of CVEs: CVE-2019-6693 and CVE-2022-40684 for initial access has been identified. Source: https://github.com/crocodyli/ThreatActors-TTPs