Skip to navigation

Threat reportRansomwareTL-2026-6653

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

highACTIVE

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. First disclosed .

Key facts

IdentifiersTL-2026-6653
SeverityHIGH
First disclosed
Affected productsMicrosoft Windows (encryptor targets Windows hosts and reachable network shares)
AttributionHYFLOCK (low confidence)
MalwareNishi, hyflock
ToolsTor Browser, qTox
MITRE ATT&CK techniquesT1027.009 Embedded Payloads, T1036.005 Match Legitimate Resource Name or Location, T1053.005 Scheduled Task, T1135 Network Share Discovery, T1490 Inhibit System Recovery, T1587.001 Malware, T1657 Financial Theft, T1685 Disable or Modify Tools
MotivationFINANCIAL
Target sectorsmanufacturing, business services, government administration, retail, telecoms, technology, financial services, health, education, energy
Target regionsGlobal, North America, Europe, Asia, Africa, 005 - South America
Detection rules9 (1 shown free)
Sources8 cited sources

Detection coverage

As of 2026-11-22, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-6653 across Splunk SPL, Microsoft KQL and Sigma, covering 17 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: HYFLOCK Ransomware .hyflock_claim Share-Coordination Artifact

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

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

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

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. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple and Gold in full, 2 calls a day on a free account)
  • HYFLOCK Ransomware Config, Key-Backup Artifacts and Sample Hash · unlock with TL Creds
  • HYFLOCK Ransomware Ransom Note and [indicator] Mass File Encryption · unlock with TL Creds
  • HYFLOCK Ransomware Security Tool Interference · unlock with TL Creds
  • HYFLOCK Ransomware Scheduled Task Registered for ProgramData Update-Lookalike Binary · unlock with TL Creds
  • HYFLOCK Ransomware Network Share Discovery and SMB Fan-Out · unlock with TL Creds
  • HYFLOCK Ransomware Operator Negotiation Channel - qTox, Tor and Leak-Site Onion · unlock with TL Creds
  • HYFLOCK Ransomware Staged [indicator] Encryptor and Scheduled-Task Persistence · unlock with TL Creds
  • HYFLOCK Ransomware Recovery Inhibition - Shadow Copy and Backup Destruction · unlock with TL Creds

Indicators of compromise

As of 2026-11-22, Threadlinqs Intelligence tracks 17 indicators of compromise for TL-2026-6653.

Sample indicators (3 of 17)

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

Defanged, TLP:CLEAR. Full set of 17 indicators: unlock with TL Creds.

17 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

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 techniques by tactic:

Defense Evasion

T1027.009 Embedded Payloads; T1036.005 Match Legitimate Resource Name or Location

Execution

T1053.005 Scheduled Task

Persistence

T1053.005 Scheduled Task

Discovery

T1135 Network Share Discovery

Impact

T1490 Inhibit System Recovery; T1657 Financial Theft

Resource Development

T1587.001 Malware

defense-impairment

T1685 Disable or Modify Tools

Remediation

Immediate actions

  • Hunt for HYFLOCK artifacts: scheduled tasks launching an eu.exe copy staged under a directory resembling an Edge/software update component, eu.cfg, system_config.dat, .hyflock_claim, and files renamed to .locked or .locked_<identifier>
  • Search endpoints for the reported SHA-256 80c474154b1df816cf513ae978936875b6dd77f47ef6bce78dda83ab1b89525b
  • Alert on ransom notes named 'How to Restore My Files.html'
  • Verify offline, immutable backups and test restore of critical systems

Workarounds

  • If encrypted files are found, preserve disk images and encrypted samples: the 2026-10-17 build leaves files above 4 KB partially unencrypted, which may allow partial recovery of content

Longer-term hardening

  • Deploy EDR with behavioral ransomware detection (mass file renames, new scheduled tasks, share enumeration)
  • Restrict SMB write access and segment file shares to limit network-share encryption
  • Monitor leak sites and the group's promised write-up for victim confirmation
  • Enforce MFA and credential hygiene, since infostealer-derived access is common among tracked victims

Affected and fixed versions

  • Microsoft — Windows (encryptor targets Windows hosts and reachable network shares)
    Vulnerable versions: Not specified in sources

Timeline

  • HYFLOCK first appears on underground forums advertising a Ransomware-as-a-Service platform (Check Point; month-level precision).
  • Earliest analyzed sample already contains a Windows ransomware core written in Rust (Check Point; month-level precision).
  • PCrisk and Gridinsoft publish removal guides for a HYFLOCK sample using the .locked extension and note 'How to Restore My Files.html'; a July build with a separate loader is described by Check Point.
  • Ransomware.live records the estimated attack date of the earliest listed HYFLOCK victim (YYC Advisors, Malaysia).
  • Eight victim claims appear on the HYFLOCK leak site across manufacturing, business services, government, retail and telecommunications (unverified claims).
  • Date of the second October build, a standalone Rust encryptor that stages itself under an update-lookalike directory, registers a scheduled task and encrypts only the first 4,096 bytes of larger files.
  • Check Point Exposure Management publishes its analysis of four HYFLOCK build generations and encryption weaknesses.
  • Four new victim posts the same day (Morocco, Colombia, India, Taiwan), with more on 2026-11-19 and 2026-11-22.
  • HYFLOCK posts an unnamed victim described as ranked in the top 30 of the Fortune 500 and promises a detailed account the next day; the claim is unverified.

Sources cited

Drafted by the Threadlinqs research pipeline from 8 sources; published ; last updated —.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats