TOPLIVO AD
bd_deed48767758795f · schema v1 · pii pii-v2
Full breach record for TOPLIVO AD →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group N0n 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.
Source: Ransomware.live
Post text · scraped from the leak site
fuel trading and construction materials · Bulgaria | The complete counterparty ledger of a fuel trading company: 694 companies with full legal names, addresses, managing persons, national company numbers, tax numbers and bank account details; More than 3,100 live customs and fuel movement documents from December 2025 through October 2026, and a 12 year archive of more than 46,000 documents from 2014 through 2025; Records of 611 drivers and 651 tanker trucks with registration plates; More than 2.6 million automated tank gauge readings from fuel storage tanks; Named staff accounts of the accounting system | [NOT PAID — EXPOSED]
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Oct 25, 2026
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
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.
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.