โšก
Diago Lima
  • โ“This Blog Has Moved
  • ๐ŸŒŠA Deep Dive Into Exploiting Windows Thread Pools
    • Introduction
    • Attacking Worker Factories
    • Attacking I/O Ports
    • Attacking Timer Queues
    • Closing Remarks
    • Github Repository
  • ๐Ÿ‘๏ธAbusing TLS Callbacks For Payload Execution
    • Introduction
    • Payload Execution
  • โ˜•Using Object Files For Malware Development
    • Introduction
    • The Why
    • The Common Object File Format
    • Loading An Object File
    • Closing Remarks
Powered by GitBook
On this page
  1. A Deep Dive Into Exploiting Windows Thread Pools

Closing Remarks

Thread Pool Injection is a powerful and innovative execution technique, and fixes one of the toughest issues many malware developers have faced for quite some time: the need to avoid creating remote threads.

While it certainly isnโ€™t a standalone technique per se, it can work very effectively alongside other malware techniques to accomplish an unprecedented level of stealth and evasion. The technique, in my opinion, marks a turning point in the continuous cat-and-mouse game between security solutions and their adversaries.

I believe itโ€™s quite powerful, but it isnโ€™t without its weaknesses. Defenders should configure their security solutions, if possible, to look for handle duplication of the three main handle types targeted in this technique: TpWorkerFactory, IoCompletion, and IRTimer. EDR drivers receiving callbacks for duplication of these handles should immediately investigate the source of the request, as this is highly irregular. In my opinion, this is the most reliable method of catching this technique.

PreviousAttacking Timer QueuesNextAbusing TLS Callbacks For Payload Execution

Last updated 1 year ago

๐ŸŒŠ