Endpoint Protection

 View Only
Expand all | Collapse all
Migration User

Migration UserNov 02, 2010 02:47 PM

  • 1.  W32.SillyFDC

    Posted Oct 30, 2010 05:11 PM

    W32.SillyFDC - This virus is on my network and has spread somewhat. It puts a check mark in the box to enable the use of a proxy server in LAN settings in IE on the client.

    SEPM has deteced the virus but it repeats its self. I was told by a Symantec tech support to disable the autorun feature on our network but he couldnt explain well enough why I should do this and what results this would have on the network and users.

    He just gave me this article below. But I would like to hear from some of you who know more about this or who have experienced it.

     

    http://www.symantec.com/security_response/writeup.jsp?docid=2006-071111-0646-99

     

    Thanks!



  • 2.  RE: W32.SillyFDC

    Posted Oct 30, 2010 05:31 PM

    Autorun should be disabled in case of worm infection or infection on file server

    http://support.microsoft.com/kb/967715

    or else which ever machines has the drive mapped of the infected server will get infected. Disabling Autoplay/Autorun stops virus from spreading in the network.

    Submit the suspicious files to security response.

    http://www.symantec.com/business/security_response/submitsamples.jsp

     

    and run full scan on infected machines with up-to-date virus definitions.



  • 3.  RE: W32.SillyFDC

    Posted Oct 30, 2010 11:03 PM

    Autorun is a fantastic way for viruses to spread in any network, and should be disabled all the time, even Microsoft recommends it!  Boohoo users have to open the cdrom drive to click on setup.exe, and it wont run on it's own.

    Just think if someone brings in an infected thumbdrive (which is how the silly virus spread in many cases) the drive autoruns the virus, you're infected..  All because a basic security measure that even MS has been pushing for being disabled, wasnt followed.

    Disable it via a GPO, or via an application control policy in SEP, there is one for download from the support site you can use, pre-made.



  • 4.  RE: W32.SillyFDC

    Posted Oct 31, 2010 12:59 AM

    Please see this KB:

    http://clientui-kb.symantec.com/kb/index?page=content&id=TECH104447&actp=search&viewlocale=en_US&searchid=1288500868090

     

    For sillyfdc, very important to disable auto-play on all the computers. Make sure that your  default shares are disabled. If possible, all shared drives arepassword protected, or Read only.

    Also, there is a new variant released on 30th Oct 2010. So please make sure you have updated definitions.

    Also, enable network scanning feature , in AV/AS policy-file system auto-protect.

     

     

     



  • 5.  RE: W32.SillyFDC

    Posted Nov 01, 2010 10:11 AM

    I understand the sense in disabling autorun, but we've used it for years without any virus problems.

    I cant see how Symantec just cant come up with a definition to clean\eliminate it. Their article says that:

    "If a Symantec antivirus product displays a detection alert for this threat, it means the computer is already protected and the Symantec product will effectively remove this threat from the computer"

    My SEPM deteced this and the AV client did as well but the problem still persists, so that statement is false.

    Besides disabling autorun is there anything I can push out from the SEPM to combat this for good? I'm not against disabling autorun but I feel that Symantec shoudl handle the job with the SEPM.

    Thanks.



  • 6.  RE: W32.SillyFDC

    Posted Nov 01, 2010 10:20 AM

    I agree ,

    However The new Generation Threats are not single file based..there might be multiple files for single threat so Symantec might be detecting one or more but not all the files.

    So you look for the suspicious files and submit to security response so they can comeup with new definitions.

    What you can do is update your SEPM with latest RapidRelease definitions and it might detect those files as well..

    Disabling Autorun only prevents threat from spreading..You can disable it for now..once everything is clear you can re-enable it.



  • 7.  RE: W32.SillyFDC

    Posted Nov 01, 2010 10:36 AM

    Well, it deteced the Backdoor.Cycbot virsus which is a variant of the W32.SillyFDC and SEPM reports it under event action as ""Virus found (process termination pending restart). So it would be correct to say that the virus is terminated since the client restarted the machines? And would it be correct to say that since the AV client found the virus and deleted it that the client is now protected from this from now on?

    These are my latest definitions:

    Windows Latest Symantec Version: 2010-10-31 rev. 002



  • 8.  RE: W32.SillyFDC

    Posted Nov 01, 2010 10:39 AM

    Here's what I can give you on why to disable Autorun:

    Autorun is meant to automatically run a file when a drive is opened, in this case a mapped drive. When this occurs, the threat may immediately begin making system changes such as:

  • -Lower security settings
  • -Alter Safe Mode settings
  • -Modify the hosts file
  • -Disable Windows Update and System Restore
  • -Bypass the Windows firewall
  • -Alter Explorer settings
  • -Disable the Task Manager, Registry Editor and other system software
  •  
  • After it makes these changes it may then attempt to copy over the share to the machine where Symantec may detect it. If we do and remove it there is still the potential that the threat has altered the machine to allow it to get back on the next time it tries.
  •  
  • There is a mantra when dealing with virus' that has been developed over many years of troubleshooting infections. Here's the steps we have developed to face any threat you come across:
  •  
  • http://www.symantec.com/docs/TECH122466


  • 9.  RE: W32.SillyFDC
    Best Answer

    Posted Nov 01, 2010 10:45 AM

    We have reclassified this detection, it's a brand new threat that we added on October 30th. Here's the link:

    http://www.symantec.com/security_response/writeup.jsp?docid=2010-103008-0555-99

    Unfortunately I don't have anything further to add other than our Security Response is looking into more robust detections for this.

    To answer your questions, yes you should be able to reboot and be clean/protected from this threat. It would be prudent to run another scan after rebooting to verify.



  • 10.  RE: W32.SillyFDC

    Posted Nov 01, 2010 11:08 AM

    Well, just to give an update:

    After SEPM detected Backdoor.Cycbot  and I rebooted the client machine I ran a scan on the client and again the virus appeared again as infected, I clicked on the "remove risk now" button and it cleaned it. I ran a scan again on the client and it came up again as infected, I then chose to remove the risk again by selecting delete, which it says it was deleted, then ran the scan again and it came up infected again.

    To prevent further spreading I'm going to disable autorun on the network but user's are still dealing with the virus.

    What does Symantec suggest I do after disabling autorun to prevent it from spreading? My definitions are already up to date?

    Does the current rapid release version have an updated definition that can detect and delete this virus?



  • 11.  RE: W32.SillyFDC

    Posted Nov 01, 2010 11:28 AM

    Make sure you run full scan in safe mode so that SEP can take complete action on those files.



  • 12.  RE: W32.SillyFDC

    Posted Nov 01, 2010 11:30 AM

    Do you know if the current rapid release version have an updated definition that can detect and delete this virus? All my clients have definition 2010-11-01 rev. 002



  • 13.  RE: W32.SillyFDC

    Posted Nov 01, 2010 11:31 AM

    http://www.sophos.com/security/analyses/viruses-and-spyware/malgbota.html

     

    Lists all relevant Processes and registry locations. Best anwser until Symantec can pick it up.



  • 14.  RE: W32.SillyFDC

    Posted Nov 01, 2010 11:35 AM

    I can Tell you 2010-11-01 rev. 019 does NOT.

     

     

    The files it does not identify are the DWM.exe and sometimes the shell.exe.

     



  • 15.  RE: W32.SillyFDC

    Posted Nov 01, 2010 11:37 AM

    We just had a security meeting on this threat. Right now there are 200 known variants of this threat. We are also seeing it packed with 3-4 other files when it infects. If you are seeing re-infections after a scan it's likely Symantec hasn't caught all the files. It would be a good idea to log a case with support so we can find the files and get them submitted for detections.



  • 16.  RE: W32.SillyFDC

    Posted Nov 01, 2010 04:00 PM

    Autorun is now disabled on the network via GPO and I guess we'll have to wait for an updated definition.

    Thanks everyone.



  • 17.  RE: W32.SillyFDC

    Posted Nov 01, 2010 04:04 PM

    I selected a few of the responses as the "solution" - thanks for all your help.



  • 18.  RE: W32.SillyFDC

    Posted Nov 01, 2010 04:05 PM

    You can also password protect your shares, if you have any need for them. Otherwise, turn it off.



  • 19.  RE: W32.SillyFDC

    Posted Nov 02, 2010 12:04 PM

    I find it somewhat disenheartening Sophos has been stopping this since 9/23. 

    Has anyone tried adding the MD5s to the Application Control>Block Applications?  Should work on the .exe files, never tried with a non-exe (the .cfg file in the write-up).



  • 20.  RE: W32.SillyFDC

    Posted Nov 02, 2010 12:14 PM

    2010-11-01 rev.54 obviously doesnt clean it either.



  • 21.  RE: W32.SillyFDC

    Posted Nov 02, 2010 12:58 PM

    Update, we *should* have an updated detection for this today that will hopefully fix this. I believe the detection will be under the name Backdoor.cycbot!gen or something similar. Unfortunately I do not have an ETA on this.



  • 22.  RE: W32.SillyFDC

    Posted Nov 02, 2010 01:56 PM

    Domains to block related to Cycbot:

     

    ·         bookknowlege.com

    ·         protectyourpc-11.com

    ·         8minutedating.com

    ·         freenetgameonline.com

    ·         xinmin.cn

    ·         freeonlinedatingtips.net

    ·         xy95.cn

     

    Listening port may be 50370, good idea to ensure that is locked as well.



  • 23.  RE: W32.SillyFDC

    Posted Nov 02, 2010 02:47 PM

    Thanks, hopefully it'll come out today.



  • 24.  RE: W32.SillyFDC

    Posted Nov 02, 2010 03:57 PM

    Updated detection: 11/2/2010 rev. 8

    Name: Backdoor.Cycbot!gen1

    I believe this should cover most of the threats if not all. If you come across anything it isn't detecting I would recommend submitting the file(s) to Symantec for further analysis.



  • 25.  RE: W32.SillyFDC

    Posted Nov 02, 2010 04:06 PM

     

     

    Just updated the clients with new revision 2010-11-02 rev.008

    Seems as if it detected the viruses on one of the infectedclients but couldnt clean them for some reason?

    Client AV notification:

    Scan type: Auto-Protect Scan

    Event: Risk Found!

    Security risk detected: Trojan.FakeAV!gen39

    File: C:\Documents and Settings\jjones\Application Data\Microsoft\svchost.exe

    Location: C:\Documents and Settings\jjones\Application Data\Microsoft

    Computer: ACCTWHSG User: SYSTEM

    Action taken: Pending Side Effects Analysis : Access denied

    Date found: Tuesday, November 02, 2010  3:42:32 PM 

    SEPM Notification: 

    Action taken is: Details Pending and Left Alone???

     

    Computer
    User
    IP Address
    Risk
    Risk Type
    Risk Count Date Time   Action
    Source
    File / Entry
    SYSTEM
    10.1.20.156
    Trojan.FakeAV!gen39
    Viral
    1 11/02/2010 14:43:44   Cleaned
    Auto-Protect scan
    C:\Documents and Settings\jjones\Local Settings\Temp\dwm.exe
    10.1.20.156 Trojan.FakeAV!gen39
    Viral
    1 11/02/2010 14:43:37   Details pending
    Auto-Protect scan
    C:\Documents and Settings\jjones\Local Settings\Temp\dwm.exe
    SYSTEM
    10.1.20.156
    Trojan.FakeAV!gen39
    Viral
    1 11/02/2010 14:43:21   Left alone
    Auto-Protect scan
    C:\Documents and Settings\jjones\Application Data\Microsoft\svchost.exe

     

     



  • 26.  RE: W32.SillyFDC

    Posted Nov 02, 2010 04:18 PM

    The file may be locked by Windows or something, try taking it to Safe Mode and scanning the C:\Documents and Settings\jjones\ folder to see if you get better results.

    Edit: The dwm.exe file is pending but right above it it gets cleaned. The above info still applies though for that file that is left alone.



  • 27.  RE: W32.SillyFDC

    Posted Nov 02, 2010 04:19 PM

     

    CleanedAuto-Protect scan

    C:\Documents and Settings\jjones\Local Settings\Temp\dwm.exe

     

    Details pending
    Auto-Protect scan
    C:\Documents and Settings\klindley\Local Settings\Temp\dwm.exe

     

    Left alone
    Auto-Protect scan
    C:\Documents and Settings\klindley\Application Data\Microsoft\svchost.exe

    Seems that the file sinfected are dwm.exe and svchost.exe



  • 28.  RE: W32.SillyFDC

    Posted Nov 02, 2010 04:22 PM

    Here's what have so far that are related to this:

    ·         dwm.exe

    ·         shell.exe

    ·         svchost.exe

    ·         stor.cfg



  • 29.  RE: W32.SillyFDC

    Posted Nov 03, 2010 08:03 PM

    I tried scanning and deleting in Safe Mode, but when I return to regular mode the virus is still detected on an active scan. I've been having this problem since October 22 (it began as W32.SillyFDC). Symantec, despite many live updates and full scans, still hasn't cleaned Backdoor.cycbot. On the bright side, it has identified all the files mentioned in this thread.

    In short, I'm getting pretty frustrated by the persistance of this problem.

    What do you suggest?

    The latest surviving (but allegedly cleaned) copy is backdoor.cycbot as shell.exe in this location:

    c:\documents and settings\[my.name]\application data\microsoft\windows\

    Before I click to take action, the software always warns that other processes should be ended -- but my browsers are closed and nothing else is open except stuff running in the background from startup.

     

    Thanks for any  help.

     

     



  • 30.  RE: W32.SillyFDC

    Posted Nov 04, 2010 10:15 AM

    Hi,

    Your best bet (for the time being) is to use MalwareBytes Antispyware (its free).

    Just until Symantec try and catch up.....;)