The National Association of Home Builders
bd_482afc9f9eed6cac · schema v1 · pii pii-v1
Full breach record for The National Association of Home Builders →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
The National Association of Home Builders represents the largest network of craftsmen, innovators and problem solvers dedicated tobuilding and enriching communities. "Building Homes, Enriching Communities, Changing Lives" is the motto of the company. They really change lives because of a neglecting attitude to their own security, so you will be able to do whatever you want with their clients, employees and others info soon. Stay tuned.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
May 30, 2023
Claim posted
—
Corroborated · see linked filings
This record's own dates cannot anchor compliance clocks; see the linked filings.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (5) · sorted by filing gap
- Indiana State AGbd_51d1a96330e36e262024-02-16 · +262dVerified
- Vermont State AGbd_854c27ea357c74502024-02-29 · +275dCandidate
- Massachusetts State AGbd_4cc7e49d3b839dde2024-03-01 · +276dVerified by operator
- Maine State AGbd_cde12f17e57692d92024-03-01 · +276dVerified
Show 1 more filing ↓Show fewer ↑up to 280d gap
- New Hampshire State AGbd_b7b7dfc373dd19792024-03-05 · +280dVerified
Filing propagation · 5 filings · 5 states
View merged incident ↗Pattern: first filing Feb 16 (IN), last Mar 5 (NH) — a 18-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