FrankRizzo
August 26th, 2011, 00:16
OK guys, I need a consult.
Any of you ever worked on a Thinstall target? (JMI, YES I've read all the threads concerning it here, even the one with you giving "helpful guidance" to someone else)
I have one that seems to be of the "single process" type, as there doesn't seem to be another process running, just the MAIN one. Also, unlike most (all?) of the others, this one has the weird embedded filesystem populated with files used by the application. I've found the place where they're pulled out, and I've dumped them from memory, but they don't disassemble very well.
Does anyone know if they're mangled?
I've found the place where it nicely tells you that it's calling the application, and then proceeds to do a far call to an address on the stack. This address seems to be too far away to be a valid OEP for the application. (Granted, I'm not the king of identifying .NET application OEPs, but this one looks weird).
So, I've tried dumping it, and get something that I can look at enough to tell it's been Dotfuscated. Problem being, it's "Not a valid win32 application", so I can't deobfuscate it. Yes, there are 100 unpacker scripts, and I've tried MOST of them. Even the tutorials on how to DIY, and I'm still getting no where.
So I guess the BIG question. Does anyone know anything about this thing?
Thanks!
FF
Any of you ever worked on a Thinstall target? (JMI, YES I've read all the threads concerning it here, even the one with you giving "helpful guidance" to someone else)

I have one that seems to be of the "single process" type, as there doesn't seem to be another process running, just the MAIN one. Also, unlike most (all?) of the others, this one has the weird embedded filesystem populated with files used by the application. I've found the place where they're pulled out, and I've dumped them from memory, but they don't disassemble very well.
Does anyone know if they're mangled?
I've found the place where it nicely tells you that it's calling the application, and then proceeds to do a far call to an address on the stack. This address seems to be too far away to be a valid OEP for the application. (Granted, I'm not the king of identifying .NET application OEPs, but this one looks weird).
So, I've tried dumping it, and get something that I can look at enough to tell it's been Dotfuscated. Problem being, it's "Not a valid win32 application", so I can't deobfuscate it. Yes, there are 100 unpacker scripts, and I've tried MOST of them. Even the tutorials on how to DIY, and I'm still getting no where.
So I guess the BIG question. Does anyone know anything about this thing?
Thanks!
FF