Explore >> Select a destination
|
You are here 
|
aixxe.net | ||
| | | | |
openpunk.com
|
|
| | | | | Recently I faced a rather intimidating problem while working on a project. The problem was fairly simple from an objective point of view: "How do I load a DLL into a process on startup?" Now you might be wondering, "Why not just patch the IAT (import address table) on the executable and force it to load your payload DLL??" Yes! That was my exact thoughts too, however for reasons I'll explain it wasn't that simple. | |
| | | | |
dblohm7.ca
|
|
| | | | | This is the second post in my "2018 Roundup" series. For an index of all entries, please see my blog entry for Q1. As I have alluded to ... | |
| | | | |
m417z.com
|
|
| | | | | In one of my previous blog posts, Implementing Global Injection and Hooking in Windows, I wrote about my journey in implementing global DLL injection for Windhawk, the customization marketplace for Windows programs. If you haven't read it yet, I invite you to read it, but the bottom line is that I ended up with an implementation that enumerates all processes and injects the DLL into each of them. To make sure the DLL is also loaded in newly created processes, the implementation intercepts new process cre... | |
| | | | |
gist.github.com
|
|
| | | Evidence of Safepoint bias for AsyncGetCallTrace (AsyncProfiler) - Profile.java | ||
