Skip to content
Cyber Threat
CTI Academy Sponsor CTI Academy
Ransomware victim Financial Services

capitalbankhaiti.biz

Listed by Lockbit5 on · organisation based in Haiti

capitalbankhaiti.biz

Disclosed
Oct 8, 2026
Leak-site listing date
Threat group
Lockbit5
385 victims listed
Country
Haiti
#119 most targeted
Sector
Financial Services

ThreatAI analysis

Compiled from this incident record and the threat intelligence profile for Lockbit5. Figures and technique mappings are quoted from the source data, not inferred.

Lockbit5 dark web leak site listed capitalbankhaiti.biz on October 8, 2026; the Financial Services firm provides traditional and online banking services.

About capitalbankhaiti.biz

Capital Bank SA provides a comprehensive range of traditional and online banking services tailored f...

Source record: ransomware.live

About the Lockbit5 group

LockBit 5.0 ("ChuongDong") emerged in September 2025 as the group's resurgence following the February 2024 law enforcement takedown, introducing cross-platform payloads targeting Windows, Linux, and VMware ESXi with enhanced evasion capabilities and continuing the RaaS affiliate model of its predecessors. Lockbit5 has listed 374 victims since April 2023.

Incident analysis

capitalbankhaiti.biz was listed by Lockbit5 ransomware, a group with 385 victims recorded in this database. The listing appeared on the group's leak site on October 8, 2026.

capitalbankhaiti.biz is based in Haiti and operates in the Financial Services sector. Haiti ranks #119 worldwide for ransomware disclosures, with 4 victims in this database.

Sector context. Financial sector organisations are targeted for their access to funds, sensitive financial data, and the reputational damage a public breach can cause. Regulatory requirements also increase recovery costs.

Lockbit5 typically follows a double extortion model: data is exfiltrated from the victim's systems before files are encrypted, so the victim faces two demands at once — pay to restore access, and pay to keep stolen data unpublished. The leak site, where this listing appeared, is the lever for the second demand.

Source. Public leak-site disclosures aggregated via the ransomware.live API. The disclosure date is when the listing was published, which can differ from the date of compromise. This site does not publish or link to stolen data. Last updated .

Frequently asked questions

Was capitalbankhaiti.biz attacked by ransomware?

Yes. capitalbankhaiti.biz was listed as a victim of the Lockbit5 ransomware group on October 8, 2026. The organisation is based in Haiti and operates in the Financial Services sector. The disclosure appeared on the group's dark web leak site.

Which ransomware group attacked capitalbankhaiti.biz?

capitalbankhaiti.biz was attacked by Lockbit5 ransomware. Lockbit5 is one of the most active ransomware groups, having claimed 385 victims globally. The group typically employs a double-extortion model: encrypting the victim's files and threatening to publish stolen data.

When did the capitalbankhaiti.biz ransomware attack occur?

The ransomware attack on capitalbankhaiti.biz was disclosed on October 8, 2026. This date reflects when the victim was published on the threat group's leak site, which may differ from the actual date of initial compromise.

What data was stolen in the capitalbankhaiti.biz ransomware attack?

The specific data stolen from capitalbankhaiti.biz has not been independently verified by this platform. Ransomware groups typically exfiltrate data before encrypting systems and use the threat of publication to pressure victims. As a Financial Services organisation, capitalbankhaiti.biz likely held financial records, client data, and transaction histories.

How can organisations protect against Lockbit5 attacks?

To defend against Lockbit5 and similar threat actors, organisations should: maintain regular offline backups tested for restoration; implement network segmentation to limit lateral movement; deploy multi-factor authentication on all remote access; use endpoint detection and response (EDR) tools; conduct regular phishing and security awareness training; and monitor threat intelligence feeds for indicators of compromise (IOCs) associated with active groups.