SI
Ransomware Victim Financial Services

siinqeebank.com

Ransomware attack by Lockbit5 ยท Disclosed September 21, 2026 ยท ๐Ÿ‡ธ๐Ÿ‡ด SO

siinqeebank.com

Date Disclosed
Sep 21, 2026
2026
Threat Group
Lockbit5
365 total victims
Industry
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 listed siinqeebank.com on its dark web leak site on 21 September 2026; Siinqee Bank is a licensed Ethiopian financial institution that offers inclusive and innovative banking services.

About siinqeebank.com

Siinqee Bank is a licensed Ethiopian financial institution that offers inclusive and innovative bank...

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 355 victims since April 2023.

Incident Analysis

siinqeebank.com was targeted by Lockbit5 ransomware, one of the most active ransomware groups in our database with 365 confirmed victims globally. The attack was disclosed on September 21, 2026, when siinqeebank.com appeared on the group's dark web leak site.

siinqeebank.com is based in SO , operating in the Financial Services sector. SO ranks #159 globally for ransomware attacks, with 1 victims in our 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 employs a double extortion model: first exfiltrating sensitive data from the victim's systems, then deploying ransomware to encrypt files. Victims face two simultaneous threats โ€” paying to restore access and paying to prevent publication of stolen data. The group's leak site publishes victim names and exfiltrated data as leverage.

Data source: This incident record is sourced from public ransomware group leak site disclosures aggregated via the ransomware.live API. Disclosure date reflects when the victim was published on the leak site, which may differ from the initial date of compromise. This platform does not publish or link to stolen data. Last data update: Sep 23, 2026 08:00 UTC.

Frequently Asked Questions

Was siinqeebank.com attacked by ransomware?

Yes. siinqeebank.com was listed as a victim of the Lockbit5 ransomware group on September 21, 2026. The organisation is based in SO and operates in the Financial Services sector. The disclosure appeared on the group's dark web leak site.

Which ransomware group attacked siinqeebank.com?

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

When did the siinqeebank.com ransomware attack occur?

The ransomware attack on siinqeebank.com was disclosed on September 21, 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 siinqeebank.com ransomware attack?

The specific data stolen from siinqeebank.com 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, siinqeebank.com 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.