Nachi America Inc
bd_9c7c532d54f52330 · schema v1 · pii pii-v1
Full breach record for Nachi America Inc →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Mountlocker 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
Sep 9, 2021
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 (3) · sorted by filing gap
- New Hampshire State AGbd_2da2cf68a3dda2432021-04-01 · +161dCandidate
- Massachusetts State AGbd_c0103221915472952021-04-01 · +161dVerified
- Indiana State AGbd_31aa6c87e99dc8282021-03-30 · +163dVerified
Filing propagation · 4 filings · 3 states
View merged incident ↗Pattern: first filing Mar 30 (IN), last Sep 9 — a 163-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.
mountlocker
According to ransomware.live, MountLocker operated as a ransomware-as-a-service from July 2020, using a standard developer/affiliate revenue split and leveraging compromised RDP credentials for initial access, propagating laterally via Windows Active Directory APIs and targeting over 2,600 file extensions.