DisclosureLens
GLOBALMalwareTransportation & LogisticsTransportationRansomwareCl0pRansom DemandedActor NamedData Leak ThreatenedData PublishedHigh

Linfox

bd_280de246e33314bc · schema v1 · pii pii-v1

Severity

High

Discovered

Filed

Jan 24, 2025

To disclose

Affected

Not disclosed

Confidence

50%
Full breach record for Linfox2 incidents on file

Threat-actor claim — not a regulatory filing

This row is a claim by the ransomware group Cl0p 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-01-24

Source: Ransomware.live

Post text · scraped from the leak site

Linfox is a leading logistics company headquartered in Melbourne, Australia. Established in 1956, they provide comprehensive supply chain solutions across the Asia-Pacific region with customized logistic service operations. Their services include warehousing, distribution, temperature-controlled storage, and supply chain consulting. Linfox also puts special focus on sustainability and safety within their operations.

Incident timeline — mostly unverified

? — ?

Breach window unknown

Jan 24, 2025

Claim posted

No filing yet · watching

Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.

Claim → filing

Compliance clock

Not assessable

Tracked as a single-filing incident — the only disclosure on record for this event so far.Unverified claimView incident

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.

No regulatory filing corroborates this yet — it is the attacker's own assertion. Watch this entity to be notified the moment a filing corroborates or contradicts it.

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.