DisclosureLens
GLOBALMalwareHospitalityHospitalityRansomwareBianlianRansom DemandedActor NamedMedium

Eureka Casino Resort

bd_3eb60fbb2de14666 · schema v1 · pii pii-v1

Severity

Medium

Discovered

—

Filed

Dec 15, 2022

To disclose

—

Affected

Not disclosed

Linked

4 filings

Confidence

50%
Full breach record for Eureka Casino Resort →

Threat-actor claim — not a regulatory filing

This row is a claim by the ransomware group BianLian 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.

Group activity: Hospitality and TourismDiscovered: 2022-12-15
View aggregator listing on ransomware.liveView merged incident timeline

Source: Ransomware.live

Incident timeline — mostly unverified

? — ?

Breach window unknown

Dec 15, 2022

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

This filing is one of 4 about the same incident.View merged incident

Linked disclosures

Why this link?

Ransomware claims (1)

Regulatory filings (2) · sorted by filing gap

Filing propagation · 3 filings · 2 states

View merged incident ↗
Leak SiteDec 15 · first · this page
Vermont State AG+63d
California State AG+64d

Pattern: first filing Dec 15, last Feb 17 (CA) — a 64-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claimThis record

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filing

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

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.

About this groupFirst seen 2022-07-14

bianlian

According to ransomware.live, BianLian ransomware operations began in late 2021. The group practices multi-pronged extortion, demanding payment for a decryptor, as well as the non-release of stolen data. The ransomware group hosts a public, TOR-based, blog to post victim identities and stolen data. Somewhat unique to BianLian at the time of their launch was their inclusion of an I2P mirror for their blog.

578 tracked hereFull profile →