3 ms·
Note that a keylogger is a completely different threat than modern identity-theft malware. A keylogger just "logs" keystrokes, either locally or remotely, for
by peterwwillis 12y ago
Note that a keylogger is a completely different threat than modern identity-theft malware.
A keylogger just "logs" keystrokes, either locally or remotely, for later use. While this is a valid threat, using two-factor authentication basically makes this a non-issue. On the other hand, malware that targets specific login fields is usually smart enough to also steal session cookies, or with most banking trojans, inject requests into your live browser session.
The latter is used to literally transfer money in/out of your account, or make automatic purchases, while you browse the web. There is no protection from these trojans. If you're infected, you're fucked. The only thing 2FA saves you from here is repeated attacks once your session expires. (Luckily i've never personally seen a trojan like this built for Linux, but that's just a matter of time/market share)
- Someone1234 12y agoGreat summary of the current state of malware. I am starting to think that security people should stop using the term "keylogger" altogether. It is unhelpful, and damn right dangerous. When people read "keylogger" they often envision malware which sits there and grabs your keystrokes, so then people assume (see posts elsewhere in this HN thread even) that using on-screen keyboards or jumping back and forth between fields saves them. Classical literal "keyloggers" are now mostly gone. Grabbing a long series of keystrokes is extremely hard to automatically utilise (which is the goal now). Instead malware will either inject itself into the TCP/IP stack, HTTP stack, or directly into the browser (most popular) itself to steal credentials after the form is submitted but before it is encrypted and sent over the network. The advantage to the "bad guys" of doing things this way is that they get contextual information (e.g. form name, form destination URL, as well as username/password). Once you have login information AND contextual information you can automate it entirely and ignore a lot of stuff you aren't interested in (e.g. steal Google accounts, but ignore Hacker News accounts). Other than spouses spying on one another or a parent spying on their kid, a "keylogger" is pretty much dead in the classical sense. No organise crime gang wants a few gigabytes of keystrokes they have to sort through in order to get to the good stuff.
- ufmace 12y agoBank of America seems to have protection against this type of threat. If you have 2FA enabled, via text to mobile, there is a 2FA test on first login on a new computer. But they also have an extra 2FA protecting everything that would allow an attacker to transfer money out of the account. Adding a new bill pay payee, changing the address or account info on a payee, and any external wire transfer all require a new 2FA code to be sent and entered every time, no matter what the device. I still wouldn't login to them, or any other financial account, on an untrusted device, though.