Some semi-samples Of Liberty X TMO cause we got yappatrons on twitter
bd_6d2ca0b5dd6cca6c · schema v1 · pii pii-v2
Full breach record for Some semi-samples Of Liberty X TMO cause we got yappatrons on twitter →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Byod 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
Lmao. Amusing tweet. However, nobody cares about Trump Mobile anymore, but you're mistaken if you think that is all we have or if they didn't get breached, or if that's what we were talking about. Sneak peek we guess, Knock yourself out.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Oct 8, 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.