FA
Ransomware Victim

fabrity.local

Ransomware attack by Warlock ยท Disclosed November 6, 2025 ยท ๐Ÿ‡ต๐Ÿ‡ฑ Poland

fabrity.local

Date Disclosed
Nov 6, 2025
2025
Threat Group
Warlock
78 total victims
Industry
โ€”

ThreatAI Analysis

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

About the Warlock group

The Warlock ransomware and operator(s) are believed to be attributed to Storm-2603, a China-based threat actor who is also known to have deployed LockBit ransomware. There's also a crossover between victims with Black Basta. Both are RaaS and have a long list of known and unknown affiliates. Having said that, this is possibly an affiliate (likely a cybergroup) of both of those groups. The Alliance & Association would technically be Encryptor Sharing, but this is realistically more of an "Old Affiliate" that created their own ransomware encryptor and operation. Warlock has listed 78 victims since April 2025.

Vulnerabilities Warlock is recorded exploiting

5 of these 5 are in the CISA Known Exploited Vulnerabilities catalog, 3 of them recorded by CISA as used in ransomware campaigns. CVEs attributed to Warlock across its reported activity. There is no indication that any of these was involved in the fabrity.local incident โ€” the source data does not record an entry point.

Incident Analysis

fabrity.local was targeted by Warlock ransomware, one of the most active ransomware groups in our database with 78 confirmed victims globally. The attack was disclosed on November 6, 2025, when fabrity.local appeared on the group's dark web leak site.

fabrity.local is based in Poland . Poland ranks #29 globally for ransomware attacks, with 117 victims in our database.

Warlock 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 19, 2026 00:00 UTC.

Frequently Asked Questions

Was fabrity.local attacked by ransomware?

Yes. fabrity.local was listed as a victim of the Warlock ransomware group on November 6, 2025. The organisation is based in Poland. The disclosure appeared on the group's dark web leak site.

Which ransomware group attacked fabrity.local?

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

When did the fabrity.local ransomware attack occur?

The ransomware attack on fabrity.local was disclosed on November 6, 2025. 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 fabrity.local ransomware attack?

The specific data stolen from fabrity.local 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. Sensitive business data was likely targeted.

How can organisations protect against Warlock attacks?

To defend against Warlock 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.