Skip to main content

Man-In-The-Browser Malware

Have heard about the malware quite long time back but today I got a chance to study about it into one of the magazines (net-security.org). It's interesting, really amazing, a clever way to steal money from transactions without you sense anything suspicious happening.
Without going into technical details, this Man-In-The-Browser (MITB) Malware is known as 'URLZone'. In contrast to Man in the middle (MITM) attack where the communication is intercepted and changed in between client and server over the wire this MITB malware infects the client machine installs some exe's like unisntall02.exe on the client machine. It then sends back the ID to the Command and Control server that is used by the hacker.
How it works:
This is most interesting part which made me read the article till end.

It records for the requests which are going on POST and over https, which indicates that something valuable is being transferred.
When user makes the transaction the URLzone malware silently changes the recipients name with the hacker's name. All these can be defined into the configuration file of the malware.
The bank will see the request as genuine as the sessionID and other tokens will be valid and transfer the amount from the user to hacker's account.
Then it intercepts again the response from the bank and replace the hacker's name to the original recipient's name which the user/sender was expecting to see.
This is the brief overview of its functioning. For more you can refer to following magazine (reference):
http://www.net-security.org/dl/insecure/INSECURE-Mag-29.pdf
It's really interesting.



Comments

Vaibhav said…
I was thinking of the same but as a MITM keylogger..
But about malware i have one doubt here... banks are not so foolish to transfer money to other account directly they have NEFT and RTGS in place.
Manipulating account no may not work as todays internet banking of most of the banks have implemented a system to add the Payee (whom you are transfering the money)then the payee has to be confirmed by OTP (One time Password which is send by SMS or email)than only the transfer happens succesfully...


Wants your view on this... :)

Popular posts from this blog

Ardilla- New tool for finding SQL Injection and XSS

Three Researchers -- MIT's Adam Kiezun , Stanford's Philip Guo , and Syracuse University's Karthick Jayaraman -- has developed a new tool ' Ardilla ' that automatically finds and exploits SQL injection and cross-site scripting vulnerabilities in Web applications. It creates inputs that pinpoint bugs in Web applications and then generates SQL injection and XSS attacks. But for now Ardilla is for PHP -based Web app only. The researchers say Ardilla found 68 never-before found vulnerabilities in five different PHP applications using the tool -- 23 SQL injection and 45 XSS flaws. More information is awaited. For their attack generation techniques refer to their document at: http://www.cs.washington.edu/homes/mernst/pubs/create-attacks-tr054.pdf

File Upload through Null Byte Injection

Sometimes, during file upload we come across situation wherein there would be check on the file extension at the client side as well as server side too. If the application does allow only .jpeg extension to be uploaded, the client side java script checks for the extension of the file before passing the request. We all know that how easily this can be defeated. Some applications, checks for the extension at the server side also. That's not easy to bypass. However there are some ways with which it still can be bypassed. Most of server side scripts are written in high level languages such as Php, Java etc who still use some C/C++ libraries to read the file name and contents. That leads to the problem. In C/C++ a line ends with /00 or which is called Null Byte. So whenever the interpreter sees a null byte at the end of the a string, it stops reading thinking it has reached at the end of the string. This can be used for the bypass. It works for many servers, specially php servers. T

Combining power of Fiddler with Burp

Both are pretty powerful tools when it comes to intercept and modify http communications. But at some point of time, they become even more powerful combo if tied with each other. They complement each other. In a recent pentest I came across a similar situation where in Burp was not able to intercept a specific kind of traffic and Fiddler came to rescue. The application was designed to upload video. The initial communication was straight forward, I mean logging into application, filling up the video details etc. And all these were easily captured by Burp except the point where you hit the Upload Video and it connects to a different server and surprisingly it was not captured by Burp, not sure why, even after repeated attempts. So, I fired Fiddler to see if the it sees this request. But it's a;ways to play with requests using Burp due to it's various functionalities like, Intruder, Repeaters etc. But it was necessary to capture this request in Burp. So the below steps can be