OWASP AW00T

=Main= The Project is under development. A quick Outlook Below for starters !

Initially the project was focused in displaying raw code and methodologies used in bypassing AV but the project is now going up a new level.

I have decided to develop a functional program that will bypass antivirus on the go with advanced polymorphic and Human like intelligence techniques.

Just for starters Demonstration. This is something that i did in 2008 in college so you can have a look how it starts! 1.	Bypassing Antivirus a. Objective

The objective of this exercise was to make the trojan.exe undetectable from the AVG antivirus and we were free to use any stub and the original functionality of the file must be regained.

Case one implementation     >       (Failure)

Case one (Failure)  Result Failure AVG detected both file Case one was based on the assumption that the signature is available on the .text section of our file but as soon i implemented it the AVG detected the file provided with the XOR stub as well.

The .text section of the program was encoded. We used Lord PE to make the text section writable.

Encode from here to here 00401225  	90           	NOP

To 004018DF. Initial instructions were:- I used a XOR stub looks like this:-

The original functionality was regained but AVG was still detecting the malicious file. So a secondary approach was required as shown in case two.

Hunting Antivirus Signature c. Case Two (Success)

Since the case one was based on our assumption that the Antivirus signature is based in the .text section of our file and thus we failed.

So our second approach was to dig out the signature or use the stub on all other sections as well but the latter idea does not sound so good as we have to deal with a lot of cases and program details in that case so we will be now hunting for the signature that the poor AVG antivirus is using.

Our approach will be as follows:-



We however are not concerned with the complete signature or the length and address it is associated with what we need is a single byte change in the signature of the file and making it undetectable from the antivirus. We used the hexedit to cut the file and then scanning it with the AVG Antivirus to check the respective files and check up to the minimal point up to which it detects and thus we can easily extract the signature from it. The signature was present in the .rdata section of the file. In hexedit if you see it starts from 1000 address or search it From hex string This is the signature that the AVG is detecting in the program. What we noticed is an instruction xor eax,eax which can easily be replaced with the mov eax,0 and on its implementation the bytes around the signature will be changed and the file will be undetectable from the AVG but the problem with this solution is that we have to add some extra bytes because of the different instruction size of these instructions the latter being larger Rather than using the above approach i used a simple method as mentioned in case one the XOR stub and used it on the address of the 31 05 (xor eax,eax) .We could have used any simple stub like just add a byte to it or subtract from it but we have to again save the file by editing and adding the opposite instruction like if we use add than after changed instruction change it to subtraction and vice versa to obtain the original file in run time. So we are using a XOR stub on the 31 05(xor eax,eax) instruction.

Implementation stub



As clearly shown in diagram above the XORed byte 3E was regained when the program is run as XORing it again makes it 31 again and the original instruction 31 C0 is regained. We need to make the .rdata section writable with LORD PE first but for safety sake i made all the first four sections writable. Firstly the initial instructions were copied and a jump to 004018e4 is done.

And made the olly to copy the changes to an executable and then save the file. The final result was as shown.



=Project About=