GLOBALMalwareFinancial ServicesFinanceRansomwareLapsus$LapsusRansom DemandedActor NamedMedium
AYA BANK
bd_ac40aef90aa4a577 · schema v1 · pii pii-v1
Full breach record for AYA BANK →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Lapsus$ 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: Financial ServicesDiscovered: 2026-06-23
Source: Ransomware.live
Post text · scraped from the leak site
Everything for the main platform is there. Full dump and PII data's. If AYA Bank dont contact us or pay the ransom we will start sale
Tracked as a single-filing incident — the only disclosure on record for this event so far.Unverified claimView incident
No regulatory filing corroborates this yet. If an SEC 8-K, state-AG notice, or victim statement lands, DisclosureLens will merge it into an incident and link it here.
Source provenance
- Source URL
- https://www.ransomware.live/id/QVlBIEJBTktAbGFwc3VzJA==
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
- Filed at
- Jun 23, 2026
- Raw hash
- 9381d4bf5be54f9d22e54981aee5e0138922189c3133b2283ca3f0d8efe42d31
Reporting entity
- Name
- lapsus$
Victim entity
- Name
- AYA BANKnorm: aya bank
- Industry
- Financial Servicesllm
What this source establishes
- Source ceiling
- A leak-site claim can't tell us: discovery date · materiality · notification · affected count · confirmed data types · compliance clock. These stay blank until a regulatory filing or victim disclosure lands.
- Attack vector
- Ransomware· lapsus$
- Threat actor
- Lapsus$ExternalFinancial
Compliance
- Compliance flags
- — (clock not assessable for this source)
Extraction provenance
- Status
- No extraction artifact recorded for this disclosure.