Foshee Architecture
bd_f8c0562613845fb8 · schema v1 · pii pii-v1
Full breach record for Foshee Architecture →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group INC Ransom 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
Foshee Architecture is a Montgomery, Alabama-based architecture firm specializing in comprehensive design services for a variety of sectors including multi-family housing, healthcare facilities, office spaces, retail, and restaurants. Founded by John H. Foshee, the firm utilizes a personalized design process informed by a rich family history in the construction industry. By collaborating with experts in engineering and other disciplines, they provide tailored architectural solutions that prioritize client objectives and budgets. Their extensive experience positions them to effectively manage complex projects while ensuring high standards of functionality and aesthetic appeal.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jan 10, 2026
Claim posted
—
No filing yet · watching
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
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.
No regulatory filing corroborates this yet — it is the attacker's own assertion. Watch this entity to be notified the moment a filing corroborates or contradicts it.
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.