Bayside Interiors
bd_5f7e905f5d0da236 · schema v1 · pii pii-v1
Full breach record for Bayside Interiors →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group LockBit 3.x 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.
Sanctions caution: LockBit 3.x carries US sanctions exposure — OFAC has designated the group or its operators. Public reporting is permitted (informational-materials exemption, 50 U.S.C. § 1702(b)(3)) — but any payment or material support may violate sanctions. Consult counsel before engaging.
Source: Ransomware.live
Post text · scraped from the leak site
Bayside started in 1984 as a Northern California family owned and operated business, offering services in Southern California since 2006. Nearly 40 years later, we have proudly grown to serve customers across the nation and around the globe. Headquar...
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Apr 8, 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 (3) · sorted by filing gap
- California State AGbd_a63142bda8c59bdf2023-07-26 · +109dVerified by operator
- Indiana State AGbd_ef9c5d8c14ecf77d2023-07-26 · +109dVerified
- Maine State AGbd_f0f55cf1b84229362023-07-26 · +109dVerified
Filing propagation · 4 filings · 3 states
View merged incident ↗Pattern: first filing Apr 8, last Jul 26 (ME) — a 109-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.