Silent Banker trojan?

[Atomas31]

Hi,

I just wonder, does NOD32 2.70 protect against the "silent banker" trojan?


Thanks,
Atomas31

Originally Posted by Atomas31

I just wonder, does NOD32 2.70 protect against the "silent banker" trojan?

There isn't only one silent banker trojan . By "silent banker trojan" one may mean a trojan (keylooger , perhaps) which is designed to steal passwords/account informations . Well , there are many such threats

[Stijnson]

Originally Posted by HiTech_boy

There isn't only one silent banker trojan . By "silent banker trojan" one may mean a trojan (keylooger , perhaps) which is designed to steal passwords/account informations . Well , there are many such threats

I think the one Atomas is referring to is the one that has recently been discovered by a Symantec investigator (a week and a half ago I think), but I haven't heard about it since to be honest.

[Atomas31]

Well, I suppose like stijnson indicated that it must be recent since they talk about it, yesterday, in the news...

[xp_1839]

Is NOD32 users protected from trojan.silentbanker?
If so, which virus signature database protect against the above threat?
Read more of this trojan here: http://www.pcworld.com/article/id,141364-c,trojanhorses/article.html

[Kosak]

Hi!

Has someone got sample of this trojan?

[ronjor]

Lukas K.

Please don't ask for samples of malware on these forums. Thanks.

[Atomas31]

So does the answer is Yes or No NOD32 protect us against this trojan? (I presume, or at least hope, it is yes but who knows!!!)

Thanks,
Atomas31

[NerdWeasel]

I know I had a customer with an IM-Worm that NOD32 did not detect and still does not over 2 weeks later even after submitting samples. I know because I scan a zipped sample of it with every new signature update, hoping. Pretty embarassing after getting many, many people on NOD32. I've read ESET's justification for not incorporating every viral into the database but still, it doesn't leave a good impression with end users or myself for that matter. VERY tempting to make the switch to Kaspersky.

Kaspersky detected it as IM-Worm.Win32.Banker.l and IM-Worm.Win32.Banker.j. As of today NOD32 still sees nothing.