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

Using an AirPcap device in Windows with Wireshark

Capturing wireless traffic in a Windows environment is unfortunately not as easy as a setting change. As with most Windows-based software, drivers in Windows are often not open source and do not allow for configuration change into monitor mode. With this in mind, we must use a specialized piece of hardware known as an AirPcap device. Once you have obtained an AirPcap device you will be required to install the software on the accompanying CD to your analysis computer. The configurable options include: • Interface - Select the device you are using for your capture here. Some advanced analysis scenarios may require you to use more than one AirPcap device to sniff simultaneously on multiple channels. • Blink LED - Clicking this button will make the LED lights on the AirPcap device blink. This is primarily used to identify the specific adapter you are using if you are using multiple AirPcap devices. • Channel - In this field, you select the channel you want AirPcap to listen on. Extension C...

Anti CSRF header

Recently I came across an application which was preventing crsf attacks using a unique non-traditional approach. In traditional approach the csrf is thwarted by embedding unique random tokens, called nonce, in each sensitive page. But this application, which was making ajax calls and used jQuery, was creating a header to identify the valid and invalid requests altogether. The idea is to generate a custom header, x-session-token in this case, with every request which is considered sensitive and includes any sort of transaction. For example: xhr.setRequestHeader('x-session-token', csrf_token)   At the server level, server checks for this header if found request is fulfilled, otherwise rejected. We need to use xhr calls for making use of this technique, not useful in regular POST and GET requests. Since, I was not aware of this kind of countermeasures, probably, since most of the applications I did were using standard requests. So, I searched a bit and found even Go...

Some one watching where you visited!

Yes... Mozilla has been susceptible to browser-history stealing java script code. Today, Giorgio posted some cool information about the exploit. Mozilla is already working on this. This bug has been reported. Actually they have set up a web site to show the proof-of-concept. Visit www.statrpanic.com in FF,Safari or Netscape and it will tell you which websites have you been already ! But I am not sure it will work in IE or not because my IE is not responding to the website. Clearing history of visited website makes you safe to this attack. I mean this is one way..may be there are other ways to exploit this. But I have found this effective. Try it yourself in FF and then in IE and see the results.