NAI Earle Furman
bd_89acd33a79c23e73 · schema v1 · pii pii-v2
Full breach record for NAI Earle Furman →2 incidents on fileThreat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Secp0 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 reviewed dataset is a single-snapshot, single-volume file-server tree (E:/Shares, 1.36M paths) covering NAI Earle Furman's brokerage deals, property-management portfolio (MRI accounting), broker commissions, employee home directories, and the absorbed Croxton Gray firm's data...
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Sep 22, 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.
secp0
According to ransomware.live, Encrypted Extension: .vanhelsing, .vanlocker. Targets Windows Platform only