Mr.Bojangles wrote:it seems to hide good, I'll try some other methods one day when I have time. This would be good in a new release.I think so too.
Thanks for checking!
A forum for reverse engineering, OS internals and malware analysis
Mr.Bojangles wrote:it seems to hide good, I'll try some other methods one day when I have time. This would be good in a new release.I think so too.
Buster_BSA wrote:http://hotfile.com/dl/119691661/3865921 ... I.RAR.html@Buster_BSA
Note: Injected filename must be "LOG_API.DLL".
Mr.Bojangles wrote:how does code splicing and openprocess stack or data tracing help detect it?call OpenProcess (program address range) ---> LOG_API.dll!FakeOpenProcess (injected dll address range) ----> trueOpenProcess (kernel32.dll address range)
looking for structs or code in own maps..this is too specific and unlikely will be implemented in any malware
kmd wrote:call OpenProcess (program address range) ---> LOG_API.dll!FakeOpenProcess (injected dll address range) ----> trueOpenProcess (kernel32.dll address range)Does it identify LOG_API.DLL uniquely or is a generic method to detect OpenProcess API has been hooked?