Threat reportThreat IntelligenceTL-2026-4458
Shellcode execution via Windows thread-pool wait callbacks (CreateThreadpoolWait) - public technique write-up
A public blog post by cocomelonc (2026-10-07), archived in the Malpedia library, demonstrates running shellcode by registering it as the callback of a Windows thread-pool wait object (CreateThreadpoolWait/SetThreadpoolWait) and triggering it with SetEvent. The article names no malware family, actor, CVE or in-the-wild use; it is an educational PoC. First disclosed .
Key facts for CreateThreadpoolWait shellcode execution
| Identifiers | TL-2026-4458 |
|---|---|
| Also known as | Malware development trick 67, CreateThreadpoolWait shellcode execution |
| Severity | LOW |
| First disclosed | |
| Exploitation status | Public proof-of-concept exploit |
| Affected products | Microsoft Windows (x64) thread-pool API |
| Malware | Assembly |
| Tools | nasm -f bin meow.asm -o meow.bin, x86_64-w64-mingw32-gcc |
| MITRE ATT&CK techniques | T1055 Process Injection, T1106 Native API, T1587.001 Malware, T1620 Reflective Code Loading |
| Motivation | UNKNOWN |
| Detection rules | 9 (1 shown free) |
| Sources | 6 cited sources |
Detection coverage for CreateThreadpoolWait shellcode execution
As of 2026-10-26, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-4458 across Splunk SPL, Microsoft KQL and Sigma, covering 10 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: Thread-Pool Wait Shellcode PoC Binaries Executed (hack.exe / hack2.exe / hack3.exe)
Detects execution of the example binaries from the cocomelonc 'Malware development trick 67' write-up (hack.exe, hack2.exe, hack3.exe), which dispatch shellcode via CreateThreadpoolWait/SetThreadpoolWait/SetEvent. Flags whether the image runs from a user-writable path. Educational PoC with no in-the-wild use, so hits are most likely lab, red-team or copycat builds.
- Languages: Splunk SPL, Microsoft KQL, Sigma
- ATT&CK: T1106, T1587.001, T1204.002, T1027
- Data sources: sysmon (Event ID 1), microsoft_defender_for_endpoint DeviceProcessEvents, windows_security 4688
- Severity: medium
- Confidence: medium
Splunk SPL
index=windows sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=1 earliest=-24h
| where match(Image,"(?i)\\\\hack[23]?\.exe$")
| eval tl_user_writable=if(match(Image,"(?i)\\\\(users|temp|programdata)\\\\"),"yes","no"), tl_threat="TL-2026-4458"
| stats count min(_time) as first_seen max(_time) as last_seen values(CommandLine) as commandlines values(ParentImage) as parents values(Hashes) as hashes by host user Image tl_user_writable tl_threat
| convert ctime(first_seen) ctime(last_seen)Microsoft KQL
DeviceProcessEvents
| where Timestamp > ago(24h)
| where FileName in~ ("hack.exe", "hack2.exe", "hack3.exe")
| extend UserWritablePath = FolderPath has_any (@"\Users\", @"\Temp\", @"\ProgramData\")
| project Timestamp, DeviceName, AccountName, FileName, FolderPath, ProcessCommandLine, InitiatingProcessFileName, InitiatingProcessCommandLine, SHA256, UserWritablePath
| order by Timestamp descSigma
title: Thread-Pool Wait Shellcode PoC Binary Execution (hack.exe family)
id: 5b1c7a52-3f0e-4c8d-9a41-6d2e8f3b1a01
status: experimental
description: Detects execution of hack.exe, hack2.exe or hack3.exe, the example binaries from the public CreateThreadpoolWait shellcode write-up (Malware development trick 67).
references:
- https://cocomelonc.github.io/malware/2026/10/07/malware-tricks-67.html
- https://github.com/cocomelonc/meow/tree/master/2026-10-07-malware-tricks-67
- https://learn.microsoft.com/en-us/windows/win32/api/threadpoolapiset/nf-threadpoolapiset-createthreadpoolwait
- https://attack.mitre.org/techniques/T1055/
author: AII-Detector — ThreadLinqs Intelligence
date: 2026-10-26
tags:
- attack.execution
- attack.t1106
- attack.resource-development
- attack.t1587.001
- attack.user-execution
- attack.t1204.002
- attack.defense-evasion
- attack.t1027
logsource:
category: process_creation
product: windows
detection:
selection:
Image|endswith:
- '\hack.exe'
- '\hack2.exe'
- '\hack3.exe'
condition: selection
falsepositives:
- Unrelated software or games that ship an executable named hack.exe
- Security training labs and red-team exercises reproducing the public PoC
level: medium
Known false positives:
- Unrelated tools named hack.exe
- Authorized lab or red-team replication of the public PoC
Tuning notes: Filename matching is trivially evaded by renaming; pair with the memory-allocation and unbacked-thread detections. Restrict to user-writable paths in production and allow-list approved red-team hosts. Add SHA256 values once hashes of your own builds are known.
- Thread-Pool Wait PoC Artifacts Written to Disk ([indicator] / [indicator] / hack*.c) · unlock with TL Creds
- Private Memory Allocated Then Made Executable by User-Path Process (Thread-Pool Callback Staging) · unlock with TL Creds
- Retrieval of the Thread-Pool Wait PoC Source (cocomelonc Repository / Blog) · unlock with TL Creds
- Shellcode Loader Build Toolchain Commands (nasm [indicator] / MinGW [indicator] -luser32) · unlock with TL Creds
- PowerShell Referencing CreateThreadpoolWait and SetThreadpoolWait · unlock with TL Creds
- Full-Access Process Handle From User-Writable-Path Process (Injection Precursor) · unlock with TL Creds
- Rare User-Writable-Path Binary Loading user32.dll (MessageBox Payload Prerequisite) · unlock with TL Creds
- Remote Thread With Unbacked Start Module (Adjacent Injection Execution) · unlock with TL Creds
Indicators of compromise for CreateThreadpoolWait shellcode execution
As of 2026-10-26, Threadlinqs Intelligence tracks 10 indicators of compromise for TL-2026-4458.
Sample indicators (2 of 10)
- URL:
hxxps://github[.]com/cocomelonc/meow/tree/master/2026-10-07-malware-tricks-67 - URL:
hxxps://cocomelonc[.]github[.]io/malware/2026/10/07/malware-tricks-67.html
Defanged, TLP:CLEAR. Full set of 10 indicators: unlock with TL Creds.
How CreateThreadpoolWait shellcode execution works
The write-up 'Malware development trick 67' shows how shellcode can be dispatched through the Windows thread-pool wait API instead of CreateThread or similar direct execution primitives. The flow is: create trigger and completion events with CreateEventW; register a callback address and context pointer with CreateThreadpoolWait; associate the wait object with the trigger event via SetThreadpoolWait; then call SetEvent so a thread-pool worker thread invokes the callback. SetEventWhenCallbackReturns, WaitForThreadpoolWaitCallbacks and CloseThreadpoolWait are used for completion and cleanup.
Two examples are published. Example 1 (hack.c) allocates memory with VirtualAlloc, copies in a 73-byte returning x64 wait-callback payload assembled from meow.asm with NASM, changes protection to PAGE_EXECUTE_READ, flushes the instruction cache and registers the buffer address as the thread-pool callback. The payload shows a MessageBox ('Meow-meow!', caption '=^..^=') and must return to the thread pool rather than terminate the process; it receives API addresses and the completion event handle through the context pointer (RDX). Example 2 (hack2.c) implements the callback as a normal compiled C function (meow_callback) to show the same dispatch mechanism without handwritten assembly. Binaries were built with x86_64-w64-mingw32-gcc and tested on a Windows x64 lab; the author reports an ANY.RUN sandbox run with no threats detected.
No in-the-wild exploitation, CVE, actor, malware family or network infrastructure is reported. The author notes that thread-pool callbacks are ordinary Windows functionality used by many legitimate programs, so analysis should focus on the callback address (for example a dynamically allocated executable region rather than a module code section), the context data, and the triggering event. Because no network IOCs exist, no BeaconBeagle correlation was applicable.
MITRE ATT&CK techniques by tactic:
Defense Evasion
T1055 Process Injection; T1620 Reflective Code Loading
Privilege Escalation
Execution
Resource Development
Remediation for CreateThreadpoolWait shellcode execution
Immediate actions
- No patch applies; this is documented use of legitimate Windows thread-pool functionality
- Add the published example file names and API sequence to hunting watchlists for lab and sandbox triage
Workarounds
- Enable memory-protection mitigations (for example arbitrary code guard and dynamic code restrictions) for high-value processes where compatible
Longer-term hardening
- Deploy EDR with telemetry on VirtualAlloc/VirtualProtect followed by thread-pool callback registration
- Inspect thread-pool wait callback addresses for pointers into private executable memory rather than image-backed code
- Review the callback context data and the signaling event when triaging suspicious thread-pool activity
Affected and fixed versions
- Microsoft — Windows (x64) thread-pool API
Vulnerable versions: Technique abuses standard Windows functionality; no specific vulnerable version identified
Timeline of CreateThreadpoolWait shellcode execution
- cocomelonc publishes 'Malware development trick 66: TLS callbacks before main', an earlier callback-based execution write-up in the same series
- cocomelonc publishes 'MacOS malware persistence 13', listed by Malpedia as a related article
- cocomelonc publishes 'Malware analysis: part 12', listed by Malpedia as a related article
- Article added to the Malpedia library with no linked malware families or actors
- Example code (locked-ioc-10, hack2.c, hack3.c, locked-ioc-9, locked-ioc-8 and compiled executables) published in the cocomelonc/meow GitHub repository
- cocomelonc publishes 'Malware development trick 67: Run shellcode via CreateThreadpoolWait' with C and assembly examples
Sources cited for CreateThreadpoolWait shellcode execution
- Malpedia library entry for the cocomelonc article malpedia.caad.fkie.fraunhofer.de · Research · 2026-10-07
- Microsoft Learn: CreateThreadpoolWait function (threadpoolapiset.h) Microsoft · Vendor report
- MITRE ATT&CK T1055 Process Injection MITRE · Research
- MITRE ATT&CK T1106 Native API MITRE · Research
- cocomelonc/meow - 2026-10-07-malware-tricks-67 example code GitHub · Proof of concept · 2026-10-07
- Malware development trick 67: Run shellcode via CreateThreadpoolWait. C and assembly examples cocomelonc.github.io · Blog · 2026-10-07
Previous and next in threat intel
Drafted by the Threadlinqs research pipeline from 6 sources; published ; last updated —.