DisclosureLens
GLOBALMalwareTransportation & LogisticsTransportationRansomwareBlackSuitRansom DemandedActor NamedData Leak ThreatenedData PublishedHigh

Liberty Lines

bd_51c4d50b0cdf8448 · schema v1 · pii pii-v1

Severity

High

Discovered

Filed

Mar 15, 2023

To disclose

Affected

Not disclosed

Linked

4 filings

Confidence

50%
Full breach record for Liberty Lines

Threat-actor claim — not a regulatory filing

This row is a claim by the ransomware group BlackSuit (formerly Royal) 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: Transportation/LogisticsDiscovered: 2023-03-15

Source: Ransomware.live

Post text · scraped from the leak site

For over 60 years Liberty Lines has been privileged to develop and operate one of the most effective and efficient Transit systems in the country. Today Liberty operates over 300 vehicles on 60 routes and carries almost 30 million passenger over 10 million miles annually. We believe our 700 union and non-union employees are the best transit workers in America. Our employees are our greatest asset and earn excellent wages, health and pension benefits. The Liberty workforce is foundational to the local economy.Since its meager beginnings in 1953 as a 4 vehicle operation, Liberty Lines has grown through merger and acquisition to become one of the largest privately owned transportation companies in New York State. Today, the company, which is headquarted in Yonkers, operates out of 2 state of the art facilities, employing approximately 610 union and 140 non-union employees and operating a fleet of 350 vehicles from 25 foot passenger vans, to 60 foot articulated and hybrid buses.

Incident timeline — mostly unverified

? — ?

Breach window unknown

Mar 15, 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

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 SiteMar 15 · first · this page

Pattern: first filing Mar 15, last May 15 (NH) — a 61-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 2023-06-12

blacksuit

According to ransomware.live, According to Trend Micro, this ransomware has significant code overlap with Royal Ransomware.

430 tracked hereFull profile →