Cyber Threat Intelligence
CTI Academy Sponsor CTI Academy
TA
Ransomware Victim Technology

takt.be

Ransomware attack by Lockbit5 · Disclosed August 27, 2026 · 🇧🇪 Belgium

takt.be

Date Disclosed
Aug 27, 2026
2026
Threat Group
Lockbit5
354 total victims
Country
🇧🇪 Belgium
Industry
Technology

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 takt.be on its dark web leak site operated by Lockbit5 on 27 August 2026, revealing that the Belgian-based technology firm operates in the Technology sector.

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

Incident Analysis

takt.be was targeted by Lockbit5 ransomware, one of the most active ransomware groups in our database with 354 confirmed victims globally. The attack was disclosed on August 27, 2026, when takt.be appeared on the group's dark web leak site.

takt.be is based in Belgium , operating in the Technology sector. Belgium ranks #21 globally for ransomware attacks, with 135 victims in our database.

Sector context: Technology companies hold intellectual property, customer data, and source code — all highly valuable assets. A successful ransomware attack can also put downstream customers at risk through supply chain exposure.

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 6, 2026 16:00 UTC.

Frequently Asked Questions

Was takt.be attacked by ransomware?

Yes. takt.be was listed as a victim of the Lockbit5 ransomware group on August 27, 2026. The organisation is based in Belgium and operates in the Technology sector. The disclosure appeared on the group's dark web leak site.

Which ransomware group attacked takt.be?

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

When did the takt.be ransomware attack occur?

The ransomware attack on takt.be was disclosed on August 27, 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 takt.be ransomware attack?

The specific data stolen from takt.be 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 Technology organisation, takt.be likely held source code, intellectual property, and customer data.

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.