# Hyflock Ransomware Group Claims Attack on Unnamed Fortune 500 Top-30 Company

> On 2026-11-22 the HYFLOCK ransomware-as-a-service group listed an unnamed victim on its leak site, described as a company ranked among the top 30 of the Fortune 500, and promised a detailed account the next day. The claim is unverified. The victim, sector, country and intrusion vector are all unstated.

- **Published:** 2026-11-22T09:36:49Z
- **Last reviewed:** 2026-11-22T09:36:49Z
- **Canonical:** https://intel.threadlinqs.com/threat/TL-2026-6653
- **Card image:** https://intel.threadlinqs.com/og/threat/TL-2026-6653.png
- **ID:** TL-2026-6653
- **Severity:** HIGH
- **Category:** RANSOMWARE
- **Status:** ACTIVE
- **Actor:** HYFLOCK
- **Detections:** 9 (1 shown free below) · **IOCs:** 17 (3 shown free below)

## Description

Ransomware.live recorded a new HYFLOCK leak-site post on 2026-11-22 at 09:22 UTC titled 'A Ransomware Attack on a Company Ranked Among the Top 30 in the Fortune 500'. The post text says only: 'We'll be posting a detailed account of this incident tomorrow, including some tongue-in-cheek commentary, so stay tuned.' No victim name, sector, country, data sample, ransom amount or intrusion vector is given, and the tracker's exposure report (ParanoidLab) shows 0 passwords and 0 cookies for the entry. This is an unverified actor claim; the stated scale of the victim has not been confirmed by any independent source or by the purported victim.

HYFLOCK is a relatively new ransomware-as-a-service operation. Check Point Exposure Management (published 2026-11-04) reports it first surfaced on underground forums in March 2026, advertising a RaaS platform whose recruitment posts promoted encryption performance, access procurement, technical assistance and shared negotiation tools. Check Point traced four build generations between April and October 2026: (1) an April Windows ransomware core written in Rust; (2) a July build delivered by a separate loader carrying configuration and key material on the same Rust foundation; (3) an early-October Go-based carrier that extracts and launches a revised payload and attempts background execution via a scheduled task; and (4) a 2026-10-17 standalone Rust encryptor that stages a copy of itself under a directory resembling a legitimate software-update component, registers a scheduled task, and processes network shares. By October the operators had announced 'version 2.0'.

Encryption characteristics reported by Check Point and Cryptika for the 2026-10-17 build: 16-byte symmetric keys with AES counter mode, RSA protection of recovery material, a 556-byte trailer holding metadata and a wrapped key (marker HFLKEY01), and encryption of only the first 4,096 bytes of larger files (14 of 17 validated files; three smaller files were fully encrypted). Researchers recovered 73 CRC-valid internal components from seven encrypted Office files without a key, but did not recover plaintext keys or the RSA private key and developed no general decryptor. An earlier October build had a processing defect that could permanently discard portions of a file. Other sources report different details for earlier samples: PCrisk and Gridinsoft describe the extension .locked, the note 'How to Restore My Files.html' and a note that claims HC-128 encryption and contact over qTox, whereas a May 2026 recruitment pitch cited AES-128-CTR plus RSA-4096. Gridinsoft notes the July sample has not been proven to be the RaaS locker. Domain-wide propagation via Group Policy was disabled in the recovered configuration and was not observed; use of vulnerable drivers to disable security tools and persistence after remote-desktop sessions end were advertised but not verified. Researchers did not establish victims' initial compromise routes.

Leak-site activity: Ransomware.live lists 23 victims (first estimated attack date 2026-09-09, 12 in the current month, 17 countries, single leak site on Tor), including entries from 2026-11-18 to 2026-11-22 across Dominican Republic, Vietnam, France, Morocco, Colombia, India and Taiwan. Other trackers give different counts (Breachsense 14 as of Nov 10; VULONE 32-35), and the group's claims may include unverified or fabricated listings. Ransomware.live also reports the group's average attack-to-claim delay is 9.6 days and its leak-site uptime is low (27.5% over 30 days). The operator's claimed LockBit/Qilin experience is self-reported and was not corroborated. No BeaconBeagle correlation was possible: the only network indicator is a Tor onion address, and no clearnet IPs or domains have been published.

Defender guidance: treat this as a monitoring item. Hunt for the file-system and scheduled-task artifacts below, and do not assume any specific organization is affected until the group's promised write-up or a victim statement is available.

## MITRE ATT&CK

- T1587.001 Malware
- T1053.005 Scheduled Task
- T1053.005 Scheduled Task
- T1036.005 Match Legitimate Resource Name or Location
- T1027.009 Embedded Payloads
- T1685 Disable or Modify Tools
- T1135 Network Share Discovery
- T1490 Inhibit System Recovery
- T1657 Financial Theft

## Free detection (Splunk SPL, Microsoft KQL, Sigma)

**HYFLOCK Ransomware .hyflock_claim Share-Coordination Artifact** (`TL-2026-6653-SPL-003`)

Detects creation of the .hyflock_claim marker file that the 2026-10-17 HYFLOCK build writes during network-share encryption to coordinate which shares are already being processed (Cryptika IOC table). Hits on either the file server (Security 5145 detailed file share audit) or the encrypting host (Sysmon 11) indicate active share encryption.

- **Languages:** Splunk SPL, Microsoft KQL, Sigma
- **ATT&CK:** T1135, T1486, T1021.002
- **Data sources:** windows_security, WinEventLog:Security, sysmon, SecurityEvent, DeviceFileEvents
- **Severity:** critical
- **Confidence:** high

### Splunk SPL

```spl
earliest=-24h ((index=wineventlog sourcetype="WinEventLog:Security" EventCode=5145 RelativeTargetName="*.hyflock_claim") OR (index=sysmon sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=11 TargetFilename="*.hyflock_claim")) | eval src=coalesce(IpAddress, host), actor=coalesce(SubjectUserName, User), path=coalesce(ShareName, TargetFilename) | stats count dc(path) as distinct_paths values(path) as paths values(actor) as actors min(_time) as first_seen by src, host | convert ctime(first_seen) | table src host actors distinct_paths paths first_seen count
```

### Microsoft KQL

```kql
union isfuzzy=true
    (DeviceFileEvents
        | where Timestamp > ago(24h)
        | where FileName endswith ".hyflock_claim"
        | project Timestamp, DeviceName, ActionType, FileName, FolderPath, InitiatingProcessFileName, InitiatingProcessFolderPath, InitiatingProcessAccountName),
    (SecurityEvent
        | where TimeGenerated > ago(24h)
        | where EventID == 5145 and RelativeTargetName endswith ".hyflock_claim"
        | project Timestamp = TimeGenerated, DeviceName = Computer, ActionType = "ShareFileAccess", FileName = RelativeTargetName, FolderPath = ShareName, InitiatingProcessFileName = IpAddress, InitiatingProcessFolderPath = "", InitiatingProcessAccountName = SubjectUserName)
```

### Sigma

```yaml
title: HYFLOCK Ransomware .hyflock_claim Share Coordination File Created
id: 6c1f0a52-3b7e-4d49-9a1e-6653a0000003
status: experimental
description: Detects creation of the .hyflock_claim file used by the HYFLOCK October 2026 Rust encryptor to coordinate network-share encryption.
references:
    - https://www.cryptika.com/hyflock-ransomware-encrypts-only-first-4kb-of-larger-files-leaves-parts-of-victims-files-accessible/
author: Threadlinqs Team
date: 2026/11/22
tags:
    - attack.discovery
    - attack.t1135
    - attack.impact
    - attack.t1486
    - attack.lateral-movement
    - attack.t1021.002
logsource:
    category: file_event
    product: windows
detection:
    selection:
        TargetFilename|endswith: '.hyflock_claim'
    condition: selection
falsepositives:
    - Security researchers detonating HYFLOCK samples in a lab
level: critical
```

**Known false positives:**

- Malware analysis sandboxes or lab hosts detonating HYFLOCK samples

**Tuning notes:** Event 5145 requires the Detailed File Share audit subcategory enabled on file servers (high volume; scope to key servers). Exclude sandbox hostnames. Any true hit should trigger immediate host isolation and share lockdown.

### 8 more detection rules (Splunk SPL, Microsoft KQL, Sigma), unlock with TL Creds

- HYFLOCK Ransomware Config, Key-Backup Artifacts and Sample Hash (locked: unlock with TL Creds)
- HYFLOCK Ransomware Ransom Note and [indicator] Mass File Encryption (locked: unlock with TL Creds)
- HYFLOCK Ransomware Security Tool Interference (locked: unlock with TL Creds)
- HYFLOCK Ransomware Scheduled Task Registered for ProgramData Update-Lookalike Binary (locked: unlock with TL Creds)
- HYFLOCK Ransomware Network Share Discovery and SMB Fan-Out (locked: unlock with TL Creds)
- HYFLOCK Ransomware Operator Negotiation Channel - qTox, Tor and Leak-Site Onion (locked: unlock with TL Creds)
- HYFLOCK Ransomware Staged [indicator] Encryptor and Scheduled-Task Persistence (locked: unlock with TL Creds)
- HYFLOCK Ransomware Recovery Inhibition - Shadow Copy and Backup Destruction (locked: unlock with TL Creds)

Sign up free to unlock the detection rules: https://threadlinqs.com/?modal=signup

## Sample indicators (3 of 17)

Defanged, TLP:CLEAR.

- Domain: `yhgphvfgaecacgtlbn67u7yfhafe6evnj4gs4s2oyb3hzjnlhq45azqd[.]onion`
- URL: `hxxps://www[.]ransomware[.]live/id/QSBSYW5zb213YXJlIEF0dGFjayBvbiBhIENvbXBhbnkgUmFua2VkIEFtb25nIHRoZSBUb3AgMzAgaW4gdGhlIEZvcnR1bmUgNTAwQEhZRkxPQ0s`
- File hash: `80c474154b1df816cf513ae978936875b6dd77f47ef6bce78dda83ab1b89525b`

Full set of 17 indicators unlocks with TL Creds: https://threadlinqs.com/tl-creds

## Sources

- [Ransomware.live victim entry: A Ransomware Attack on a Company Ranked Among the Top 30 in the Fortune 500 (Hyflock)](https://www.ransomware.live/id/QSBSYW5zb213YXJlIEF0dGFjayBvbiBhIENvbXBhbnkgUmFua2VkIEFtb25nIHRoZSBUb3AgMzAgaW4gdGhlIEZvcnR1bmUgNTAwQEhZRkxPQ0s)
- [Ransomware.live group page: Hyflock](https://www.ransomware.live/group/HYFLOCK)
- [Check Point: HYFLOCK Ransomware Evolves with New Builds and Encryption Weaknesses](https://blog.checkpoint.com/security/hyflock-ransomware-evolves-with-new-builds-and-encryption-weaknesses/)
- [GBHackers: Hackers Develop New HYFLOCK Ransomware That Encrypts Files and Attempts to Block Recovery](https://gbhackers.com/hyflock-ransomware/)
- [Cryptika: HYFLOCK Ransomware Encrypts Only First 4KB of Larger Files](https://www.cryptika.com/hyflock-ransomware-encrypts-only-first-4kb-of-larger-files-leaves-parts-of-victims-files-accessible/)
- [VULONE: Hyflock Ransomware Group profile](https://vulone.com/ransomware/hyflock)
- [Gridinsoft: HYFLOCK Ransomware: .locked File Recovery and Removal](https://blog.gridinsoft.com/hyflock-ransomware/)
- [PCrisk: HYFLOCK ransomware removal guide](https://www.pcrisk.com/removal-guides/35596-hyflock-ransomware)

## Full data

The other 8 detection rules (Splunk SPL / Microsoft KQL / Sigma) unlock with TL Creds; a free account includes daily creds: https://threadlinqs.com/?modal=signup
Indicator values unlock with TL Creds, at a lower price on Red and Purple; AI agents can query rules and IOCs through the Threadlinqs MCP server (Purple and Gold in full, 2 calls a day on a free account): https://intel.threadlinqs.com/mcp

Canonical: https://intel.threadlinqs.com/threat/TL-2026-6653
