Aviareps
bd_745a79849520ccd9 · schema v1 · pii pii-v1
Full breach record for Aviareps →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Black Basta 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
AVIAREPSWith our global group of local sales, marketing and communications experts, we have the structures in place to let us launch targeted local initiatives, as well as multi-market campaigns that benefit from the powerful synergies across our business. Our teams have their finger on the pulse of the industry and can effortlessly adapt our clients’ message to the subtle nuances of their region and culture.In doing so, we go beyond promotion: We influence where people go, how they get there, and what they do when they’re there.**SITE:**www.aviareps.com Address 110 Landsberger StrasseMunich, Bavaria80339, Germany
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
May 17, 2023
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.