Financial Malware Hijacks Online Banking Sessions
Orome1 writes "A new type of financial malware has the ability to hijack customers' online banking sessions in real time using their session ID tokens. The OddJob Trojan keeps sessions open after customers think they have 'logged off,' enabling criminals to extract money and commit fraud unnoticed. This is a completely new piece of malware that pushes the hacking envelope through the evolution of existing attack methodologies. It shows how hacker ingenuity can side-step many commercial IT security applications traditionally used to defend users' digital — and online monetary — assets."
... why you require your customers to use Windows when doing online banking?
Trusteer's research team has reverse engineered and dissected OddJob's code methodology, right down to the banks it targets and its attack methods.
No one thought it important enough to list the banks being targeted? Or is this "professional courtesy" on the part of whatever law enforcement agency is conducting the investigation to leave all of the banks' customers in the dark, lest the banks get a bad rep?
The bank I use (in Mexico) forces you to get a different number from the security token every time you login or make a transaction (they are generated once a minute). If you try to make a transaction using the same token number that was used to login to the bank, the system forces you to get a different number from the token. In theory, this would stop this kind of attack. Why are no other banks doing the same?
Hence the suggestion that after using online banking, you close the browser not just log out of the session. Or would this not help with this malware?
From the source site (the blog at http://www.trusteer.com/
"The good news is that Trusteer's Rapport secure web access software- which is now in use by millions of online banking customers - can prevent OddJob from executing."
Now, I don't know Trusteer's rep, but when I see a story like this that originates from what appears to be a source that's in the business of selling security software, I want a second opinion from another source. A quick "google" for OddJob finds stories that all seem to tie back to Trusteer's blog entry. This story also doesn't say much about platform sensitivity. Is this an issue on any OS platform that uses Firefox, for example?
Which is why I always close my browser after a banking session.
Which is why I always use a secure OS and a secure browser to do my online banking.
If you use Internet Explorer on Windows, "closing" your browser is not enough. Internet Explorer is part of the OS, and keeps on running in the background even if no window of it is showing.
http://www.computing.net/answers/security/rapport-security-software-avoid-using-it/28295.html
This product is to be avoided at all costs...if anyone is still having problems, I have managed to switch it off and uninstall it, altho' the Rapport/Trusteer team clearly did not want to help, and many believe it's not intended to be uninstalled.
If you use a live cd, then you're not booting to your [presumably] windows hard drive, so you are therefore avoiding any malware/trojan/virus therein. There are no cookies or session id's or anything else saved from a live cd. All it takes is a reboot to a Live cd, do your online banking, remove cd, reboot to windoze. http://voices.washingtonpost.com/securityfix/2009/10/e-banking_on_a_locked_down_non.html
What is this "teller window" you speak of? Can I encourage my bank to install one?
Nae king! Nae laird! Nae yurrupiean pressedent! We willna be fooled again!
P.S.=> Which, in the end, speaks MORE FOR ME, than against me... because, when ALL YOU HAVE IS EFFETE MOD DOWNS, that have NO TECHNICAL JUSTIFICATION BEHIND THEM? You're shown as "helpless henrys"... and you ALL know it! apk
I know, I know, don't feed the trolls.
I'll play along for a moment and keep pretending like the number of vulnerabilities are a valid measure of a system's security. Let's take a closer look at your secunia links: the number for the Linux kernel includes all vulnerabilities from 2003-2011. Windows 7 was released in October 2009. The most severe unpatched vulnerability in the Linux kernel is rated "Less critical," or 2/5. The most severe unpatched Windows vulnerability is rated "Highly critical," or 4/5. The actual numbers are pretty even: both had 47 in 2010, Win7 has had 6 and Linux has had 4 so far this year. And hey, I don't even need to cite this info, you've already done it for me.
Now let's find some more of these facts that you love so much. There were at least 1,017,208 malware programs *created* in the first half of 2010...99.4% of them for Windows. Now consider that, by far, the primary entry point of malware is social engineering, not actual system vulnerabilities. I know this is Slashdot and all, but once you have less tech-savvy family and friends on your computers and networks, it doesn't matter how careful or knowledgeable you are.
You didn't read further...
The most severe unpatched Secunia advisory affecting Linux Kernel 2.6.x, with all vendor patches applied, is rated Less critical
The most severe unpatched Secunia advisory affecting Microsoft Windows 7, with all vendor patches applied, is rated Highly critical
Don't even get me started on Microsoft applying patches on patches without reporting it to users.
Here's where you are wrong: By Microsoft's own admission, Windows 7 kernel is the same as Windows Vista kernel only adding new features. That means all of Vista's problems are 7's problems. You were comparing it to the entire 2.6.x series kernel right? In reality you should really only be comparing kernel 2.6.27 and newer as all older versions have reached end of life.
So even counting the end of life versions of the kernel we have 2.6.x - Unpatched 5% (13 of 249 Secunia advisories) = 13 unpatched
and Vista 7% (9 of 138 Secunia advisories) + 7(same kernel) 11% (6 of 57 Secunia advisories) = 9+6 = 15 unpatched
So the kernel found in both Vista and 7 has 2 more unpatched advisories and some of them are rated highly critical none in the Linux kernel are. How many super secret microsoft patches never caught prior to patching and/or acknowledged? Who knows. You fail.
What is ironic is that IBM Zurich was predicting this exact type of attack.
This is why they made the ZTIC prototype, and is why UBS is using it under their name of the UBS Access Key.
Why is the ZTIC so unique that IBM made it? Couple reasons:
1: Simplicity. Plug it in a USB port, it makes a secure connection through the computer to the bank, and no matter how trashed the host computer is, the worst it can do is stop the connection. It confirms access and transactions on the device, so even if the web browser is saying that a transaction was successful, the ZTIC will show if it got modified and turned into a large bank withdrawal heading to Elbonia in reality.
2: Low attack surface. Almost anything can be hacked, but it only does one task. If the device is constructed right, reflashing the device without taking it apart and finding the JTAG parts on a chip would be almost impossible.
3: Even Joe Sixpack might wake up and not let a transaction through if the $100 that was going to his bookie for a Superbowl game showed up as a $10,000 transfer to an offshore bank. So, it does contribute to slowing down even PEBKAC issues.