Hi Carlos,
If you see the injected code with malfind, you can just use malfind --pid=PID
--dump-dir=OUTDIR and it will automatically extract it to disk. Most likely the legitimate
EXE isn’t removed from the process address space, so it still resides at
_EPROCESS.Peb.ImageBaseAddress (which is what procexedump extracts). In other words, the
process contains two EXE files now, the original one at ImageBaseAddress, and the injected
one (wherever malfind says it exists).
Let me know if that *doesn’t* work as expected and we can look at some other options.
MHL
--------------------------------------------------
Michael Ligh (@iMHLv2)
GPG:
http://mnin.org/gpg.pubkey.txt
Blog:
http://volatility-labs.blogspot.com
On Apr 14, 2014, at 6:51 PM, Carlos Angeles <cangeles(a)gmail.com> wrote:
Hello all,
I'm analyzing a malware sample that is doing process hollowing. While
doing dynamic analysis, with Process Explorer open, I can see the
legitimate EXE (that appears to get hollowed) get started by the
malware, and is then orphaned as the malware terminates itself. A few
seconds later I see network communication starting.
The malfind plugin identifies the process as malware but when I try to
dump process from memory, the strings on the dumped process look the
same as the strings of the legitimate file in the System32 folder.
Using the yarascan plugin (following the example on the wiki) I'm able
to locate some strings (domain name, IP address, file requested by
GET) that are associated with the PID of the suspected hollowed
process.
Oh, and the malware is packed so I assume the unpacked code is being
placed into the address space of the legitimate file in memory.
The capture is a .vmem from a VM snapshot.
Any thoughts on how I can locate the unpacked code in memory?
Shouldn't dumping the PID with procexedump contain the unpacked code?
I've dumped the process by PID and physical offset (from psscan).
Thanks,
Carlos
_______________________________________________
Vol-users mailing list
Vol-users(a)volatilityfoundation.org
http://lists.volatilityfoundation.org/mailman/listinfo/vol-users