Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Another computer with Trojan.Dropper.BCMiner


  • This topic is locked This topic is locked
2 replies to this topic

#1 Coconfused

Coconfused

  • Members
  • 48 posts
  • OFFLINE
  •  
  • Local time:07:13 PM

Posted 22 July 2012 - 05:31 PM

Malaware Bytes has identified Trojan.Dropper.BCMiner. It says it fixes it, but it always comes back.

I saw a post by someone else with this problem.

I followed the first three steps listed, but I could not figure out how to export the log from the tdsskiller.

This is the log from aswMBR that the other user was told to run:

aswMBR version 0.9.9.1665 Copyright© 2011 AVAST Software
Run date: 2012-07-22 13:17:43
-----------------------------
13:17:43.681 OS Version: Windows x64 6.1.7601 Service Pack 1
13:17:43.681 Number of processors: 8 586 0x2A07
13:17:43.681 ComputerName: THEBURNINATOR UserName: Ole Bry
13:17:45.682 Initialize success
13:17:46.088 AVAST engine defs: 12072200
13:18:21.531 Disk 0 (boot) \Device\Harddisk0\DR0 -> \Device\Ide\IAAStorageDevice-1
13:18:21.531 Disk 0 Vendor: ST320LT0 0001 Size: 305245MB BusType: 8
13:18:21.562 Disk 0 MBR read successfully
13:18:21.562 Disk 0 MBR scan
13:18:21.562 Disk 0 Windows VISTA default MBR code
13:18:21.578 Disk 0 Partition 1 00 DE Dell Utility DELL 4.1 39 MB offset 63
13:18:21.594 Disk 0 Partition 2 80 (A) 07 HPFS/NTFS NTFS 9968 MB offset 81920
13:18:21.594 Disk 0 Partition 3 00 07 HPFS/NTFS NTFS 295236 MB offset 20496384
13:18:21.625 Disk 0 scanning C:\Windows\system32\drivers
13:18:33.730 Service scanning
13:18:50.195 Modules scanning
13:18:50.195 Disk 0 trace - called modules:
13:18:50.242 ntoskrnl.exe CLASSPNP.SYS disk.sys stdcfltn.sys ACPI.sys iaStor.sys hal.dll
13:18:50.242 1 nt!IofCallDriver -> \Device\Harddisk0\DR0[0xfffffa8009d35060]
13:18:50.257 3 CLASSPNP.SYS[fffff88001bad43f] -> nt!IofCallDriver -> [0xfffffa8009b64cb0]
13:18:50.257 5 stdcfltn.sys[fffff88001aedc52] -> nt!IofCallDriver -> [0xfffffa800814f810]
13:18:50.257 7 ACPI.sys[fffff88000f607a1] -> nt!IofCallDriver -> \Device\Ide\IAAStorageDevice-1[0xfffffa8008155050]
13:18:55.327 AVAST engine scan C:\Windows
13:18:56.903 AVAST engine scan C:\Windows\system32
13:20:05.404 File: C:\Windows\assembly\GAC_32\Desktop.ini **INFECTED** Win32:Sirefef-PL [Rtk]
13:20:06.715 File: C:\Windows\assembly\GAC_64\Desktop.ini **INFECTED** Win32:Sirefef-PL [Rtk]
13:20:53.978 AVAST engine scan C:\Windows\system32\drivers
13:21:06.895 AVAST engine scan C:\Users\Ole Bry
13:22:49.559 AVAST engine scan C:\ProgramData
13:26:30.446 Scan finished successfully
13:27:30.116 Disk 0 MBR has been saved successfully to "C:\Users\Ole Bry\Desktop\MBR.dat"
13:27:30.116 The log file has been saved successfully to "C:\Users\Ole Bry\Desktop\aswMBR Log.txt"

*******************************************************************************************************

And this is the text file from the List of threats from ESET:

C:\TDSSKiller_Quarantine\22.07.2012_13.36.21\tdlfs0000\trz12A4.tmp Win32/Olmarik.AYH trojan cleaned by deleting - quarantined
C:\TDSSKiller_Quarantine\22.07.2012_13.36.21\tdlfs0000\trz27DA.tmp Win64/Olmarik.AL trojan cleaned by deleting - quarantined
C:\TDSSKiller_Quarantine\22.07.2012_13.36.21\tdlfs0000\trz280A.tmp Win32/Olmarik.AWO trojan cleaned by deleting - quarantined
C:\TDSSKiller_Quarantine\22.07.2012_13.36.21\tdlfs0000\trz2849.tmp Win64/Olmarik.AK trojan cleaned by deleting - quarantined
C:\TDSSKiller_Quarantine\22.07.2012_13.36.21\tdlfs0000\trz3D7F.tmp Win32/Olmarik.AFK trojan cleaned by deleting - quarantined
C:\TDSSKiller_Quarantine\22.07.2012_13.36.21\tdlfs0000\trz3D90.tmp Win64/Olmarik.AK trojan cleaned by deleting - quarantined
C:\TDSSKiller_Quarantine\22.07.2012_13.36.21\tdlfs0000\tsk0000.dta a variant of Win32/Olmarik.AYI trojan cleaned by deleting - quarantined
C:\TDSSKiller_Quarantine\22.07.2012_13.36.21\tdlfs0000\tsk0001.dta Win64/Olmarik.AK trojan cleaned by deleting - quarantined
C:\TDSSKiller_Quarantine\22.07.2012_13.36.21\tdlfs0000\tsk0014.dta a variant of Win32/Olmarik.AYI trojan cleaned by deleting - quarantined
C:\Windows\Installer\{3989ae76-a829-875d-70aa-a1d4c5dba47b}\U\00000008.@ Win64/Agent.BA trojan cleaned by deleting - quarantined
C:\Windows\Installer\{3989ae76-a829-875d-70aa-a1d4c5dba47b}\U\trz2D0F.tmp a variant of Win32/Sirefef.FD trojan cleaned by deleting - quarantined
C:\Windows\Installer\{3989ae76-a829-875d-70aa-a1d4c5dba47b}\U\trz2D7D.tmp a variant of Win32/Sirefef.FD trojan cleaned by deleting - quarantined
C:\Windows\Installer\{3989ae76-a829-875d-70aa-a1d4c5dba47b}\U\trz380E.tmp a variant of Win32/Sirefef.FD trojan cleaned by deleting - quarantined
C:\Windows\Installer\{3989ae76-a829-875d-70aa-a1d4c5dba47b}\U\trz42BD.tmp a variant of Win32/Sirefef.FD trojan cleaned by deleting - quarantined
C:\Windows\Installer\{3989ae76-a829-875d-70aa-a1d4c5dba47b}\U\trz42F4.tmp a variant of Win32/Sirefef.FD trojan cleaned by deleting - quarantined
C:\Windows\Installer\{3989ae76-a829-875d-70aa-a1d4c5dba47b}\U\trz599E.tmp a variant of Win32/Sirefef.FD trojan cleaned by deleting - quarantined
C:\Windows\Installer\{3989ae76-a829-875d-70aa-a1d4c5dba47b}\U\trz76EB.tmp a variant of Win32/Sirefef.FD trojan cleaned by deleting - quarantined
C:\Windows\Installer\{3989ae76-a829-875d-70aa-a1d4c5dba47b}\U\trz9B61.tmp a variant of Win32/Sirefef.FD trojan cleaned by deleting - quarantined
C:\Windows\Installer\{3989ae76-a829-875d-70aa-a1d4c5dba47b}\U\trz9E3C.tmp a variant of Win32/Sirefef.FD trojan cleaned by deleting - quarantined
C:\Windows\Installer\{3989ae76-a829-875d-70aa-a1d4c5dba47b}\U\trzA261.tmp a variant of Win32/Sirefef.FD trojan cleaned by deleting - quarantined
C:\Windows\Installer\{3989ae76-a829-875d-70aa-a1d4c5dba47b}\U\trzA313.tmp a variant of Win32/Sirefef.FD trojan cleaned by deleting - quarantined
C:\Windows\Installer\{3989ae76-a829-875d-70aa-a1d4c5dba47b}\U\trzCE2B.tmp a variant of Win32/Sirefef.FD trojan cleaned by deleting - quarantined
Operating memory a variant of Win32/Sirefef.EZ trojan


Any help would be much appreciated. This sticky little problem won't seem to go away.

BC AdBot (Login to Remove)

 


#2 narenxp

narenxp

  • BC Advisor
  • 16,371 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:07:13 PM

Posted 22 July 2012 - 06:20 PM

We need advanced tools to remove this one

Read the guide here

http://www.bleepingcomputer.com/forums/topic34773.html

and create a topic here

http://www.bleepingcomputer.com/forums/forum22.html

Good luck

#3 Orange Blossom

Orange Blossom

    OBleepin Investigator


  • Moderator
  • 36,993 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Location:Bloomington, IN
  • Local time:08:13 PM

Posted 22 July 2012 - 09:19 PM

Hello,

Now that you have posted a log here: http://www.bleepingcomputer.com/forums/topic461966.html you should NOT make further changes to your computer (install/uninstall programs, use special fix tools, delete files, edit the registry, etc) unless advised by a MRT Team member, nor should you ask for help elsewhere. Doing so can result in system changes which may not show in the log you already posted. Further, any modifications you make on your own may cause confusion for the helper assisting you and could complicate the malware removal process which would extend the time it takes to clean your computer.

From this point on the MRT Team should be the only members that you take advice from, until they have verified your log as clean.

Please be patient. It may take a while to get a response because the MRT Team members are EXTREMELY busy working logs posted before yours. They are volunteers who will help you out as soon as possible. Once you have made your post and are waiting, please DO NOT make another reply until it has been responded to by a member of the MRT Team. Generally the staff checks the forum for postings that have 0 replies as this makes it easier for them to identify those who have not been helped. If you post another response there will be 1 reply. A team member, looking for a new log to work may assume another MRT Team member is already assisting you and not open the thread to respond.

Please be patient. It may take several days to get a response but your log will be reviewed and answered as soon as possible. I advise checking your topic once a day for responses as the e-mail notification system is unreliable.

If HelpBot replies to your topic, PLEASE follow Step One so it will report your topic to the team members.

To avoid confusion, I am closing this topic. Good luck with your log.

Orange Blossom :cherry:
Help us help you. If HelpBot replies, you MUST follow step 1 in its reply so we know you need help.

Orange Blossom

An ounce of prevention is worth a pound of cure

SpywareBlaster, WinPatrol Plus, ESET Smart Security, Malwarebytes' Anti-Malware, NoScript Firefox ext., Norton noscript




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users