Search the Community
Showing results for tags 'Wsnpoem'.
I could use some help. I believe I have a trojan in the family of Zbot/Zeus on either my computer or Android phone (or both). I connect to the internet at home via wifi hotspot with my Android phone. I had a suspicion something was wrong and ran all the normal anti-virus/malware software which came up with a couple issues. After this I attempted to start an account with this forum and was denied access with the following: "Sorry, you don't have permission for that! [#1001] You are not allowed to visit this community." This looked suspicious so I checked to see if my IP was blacklisted. As I have a dynamic IP I checked the range in which my phone normally uses, 3 of the 5 were blacklisted with cbl.abuseat.org. The majority of reports showed: “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.” I then switched my PC off and left my phone on, checking the current IP. The same activity was reported later that evening by cbl.abuseat.org for my IP with only my phone on (full report follows). It should also be noted that three other IPs in the range ending 10-15 also showed activity around the same time (so not all my phone). From the report on cbl.abuseat.org it sounds like wiping the infected device is the best option for ensuring protection in future. I would like to know what others think. Is there a way to tell which device is infected? Maybe through logs on the phone and firewall on the computer? Is there anyway to know if my external hard drive is compromised (with my backupdata)? Any help is greatly appreciated. Example log from cbl.abuseat.org (with my IP address removed): CBL Lookup Utility: http://cbl.abuseat.org/lookup.cgi?ip=XX.XX.XX.12&.pubmit=Lookup IP Address XX.XX.XX.12 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 2013-07-25 11:00 GMT (+/- 30 minutes), approximately 3 hours ago. It has been relisted following a previous removal at 2012-05-04 10:38 GMT (447 days, 3 hours, 19 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 XX.XX.XX.12 on port 16172 going to IP address 188.8.131.52 (the sinkhole) on port 80. The botnet command and control domain for this connection was "zadejola.com". Behind a NAT, you should be able to find the infected machine by looking for attempted connections to IP address 184.108.40.206 or host name zadejola.com on any port with a network sniffer such as wireshark. Equivalently, you can examine your DNS server or proxy server logs to references to 220.127.116.11 or zadejola.com. See Advanced Techniques for more detail on how to use wireshark - ignore the references to port 25/SMTP traffic - the identifying activity is NOT on port 25. This detection corresponds to a connection at 2013-07-25 10:56:24 (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.