Win32/Zbot - беда-беда
Вот такая зараза прилепилась к нам.
Будьте очень аккуратны и по возможности просмотрите логи своих фаерволов. В двух словах, что произошло.
Вирус распространяется через уязвимость в одной из версий Java Runtime Environment (какая - не знаю, разбирательствами занимался не я). Вирус НЕ ДЕТЕКТИРУЕТСЯ Касперским и всеми возможными сканерами, которые мы использовали.
Зато его активность очень хорошо определяются почтовые DNSBL, которые радостно банят IP. Это естественно сказывается на возможность пользователей отправлять почту наружу.
IP Address xxx.xxx.xxx.xxx is listed in the CBL. It appears to be infected with a spam sending trojan, proxy or some other form of botnet.
It was last detected at 2012-11-22 13:00 GMT (+/- 30 minutes), approximately 18 hours ago.
It has been relisted following a previous removal at 2012-11-21 15:23 GMT (1 days, 15 hours, 16 minutes ago)
This IP is infected with, or is NATting for a machine infected with Win32/Zbot (Microsoft).
This was detected by observing this IP attempting to make contact to a Zeus Command and Control server, with contents unique to Zeus C&C command protocols.
Zbot is known by other names: Wsnpoem (Symantec) and most commonly as Zeus.
Zbot/Zeus is a banking trojan, and specializes in stealing personal information (passwords, account information, etc) from interactions with banking sites through the use of "formgrabs".
This was detected by a TCP/IP connection from xxx.xxx.xxx.xxx on port 49380 going to IP address 126.96.36.199 (the sinkhole) on port 80.
The botnet command and control domain for this connection was "f0adugd8sj-akssfa.info".
This detection corresponds to a connection at 2012-11-22 12:34:09 (GMT - this timestamp is believed accurate to within one second).
These infections are rated as a "severe threat" by Microsoft. It is a trojan downloader, and can download and execute ANY software on the infected computer.
You will need to find and eradicate the infection before delisting the IP address.
We strongly recommend that you DO NOT simply firewall off connections to the sinkhole IP addresses given above. Those IP addresses are of sinkholes operated by malware researchers. In other words, it's a "sensor" (only) run by "the good guys". The bot "thinks" its a command and control server run by the spambot operators but it isn't. It DOES NOT actually download anything, and is not a threat. If you firewall the sinkhole addresses, your IPs will remain infected, and they will STILL be delivering your users/customers personal information, including banking information to the criminal bot operators.
If you do choose to firewall these IPs, PLEASE instrument your firewall to tell you which internal machine is connecting to them so that you can identify the infected machine yourself and fix it.
We are enhancing the instructions on how to find these infections, and more information will be given here as it becomes available.
Virtually all detections made by the CBL are of infections that do NOT leave any "tracks" for you to find in your mail server logs. This is even more important for the viruses described here - these detections are made on network-level detections of malicious behaviour and may NOT involve malicious email being sent.
This means: if you have port 25 blocking enabled, do not take this as indication that your port 25 blocking isn't working.
The links above may help you find this infection. You can also consult Advanced Techniques for other options and alternatives. NOTE: the Advanced Techniques link focuses on finding port 25(SMTP) traffic. With "sinkhole malware" detections such as this listing, we aren't detecting port 25 traffic, we're detecting traffic on other ports. Therefore, when reading Advanced Techniques, you will need to consider all ports, not just SMTP.
Pay very close attention: Most of these trojans have extremely poor detection rates in current Anti-Virus software. For example, Ponmocup is only detected by 3 out of 49 AV tools queried at Virus Total.
Thus: having your anti-virus software doesn't find anything doesn't prove that you're not infected.
While we regret having to say this, downloaders will generally download many different malicious payloads. Even if an Anti-Virus product finds and removes the direct threat, they will not have detected or removed the other malicious payloads. For that reason, we recommend recloning the machine - meaning: reformatting the disks on the infected machine, and re-installing all software from known-good sources.
WARNING: If you continually delist xxx.xxx.xxx.xxx without fixing the problem, the CBL will eventually stop allowing the delisting of xxx.xxx.xxx.xxx.
If you have resolved the problem shown above and delisted the IP yourself, there is no need to contact us.