-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reflective Loader as payload #6
Comments
Hi, I see that the error was on referencing the token? I think the reason is the parameters that are passed to the newly created process are incomplete. Some of the components are not filled: process_ghosting/process_env.cpp Lines 139 to 151 in cc51f9c
This is because the PoC is not finished, I added only those components that were essential for making the process run. It will be fixed in the future, as mentioned here: #2 |
I understand now. How can I try to find missing parameters ? |
The problem is, it is not that easy. By parameters I mean not just some particular values, but structures that have to be initialized in a proper way, and filled manually. It will require some research about how those parameters are set in the original process creation. And it is not documented, so it will take some digging. It is on my TODO, but I currently have some more urgent work. |
For now what I can offer you is trying a similar method, which does not require it: transacted_hollowing. Please let me know if it works for you (it should). |
Alright, I got you. |
Hi,
Reflective loaders like Cobalt Strike's beacon or Metasploit's meterpreter don't callback home.
Beacon seems alive but not calling back home.
Also nothing on wireshark.
Do you have an idea of why ?
Thanks in advance
The text was updated successfully, but these errors were encountered: