DisclosureLens
GLOBALMalwareTransportation & LogisticsTransportationRansomwareInc RansomRansom DemandedActor NamedData Leak ThreatenedData PublishedHigh

Teamsters Local 175

bd_91f264bdb400ed71 · schema v1 · pii pii-v1

Severity

High

Discovered

Filed

Jan 29, 2025

To disclose

Affected

Not disclosed

Linked

7 filings

Confidence

50%

Threat-actor claim — not a regulatory filing

This row is a claim by the ransomware group INC Ransom 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: 2025-02-22

Source: Ransomware.live

Post text · scraped from the leak site

PROUDLY SERVING TEAMSTER MEMBERS AND THEIR FAMILIES IN WEST VIRGINIA, KENTUCKY, OHIO AND VIRGINIA SINCE 1940 Saturday, October 16th (next Saturday) at 10:00 a.m. at 267 Staunton Ave., South Charleston, WV 25309. Biscuits will be available. AHF members joined together for a Unity Rally for each shift to show their solidarity and support for a new better contract. Negotiations have been ongoing with a company that bought the plant sometime last year. They stand together stong and we stand with them. Teamsters Local 175 joins West Virginia AFL-CIO March 12, 2019 Facebook Twitter Email Google+ Share In an encouraging sign of unity within the West Virginia labor movement, the International Brotherhood of Teamsters Local 175 made a unanimous decision this past Saturday to affiliate with the West Virginia AFL-CIO.

Incident timeline — mostly unverified

? — ?

Breach window unknown

Jan 29, 2025

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 7 about the same incident.View merged incident

Linked disclosures

Why this link?

Ransomware claims (1)

Regulatory filings (5) · sorted by filing gap

Show 1 more filingup to 409d gap

Filing propagation · 6 filings · 4 states

View merged incident ↗
Leak SiteJan 29 · first · this page

Pattern: first filing Jan 29, last Mar 14 (MA) — a 409-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.