Bangladesh Krishi Bank was listed on 06 July 2023 by the alphv ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). alphv listed 417 organizations that month and 717 in total.
- Listed 1232 days ago.
- 904 organizations were listed by all groups in July 2023, see the month.
- 72 in Financial Services that month.
- 1 in BD that month.
Updated 2026-11-19 06:47 UTC. Data: public leak-site listings. How we work.
Bangladesh Krishi Bank
Threat Group Post & Evidence
- Listed by
- ALPHV / BlackCat 717 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.
The group's leak-site address is on paid plans
Free accounts see who listed this organization, when, and what the post claims. The address of the group's own page is shown to license-key holders. If you have a key, see what a license key adds.
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.
We are here to inform you about data breach which took place at the "Bangladesh Krishi Bank" network on June 21th 2023. As a result of this breach our team had downloaded over 170Gb of sensitive data from this network. Also we have encrypted all servers and data stored there. We have infiltrated Krishi Bank network and stayed there for 12 days, it was enough to study their documentation and download everything was needed. Here is a quick scope of data we have downloaded: - financial data (accounts, statements, payments, taxes, etc) - employees data (emails, passports, labor papers, contracts, etc) - sql backup dated 6/19/2023 Unfortunatelly, for "Bangladesh Krishi Bank" top management, they decided not to negotiate recovery of stolen data's. We have placed a strong backdoor tools within Krishi Bank's network, so we can always return there and do whatever we want. IT-management of this ba…
Show the full post (1426 characters)
We are here to inform you about data breach which took place at the "Bangladesh Krishi Bank" network on June 21th 2023. As a result of this breach our team had downloaded over 170Gb of sensitive data from this network. Also we have encrypted all servers and data stored there. We have infiltrated Krishi Bank network and stayed there for 12 days, it was enough to study their documentation and download everything was needed. Here is a quick scope of data we have downloaded: - financial data (accounts, statements, payments, taxes, etc) - employees data (emails, passports, labor papers, contracts, etc) - sql backup dated 6/19/2023 Unfortunatelly, for "Bangladesh Krishi Bank" top management, they decided not to negotiate recovery of stolen data's. We have placed a strong backdoor tools within Krishi Bank's network, so we can always return there and do whatever we want. IT-management of this bank does not have enough qualification and skills to protect their data. "All the contributors and investors who used to store their money at the Bangladesh Krishi Bank should withdraw their money within 7 days after this message being send, in case if they don't want to lost all their money." - this message will be send to all contacts and emails we will found in "Bangladesh Krishi Bank" documents, in case if "Bangladesh Krishi Bank" top-management will not contact us within 72 hours starting July 8th 2023.
Amounts as written
- 170Gb
Kinds of data mentioned
-
Tax records
“…we have downloaded: - financial data (accounts, statements, payments, taxes, etc) - employees data (emails, passports, labor papers, contracts, etc) - sql backup dated…”
-
Identity documents
“…(accounts, statements, payments, taxes, etc) - employees data (emails, passports, labor papers, contracts, etc) - sql backup dated 6/19/2023 Unfortunatelly, for "Bangladesh…”
-
Email and communications
“…financial data (accounts, statements, payments, taxes, etc) - employees data (emails, passports, labor papers, contracts, etc) - sql backup dated 6/19/2023 Unfortunatelly, for…”
-
Employee and HR records
“…downloaded: - financial data (accounts, statements, payments, taxes, etc) - employees data (emails, passports, labor papers, contracts, etc) - sql backup dated 6/19/2023 Unfortunatelly,…”
-
Contracts and legal files
“…payments, taxes, etc) - employees data (emails, passports, labor papers, contracts, etc) - sql backup dated 6/19/2023 Unfortunatelly, for "Bangladesh Krishi Bank" top management,…”
-
Databases and backups
“…etc) - employees data (emails, passports, labor papers, contracts, etc) - sql backup dated 6/19/2023 Unfortunatelly, for "Bangladesh Krishi Bank" top management, they decided…”
Plain-English summary AI-written
The group says it downloaded sensitive Bangladesh Krishi Bank data, including financial records, employee information and a SQL backup, and encrypted servers and stored data.
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 Bangladesh Krishi 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 Bangladesh Krishi 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 Bangladesh Krishi 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.
- Expect convincing phishing Messages that quote real orders, invoices or names are more likely after a leak. Tell finance and the help desk to treat any request from, or about, this company with extra care. Why: The post names: email and communications, identity documents, employee and hr records.
- Verify payment-detail changes by phone Confirm any change to bank details or any urgent invoice with a number you already hold, not one in the message. Why: The post names: tax records.
- 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 Bangladesh Krishi 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 Bangladesh Krishi Bank
First 24 hours
- Reset credentials and sessions Force password, API-key and session-token resets for the accounts the post suggests were exposed, enforce phishing-resistant MFA, and revoke OAuth/SSO grants issued before the listing date. Why: The post names: identity documents, email and communications.
Within 3 days
- Support affected individuals Identify the employees or customers whose identity data may be in scope and offer identity-protection or credit monitoring; brief the help desk on likely phishing. Why: The post names: employee and hr records, identity documents.
- 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 for mailbox compromise Audit mailbox rules, forwarding and delegated access, rotate mail-admin credentials and move DMARC to p=reject to limit follow-on phishing. Why: The post names: email and communications.
- Size the exposure against your own systems Inventory which systems hold data of the kind and volume claimed, so notification and legal decisions rest on your records rather than the group's figures. Why: The post claims: 170Gb. Treat group figures as unverified.
- Lock down exposed admin, VPN and SSO panels Restrict by IP allow-list or a zero-trust proxy and require MFA. Why: A passive scan found 1 critical panel(s) reachable from the internet.
- 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.
-
Check the ways alphv is reported to get in
Check these first; they are how the group is reported to work in general.
- Affiliates impersonate IT or help-desk staff by phone or SMS to obtain credentials, and use the Evilginx2 framework to capture MFA codes and session cookies. (update of Feb 2024)
Within 30 days
- Review privileged and contract material Ask counsel which contracts and privileged files are named, and whether client or partner confidentiality terms oblige you to tell them. Why: The post names: contracts and legal files.
- Watch for tax-filing fraud Tell your tax advisers and, where available, tax authorities so fraudulent filings made with exposed identifiers can be caught early. Why: The post names: tax records.
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
Listing severity score (heuristic)
75/100 • ELEVATEDA heuristic built from sector, group, data volume and claim details. It is not evidence that a breach occurred or a measure of harm.
External Attack Surface Profile
ASM IntelligenceRun a free passive scan on your own domain to see what an attacker can see from the outside.