Ransomware Tracker by ExposureDrift
Dashboard / Victims / AYA BANK

AYA BANK was listed on 23 June 2026 by the lapsus$ ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). lapsus$ listed 3 organizations that month and 25 in total.

  • Listed 149 days ago.
  • 708 organizations were listed by all groups in June 2026, see the month.
  • 35 in Financial Services that month.
  • 1 in MM that month.

Updated 2026-11-19 05:42 UTC. Data: public leak-site listings. How we work.

AYA BANK corporate emblem
Listed by lapsus$ Disclosed: 2026-06-23 19:52 UTC

AYA BANK

ayabank.com Financial Services MM

Threat Group Post & Evidence

Listed by
Lapsus$ 25 listings in total

The listing states no data size and no ransom demand.

No capture of the original post

We only show a screenshot when we captured the group's own page ourselves. For this listing we have not, so none is shown.

What the group says it holds

Taken from the group's own post. Ransomware Tracker by ExposureDrift has not seen the data and cannot confirm any of this.

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

Kinds of data mentioned

  • Databases and backups

    “Full dump and PII data's. If AYA Bank dont contact us or pay the ransom we will start sale”

Plain-English summary AI-written

The group says it has a full dump and personal information for the main platform.

Written by an AI model (openai/gpt-6-luna) from the post above. It can contain mistakes: rely on the quote, not the summary.

What to do about this listing

Choose who you are. Each step shows why it appears and, where we have one, its source. General guidance, not legal or incident-response advice.

If you work with AYA BANK (customer, supplier or partner)

Within 3 days

  • Do not open the group's page or download the data Do not visit the leak site or download files from a listing. Holding stolen data can be unlawful, and the files can carry malware. Wait for the company's own notice. Why: A safety rule for any leak listing.
  • Ask AYA BANK directly Write to your contact and ask whether your data, or your access to their systems, is in scope, and ask for a written statement. Your contract or data-protection law may oblige them to tell you if your data is affected: check the notification clause. Why: A listing is only the group's claim; the company is the one who can confirm what was taken.
  • Review what AYA BANK can reach of yours List the accounts, API keys, VPN or SSO connections and shared mailboxes this company has with you. Rotate the keys you gave them and remove access they do not need. Why: Access a supplier holds is how a listing about them can become a problem for you.
  • Check software and integrations you take from them If you run their software or call their API, check that updates come through the usual channel and rotate the keys and tokens you hold for it. Why: The post names: databases and backups.

Within 30 days

  • Keep watching AYA BANK A supplier's listing can change after the first sighting: the group can add data, change the status or publish. Add the company to your supplier list to be told, and check your own domain too. Why: A listing is a moving claim, not a single event. Add to your supplier list Check your own domain
If you are AYA BANK

Within 3 days

  • Rotate database and cloud access Rotate database and cloud-storage keys, review public bucket and snapshot sharing, turn on object-level audit logging and keep backup encryption keys separate. Why: The post names: databases and backups.
  • Check regulatory and stakeholder notification duties No country is recorded for this listing. Identify the data-protection and contractual duties that apply where the affected people live, and ask counsel. General guidance, not legal advice. Why: The listing records no country.
General readiness for any ransomware claim (not about this listing)
  • Offline, immutable backups and a restore drill Keep backups outside domain-admin reach and practise a restore; a leak does not remove the risk of re-encryption. Why: General practice for any ransomware claim; not specific to this listing.
  • Look for mass file access and unusual outbound transfers Review EDR, proxy and identity logs for bulk reads, archive creation and large uploads to file-sharing services. Why: General practice for any ransomware claim; not specific to this listing.
  • Phishing-resistant MFA on remote access Enforce MFA on VPN, SSO and admin panels, and retire password-only or SMS-based remote access. Why: General practice for any ransomware claim; not specific to this listing.

Listing details

Resolved Domain ayabank.com
Industry Vertical Financial Services
Country MM
Enrichment Status ENRICHED

Listing severity score (heuristic)

38/100 • LOW

A heuristic built from sector, group, data volume and claim details. It is not evidence that a breach occurred or a measure of harm.

1. Sector Criticality 10/30 pts
Commercial and general business
2. Group tier 10/25 pts
Tier 3: all other groups
3. Data Volume & PII Scope 10/25 pts
Baseline: no size or sensitive data named in the post
Formula: sector • group tier • data claimed (scaled to 100) Rule-based score

External Attack Surface Profile

ASM Intelligence
62/100 • HIGH
Last Audited: 2026-11-14 16:31 UTC Passive Recon
Total Network Assets 2
1 hosts • 1 unique IPs
0 cloud-hosted • 3 SaaS
Subdomain Assets 1
Critical Panels 0 (VPN/Admin/SSO)
Non-Prod / UAT 0 Staging/Dev
SaaS Ecosystem 3 Cloud Apps
Primary CSP SoftLayer Techno
Email Security Grade A (SPF/DMARC)
Open the full attack surface scan →
Is Your Organization Exposed?

Run a free passive scan on your own domain to see what an attacker can see from the outside.

Defense Telemetry

Passive DNS
Mail Gateway Microsoft 365 / Exchange Online
DNS Authority Authoritative DNS (com)
Edge CDN / Shield None
SPF Record Configured
DMARC Policy Enforced
Public DNS records only • no port scanning

More Claims by lapsus$

All →
INGKA GROUP
Retail & E-Commerce 2026-06-13 10:02 UTC
GITHUB INTERNAL
Technology 2026-06-13 10:02 UTC
MERCOR
Technology 2026-05-31 20:24 UTC
MAPFRE ASSURANCE
Financial Services 2026-05-31 20:24 UTC
VODAFONE
Technology 2026-05-29 22:52 UTC
AXCERA TRADING
Professional Services 2026-05-10 13:22 UTC