MasterCorp
bd_f7a0a5ed0c870133 · schema v1 · pii pii-v1
Full breach record for MasterCorp →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Black Basta 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
MasterCorpBusiness Services · Tennessee, United States · 1,000 EmployeesHeadquarters 3505 N Main St, Crossville, Tennessee, 38555, United StatesPhone Number (931) 484-1752Website www.mastercorp.comRevenue $217.8MA leader in cleanliness since 1981, today MasterCorp is considered the most trusted name in hospitality services. We partner with premier resorts and developers nationwide and lead the industry, not only in size, but in innovation, performance, and customer satisfaction.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Apr 27, 2023
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 (2) · sorted by filing gap
- Vermont State AGbd_987c1d95566b0a3c2023-05-30 · +32dVerified
- Massachusetts State AGbd_e8cd3a1ed548572b2023-05-31 · +33dVerified by operator
Filing propagation · 3 filings · 2 states
View merged incident ↗Pattern: first filing Apr 27, last May 31 (MA) — a 33-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.