Exetools - [C++, WinAPI] Enigma HWID patcher with hardware breakpoints

Hey guys,
 
This is a small project I did for a friend some time ago, basically it's a DLL you inject into an engima process (by loader, or by inline) and it will put a hardware breakpoint somewhere and write a new HWID.
 
Attached the full source code, you have to manually find the HWID patch offset, but for someone who works with Enigma often this should be no problem...
 
Little hint:

Code:

0044F168 &#160;^\75 A7 &#160; &#160; &#160; &#160; &#160; JNZ SHORT test1.0044F111

0044F16A &#160; &#160;85F6 &#160; &#160; &#160; &#160; &#160; &#160;TEST ESI,ESI

0044F16C &#160;/-7E 25 &#160; &#160; &#160; &#160; &#160; JLE SHORT test1.0044F193            ; This is the patch place.

0044F16E &#160;|&#160;8D45 EC &#160; &#160; &#160; &#160; LEA EAX,DWORD PTR SS:[EBP-0x14]

0044F171 &#160;|&#160;66:83E3 0F &#160; &#160; &#160;AND BX,0xF

0044F175 &#160;|&#160;0FB7D3 &#160; &#160; &#160; &#160; &#160;MOVZX EDX,BX

0044F178 &#160;|&#160;B9 04F24400 &#160; &#160; MOV ECX,test1.0044F204 &#160; &#160; &#160; &#160; &#160; &#160; &#160;; ASCII "ABCDEF1234567890- \t\r\n"

0044F17D &#160;|&#160;8A1411 &#160; &#160; &#160; &#160; &#160;MOV DL,BYTE PTR DS:[ECX+EDX]

0044F180 &#160;|&#160;E8 0F25FCFF &#160; &#160; CALL test1.00411694

0044F185 &#160;|&#160;8B55 EC &#160; &#160; &#160; &#160; MOV EDX,DWORD PTR SS:[EBP-0x14]

0044F188 &#160;|&#160;8B0F &#160; &#160; &#160; &#160; &#160; &#160;MOV ECX,DWORD PTR DS:[EDI]

0044F18A &#160;|&#160;8BC7 &#160; &#160; &#160; &#160; &#160; &#160;MOV EAX,EDI

0044F18C &#160;|&#160;E8 3726FCFF &#160; &#160; CALL test1.004117C8

0044F191 &#160;|&#160;EB 23 &#160; &#160; &#160; &#160; &#160; JMP SHORT test1.0044F1B6

0044F193 &#160;\-8B07 &#160; &#160; &#160; &#160; &#160; &#160;MOV EAX,DWORD PTR DS:[EDI]

0044F195 &#160; &#160;E8 E225FCFF &#160; &#160; CALL test1.0041177C

0044F19A &#160; &#160;85C0 &#160; &#160; &#160; &#160; &#160; &#160;TEST EAX,EAX

 
As a bonus there is two extra functions: dputs and dprintf, just puts and printf, but they will output debug strings (so you can use DbgView to get logging information).
 
Greetings,
 
Mr. eXoDia