April 18, 2024, 22:20
bigger smaller reset     1020px Wide width Full width Reset   * *

Gildor's Forums

  Homepage Facebook Read news on Twitter Youtube channel Github page
Welcome, Guest. Please login or register.
Did you miss your activation email?

« previous next »
Print
Author Topic: How Unpack Themida 2.x.x  (Read 16267 times)
CriticalError
Full Member
***
Posts: 172



View Profile
« on: June 16, 2015, 23:32 »

Hello everybody,

Today I will be showing you all how you can unpack a sample which is packed with Themida. This tutorial will show you how to do the process without requiring to manually use a debugger yourself.

What you will learn in this thread:
- What Themida is
- A bit about how Themida works
- Why packers/obfuscators may be used with not only malicious software but safe, legitmate software
- Why unpacking is useful to Malware Analysis
- How you can unpack samples packed by Themida without requring knowledge of how to use a Debugger yourself manually

1). What Themida is
Themida is software specifically engineered to help software stay better protected from becoming cracked and/or it's source code was being stolen.

If someone comes along and they can read the code you wrote for your software, if you have not made the software opensource and did not wish the code to be given out and/or read by someone, would you be happy about them having found a way to read your source code? I don't think you would.

The purpose of Themida is to help prevent the protected software from becoming vulnerable to reverse engineering attempts. It can also help against piracy.

2). A bit about how Themida works
Themida will pack the executable. When you execute the packed sample, it will unpack the executable in memory and use that to continue executing to perform and do what it's meant to do. If the unpacking of the packed executable into memory fails for whatever reason, then the program will not work.

3). Why packers may be used in legitimate software
Packers may be used in legitimate software so the developer's software is better protected against attacks. If someone can read your code, or use Disassembly to understand how it works, they can try to find vulnerabilities and then use them to create zero-day exploits.

Packers are also quite frequent with malware. Your Antivirus product may pickup detections for software packed in a certain way/type of packer used.

4). Why unpacking is useful in Malware Analysis
If the sample is packed, then this essentially protects against Disassembly. We won't be able to understand how the program works, we'll just be reading the instructions from the packer wrapper. For example, the process of the unpacking. However, we want the original executable (unpacked executable) and we want to perform Disassembly with that executable so we can try to make sense of and understand how the program works to know if it's malicious or not.

5). How we can actually identify and unpack Themida packed executables
To start off, you'll need a few things:

Tools


OllyDBG Plugins


Script


Ok the first thing we need do is set path in the Themida - Winlicense Ultra Unpacker 1.4.txt for your "ARImpRec.dl", so we open the txt with notepad and search it.

Quote
HERE_ENTER_YOUR_DLL_PATH_TO_ARIMPREC_DLL:
mov ARIMPREC_PATH, "C:\Documents and Settings\Admin\Desktop\OllyDBG\plugin\ARImpRec.dll"

Open up ProtectionID and as can see first icon like a paper with a pencil, press there and drop your executable. It should process the information (if it can). As we can see in the below screenshot, it detects the Themida packing:



Ok after checked that we unpack ollydbg in a path we want, a example mine is in Desktop: C:\Documents and Settings\Admin\Desktop\OllyDBG.

So now we gonna create inside ollydbg folder a folder called plugin and inside we extract all plugins we download, so this need be look like that.




PS: delete PSAPI.DLL from main folder of OllyDBG.

Ok so now we are ready to start with it.

1. First time we open Olly we need set the plugin directory because is not configured, for do it we go to --> Option-Appareance, in the tab Directories we can set where we stored plugins, so do it, press ok and restart Olly.



2.So now the next time we open Olly we see plugins loaded.



3. Ok now we go open the target to unpack or just press F3, after opened we got a pop up, just press Yes and the file continue Analysing, just wait to finish.



4.Now press F9 to run it and as you can see, we got a pop up, don't worry just press ok and the debug is terminated.




5. Good the next move is run script, so for this we go can do it via plugin menu-ODBGScript-Run Script and we search for "Themida - Winlicense Ultra Unpacker 1.4.txt" download before.
Logged
CriticalError
Full Member
***
Posts: 172



View Profile
« Reply #1 on: June 16, 2015, 23:32 »

6.Ok after we load nothing happen becase we terminated the debug before, so what we need do is reopen the target, just press in the X to close target.

7.After reopened target run script again or if you get this pop up asking for begin unpacking process we press Yes.



Ok next one we press No.



So now the unpacking process has begun, we can check status in the down bar as the right side of screen, after some seconds, we got pause, now to resume and continue unpacking maximize main thread windows and press right click and go to -> Script Functions-Script Windows, so now we have a Window of Script opened, right click there and press Resume.



8. So now we got a pop up telling us about we need modify some values into "ollydbg.ini", after that we need restart Olly and resume script.



9. So now we repeat steps do before, open target and run script,etc, after we finish we got this at the end.



PS: remember close OllyDBG after open .ini.

10. Ok we press Yes and in the Script Execution press right click and Resume.

11. Good now this part is very important, if we running a VMWare, we need set Yes, if we running normal SO just press No.



12. Now we got another pop up, really in my case I select Moddern Scan no Simple, it uses more checks.



13. Ok in this one we select No.



14. Ok after finished we got a new pop, there I press Yes.



15. Finally the job is done, as you can see there, now we can see dumped file, so we press Yes for use this data.



16. As script say, we choose first time no, if we got any problem after press no, repeat the process and the next time just press Yes, just in case.



17. Ok this pop ask for compress the dumped file, but in this case we won't do it because is a good size, is not a file of 120MB or 200MB so I think is fine press No.



18. Ok after all this we finally have dumped file in the folder where stored exe.



Press ok and we are done.







PS: Ok I hope this guide help us to unpack in future your themida protections, so well have fun and sorry if my english is to bad.

Credits: LCF-AT, Nacho_dj and me for write this guide.
Logged
Gildor
Administrator
Hero Member
*****
Posts: 7973



View Profile WWW
« Reply #2 on: June 16, 2015, 23:49 »

Thank you very much for tutorial, Enzo!
Logged
Asuki
L2tool User
Newbie
*****
Posts: 21


View Profile
« Reply #3 on: September 08, 2018, 21:07 »

Thank you very much, my friend
Logged
kees
Newbie
*
Posts: 1


View Profile
« Reply #4 on: June 08, 2019, 16:42 »

I see this is old

But have aquestion about themida, I run the 1.4 script but it just lanch the program in trial mode and scrtipt stops at
REP_AFTER .

target is also protected with a everkey dongle by the way, but is busy to migrate to themida, I think that is not such a good idea, the everkey is better, if the programmers are not lazy, she are because I have patch the program in past and put all modules on and license to 2098 just hardware coded into, yes the end, it was just cmp, 0 if 1 then jump, unbelievable.

I am not as good with packet programs.

I do not crack programs for misuse the programmers, I just do it for fun, and if she lucky I do also tell them.

Such fun to do not telling, program is of no use, just music automation.

regards
Logged
Print 
« previous next »
Jump to:  

Powered by SMF | SMF © 2006-2009, Simple Machines LLC
Leviathan design by Bloc | XHTML | CSS