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

please help with bredolab infection removal


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

#1 clarkstar

clarkstar

  • Members
  • 20 posts
  • OFFLINE
  •  
  • Local time:10:06 AM

Posted 31 October 2009 - 08:58 PM

hello, my avast antivirus keeps popping up with the following:

C:WindowsTemprtrr.tmp or generic like C:WindowsTempmyoe.tmp C:\Windows\Temp\sgim.tmp
Win32:Bredolab-AQ [Trj]
Trojan Horse
091030-0, 10/30/2009

i cannot find it using MalWare Bytes, i think i got it through a google redirect malware which popped up last week and then again yesterday. i also use utorrent to dl occasionally but mostly use rapidshare links

BC AdBot (Login to Remove)

 


#2 rigel

rigel

    FD-BC


  • Members
  • 12,944 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:South Carolina - USA
  • Local time:12:06 PM

Posted 31 October 2009 - 10:09 PM

Let's try these ...

:flowers: Please download TFC by Old Timer and save it to your desktop.
alternate download link
  • Save any unsaved work. TFC will close ALL open programs including your browser!
  • Double-click on TFC.exe to run it. If you are using Vista, right-click on the file and choose Run As Administrator.
  • Click the Start button to begin the cleaning process and let it run uninterrupted to completion.
  • Important! If TFC prompts you to reboot, please do so immediately. If not prompted, manually reboot the machine anyway to ensure a complete clean.
:thumbsup: Please download and scan with SUPERAntiSpyware Free
  • Double-click SUPERAntiSypware.exe and use the default settings for installation.
  • An icon will be created on your desktop. Double-click that icon to launch the program.
  • If it will not start, go to Start > All Prgrams > SUPERAntiSpyware and click on Alternate Start.
  • If asked to update the program definitions, click "Yes". If not, update the definitions before scanning by selecting "Check for Updates". (If you encounter any problems while downloading the updates, manually download them from here. Double-click on the hyperlink for Download Installer and save SASDEFINITIONS.EXE to your desktop. Then double-click on SASDEFINITIONS.EXE to install the definitions.)
  • In the Main Menu, click the Preferences... button.
  • Click the "General and Startup" tab, and under Start-up Options, make sure "Start SUPERAntiSpyware when Windows starts" box is unchecked.
  • Click the "Scanning Control" tab, and under Scanner Options, make sure the following are checked (leave all others unchecked):
    • Close browsers before scanning.
    • Scan for tracking cookies.
    • Terminate memory threats before quarantining.
  • Click the "Close" button to leave the control center screen and exit the program.
  • Do not run a scan just yet.
Reboot your computer in "Safe Mode" using the F8 method. To do this, restart your computer and after hearing your computer beep once during startup (but before the Windows icon appears) press the F8 key repeatedly. A menu will appear with several options. Use the arrow keys to navigate and select the option to run Windows in "Safe Mode".

Scan with SUPERAntiSpyware as follows:
  • Launch the program and back on the main screen, under "Scan for Harmful Software" click Scan your computer.
  • On the left, make sure you check C:\Fixed Drive.
  • On the right, under "Complete Scan", choose Perform Complete Scan and click "Next".
  • After the scan is complete, a Scan Summary box will appear with potentially harmful items that were detected. Click "OK".
  • Make sure everything has a checkmark next to it and click "Next".
  • A notification will appear that "Quarantine and Removal is Complete". Click "OK" and then click the "Finish" button to return to the main menu.
  • If asked if you want to reboot, click "Yes" and reboot normally.
  • To retrieve the removal information after reboot, launch SUPERAntispyware again.
    • Click Preferences, then click the Statistics/Logs tab.
    • Under Scanner Logs, double-click SUPERAntiSpyware Scan Log.
    • If there are several logs, click the current dated log and press View log. A text file will open in your default text editor.
    • Please copy and paste the Scan Log results in your next reply.
  • Click Close to exit the program.

"In a world where you can be anything, be yourself." ~ unknown

"Fall in love with someone who deserves your heart. Not someone who plays with it. Will Smith


#3 clarkstar

clarkstar
  • Topic Starter

  • Members
  • 20 posts
  • OFFLINE
  •  
  • Local time:10:06 AM

Posted 31 October 2009 - 10:15 PM

ok done, nothing found by superantispyware
SUPERAntiSpyware Scan Log
http://www.superantispyware.com

Generated 10/31/2009 at 10:16 PM

Application Version : 4.29.1004

Core Rules Database Version : 4217
Trace Rules Database Version: 2122

Scan type : Complete Scan
Total Scan Time : 00:06:08

Memory items scanned : 285
Memory threats detected : 0
Registry items scanned : 7878
Registry threats detected : 0
File items scanned : 9458
File threats detected : 0

Edited by clarkstar, 01 November 2009 - 01:22 AM.


#4 clarkstar

clarkstar
  • Topic Starter

  • Members
  • 20 posts
  • OFFLINE
  •  
  • Local time:10:06 AM

Posted 01 November 2009 - 01:09 PM

still infected fyi. malware bytes found a file but avast still going crazy
Malwarebytes' Anti-Malware 1.41
Database version: 3064
Windows 6.0.6002 Service Pack 2 (Safe Mode)

10/31/2009 11:16:10 PM
mbam-log-2009-10-31 (23-16-10).txt

Scan type: Full Scan (C:\|)
Objects scanned: 323320
Time elapsed: 51 minute(s), 15 second(s)

Memory Processes Infected: 0
Memory Modules Infected: 0
Registry Keys Infected: 0
Registry Values Infected: 0
Registry Data Items Infected: 0
Folders Infected: 0
Files Infected: 1

Memory Processes Infected:
(No malicious items detected)

Memory Modules Infected:
(No malicious items detected)

Registry Keys Infected:
(No malicious items detected)

Registry Values Infected:
(No malicious items detected)

Registry Data Items Infected:
(No malicious items detected)

Folders Infected:
(No malicious items detected)

Files Infected:


C:\Windows\Temp\qbxw.tmp (Rogue.SecurityTool) -> Quarantined and deleted successfully.

man i just ran another malware bytes and got 70 files. i had avast turned off for a couple hours it keeps interrupting my term paper
Malwarebytes' Anti-Malware 1.41
Database version: 3064
Windows 6.0.6002 Service Pack 2

11/1/2009 11:28:48 AM
mbam-log-2009-11-01 (11-28-14).txt

Scan type: Quick Scan
Objects scanned: 97216
Time elapsed: 4 minute(s), 16 second(s)

Memory Processes Infected: 0
Memory Modules Infected: 0
Registry Keys Infected: 0
Registry Values Infected: 0
Registry Data Items Infected: 0
Folders Infected: 0
Files Infected: 70

Memory Processes Infected:
(No malicious items detected)

Memory Modules Infected:
(No malicious items detected)

Registry Keys Infected:
(No malicious items detected)

Registry Values Infected:
(No malicious items detected)

Registry Data Items Infected:
(No malicious items detected)

Folders Infected:
(No malicious items detected)

Files Infected:
C:\Windows\Temp\aane.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\aogi.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\bdvy.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\btrm.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\cgwp.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\crri.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\cxhb.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\dgtp.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\njcl.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\nkok.tmp (Rogue.SystemSecurity) -> No action taken.
C:\Windows\Temp\nord.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\nrpx.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\oxhf.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\peee.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\pwrx.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\gvfx.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\hrha.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\ibpg.tmp (Rogue.SystemSecurity) -> No action taken.
C:\Windows\Temp\isgh.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\jgxc.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\jusn.tmp (Rogue.SystemSecurity) -> No action taken.
C:\Windows\Temp\jxvw.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\tdvy.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\tqvu.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\tqwm.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\ttph.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\tucs.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\ukfi.tmp (Rogue.SystemSecurity) -> No action taken.
C:\Windows\Temp\uodw.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\urft.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\uwry.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\vybb.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\wkue.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\dpql.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\dxye.tmp (Rogue.SystemSecurity) -> No action taken.
C:\Windows\Temp\elsh.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\enmu.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\ethb.tmp (Rogue.SystemSecurity) -> No action taken.
C:\Windows\Temp\eyun.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\fbux.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\fcec.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\ffms.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\fjwv.tmp (Rogue.SystemSecurity) -> No action taken.
C:\Windows\Temp\glts.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\qixc.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\qjic.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\qkfy.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\qvbp.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\qwrh.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\rxnf.tmp (Rogue.SystemSecurity) -> No action taken.
C:\Windows\Temp\sxag.tmp (Rogue.SystemSecurity) -> No action taken.
C:\Windows\Temp\syfq.tmp (Rogue.SystemSecurity) -> No action taken.
C:\Windows\Temp\syof.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\tcgt.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\kpwj.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\kuca.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\kxqy.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\laoq.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\lead.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\lgtq.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\mjby.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\mkik.tmp (Rogue.SystemSecurity) -> No action taken.
C:\Windows\Temp\xbkt.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\xbpc.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\xffh.tmp (Rogue.SystemSecurity) -> No action taken.
C:\Windows\Temp\xfsa.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\yayr.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\yfxq.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\ypgv.tmp (Rogue.SecurityTool) -> No action taken.
C:\Windows\Temp\wxdn.tmp (Rogue.SystemSecurity) -> No action taken.

Edited by clarkstar, 01 November 2009 - 01:44 PM.


#5 Satalink

Satalink

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Atlanta, GA
  • Local time:12:06 PM

Posted 01 November 2009 - 04:18 PM

Try malwarebyte's anti-malware removal tool.. it's free. It picked up many things others did not. But it did not fix the problem in the end.

Look at your task scheduler. I noticed some malicious garbage in mine and disabled and deleted it.

I'll keep you posted if I find anything else... I have the same issue "Bredolab.AQ"

#6 Satalink

Satalink

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Atlanta, GA
  • Local time:12:06 PM

Posted 01 November 2009 - 04:47 PM

I'm tracking it down with microsoft's Process Explorer. It comes quick and vanishes, but it's definitely a service host process. Probably a registered service. I'll check into it.

#7 Satalink

Satalink

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Atlanta, GA
  • Local time:12:06 PM

Posted 01 November 2009 - 05:00 PM

Using Process Explorer, I've traced the creation of the C:\Windows\Temp\????.tmp AVAST reported Trojan Horse BREDOLAB.AQ to the process:

svchost.exe "Host Process for Windows Services" Microsoft Corporation 0:C:\Windows\system32\svchost.exe -k DcomLaunch

I've temporarily paused the service to ensure the reported virus stops.


Will keep you posted.

#8 Satalink

Satalink

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Atlanta, GA
  • Local time:12:06 PM

Posted 01 November 2009 - 05:14 PM

The trojan notification was coming in every 6 minutes. Since I've suspended the DcomLaunch service (PlugNPlay), it has not come back yet. I'll report back in an hour to make sure.

#9 rigel

rigel

    FD-BC


  • Members
  • 12,944 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:South Carolina - USA
  • Local time:12:06 PM

Posted 01 November 2009 - 06:47 PM

Before we start fixing anything you should print out these instructions or copy them to a NotePad file so they will be accessible. Some steps will require you to disconnect from the Internet or use Safe Mode and you will not have access to this page.

Please download DrWeb-CureIt and save it to your desktop. DO NOT perform a scan yet.

Reboot your computer in "Safe Mode" using the F8 method. To do this, restart your computer and after hearing your computer beep once during startup (but before the Windows icon appears) press the F8 key repeatedly. A menu will appear with several options. Use the arrow keys to navigate and select the option to run Windows in "Safe Mode".

Scan with Dr.Web CureIt as follows:
  • Double-click on launch.exe to open the program and click Start. (There is no need to update if you just downloaded the most current version
  • Read the Virus check by DrWeb scanner prompt and click Ok where asked to Start scan now? Allow the setup.exe to load if asked by any of your security programs.
  • The Express scan will automatically begin.
    (This is a short scan of files currently running in memory, boot sectors, and targeted folders).
  • If prompted to dowload the Full version Free Trial, ignore and click the X to close the window.
  • If an infected object is found, you will be prompted to move anything that cannot be cured. Click Yes to All. (This will move any detected files to the C:\Documents and Settings\userprofile\DoctorWeb\Quarantine folder if they can't be cured)
  • After the Express Scan is finished, put a check next to Complete scan to scan all local disks and removable media.
  • In the top menu, click Settings > Change settings, and unheck "Heuristic analysis" under the "Scanning" tab, then click Apply, Ok.
  • Back at the main window, click the green arrow "Start Scanning" button on the right under the Dr.Web logo.
  • Please be patient as this scan could take a long time to complete.
  • When the scan has finished, a message will be displayed at the bottom indicating if any viruses were found.
  • Click Select All, then choose Cure > Move incurable.
  • In the top menu, click file and choose save report list.
  • Save the DrWeb.csv report to your desktop.
  • Exit Dr.Web Cureit when done.
  • Important! Reboot your computer because it could be possible that files in use will be moved/deleted during reboot.
  • After reboot, post the contents of the log from Dr.Web in your next reply. (You can use Notepad to open the DrWeb.cvs report)

"In a world where you can be anything, be yourself." ~ unknown

"Fall in love with someone who deserves your heart. Not someone who plays with it. Will Smith


#10 Satalink

Satalink

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Atlanta, GA
  • Local time:12:06 PM

Posted 01 November 2009 - 07:27 PM

Here's as far as I go. This is a temporary "manual" fix. Hopefully, one of the great anti-virus companies out there will have a fix for this soon.

Using "Process Explorer" from Microsoft.

First, set the viewable columns by selecting the pull down menu "View", "Select Columns". Then select "Command Line".

This will give you the view you'll need to determine which svchost.exe you need to work on.

Now, from the process list, select the svchost.exe with the command line of "C:\Windows\system32\svchost.exe -k DcomLaunch"

Right click on this process and select "Properties"

In the properties window that displays, select the "Threads" tab. I have 10 threads running under this svchost.exe

Select each of the "ntdll.dll!Rt|DecoderPointer+0x9b" Threads and "Suspend" them all.

Now of the four, you just suspeneded, only one of them is the thread that is creating the reported trojan. You can resume each with about 10min in between until you find the one that you need to go back and suspend. With that, the problem is temporarally resolved until you reboot.

You need to restart the threads that I outlined as they are required services. Your system may start acting up if they are not running. The best way to identify the thread that is causing the reported trojan is to look at the number of "cycles" being used by the threads "ntdll.dll!Rt|DecoderPointer+0x9b". The one that has a really high "Cycle" count is the one that was causing the reported trojan on my pc.


Hope this helps until the guru's can code a fix for everyone.

Edited by Satalink, 02 November 2009 - 03:44 PM.


#11 clarkstar

clarkstar
  • Topic Starter

  • Members
  • 20 posts
  • OFFLINE
  •  
  • Local time:10:06 AM

Posted 02 November 2009 - 04:01 AM

Before we start fixing anything you should print out these instructions or copy them to a NotePad file so they will be accessible. Some steps will require you to disconnect from the Internet or use Safe Mode and you will not have access to this page.

Please download DrWeb-CureIt and save it to your desktop. DO NOT perform a scan yet.

Reboot your computer in "Safe Mode" using the F8 method. To do this, restart your computer and after hearing your computer beep once during startup (but before the Windows icon appears) press the F8 key repeatedly. A menu will appear with several options. Use the arrow keys to navigate and select the option to run Windows in "Safe Mode".

Scan with Dr.Web CureIt as follows:

  • Double-click on launch.exe to open the program and click Start. (There is no need to update if you just downloaded the most current version
  • Read the Virus check by DrWeb scanner prompt and click Ok where asked to Start scan now? Allow the setup.exe to load if asked by any of your security programs.
  • The Express scan will automatically begin.
    (This is a short scan of files currently running in memory, boot sectors, and targeted folders).
  • If prompted to dowload the Full version Free Trial, ignore and click the X to close the window.
  • If an infected object is found, you will be prompted to move anything that cannot be cured. Click Yes to All. (This will move any detected files to the C:\Documents and Settings\userprofile\DoctorWeb\Quarantine folder if they can't be cured)
  • After the Express Scan is finished, put a check next to Complete scan to scan all local disks and removable media.
  • In the top menu, click Settings > Change settings, and unheck "Heuristic analysis" under the "Scanning" tab, then click Apply, Ok.
  • Back at the main window, click the green arrow "Start Scanning" button on the right under the Dr.Web logo.
  • Please be patient as this scan could take a long time to complete.
  • When the scan has finished, a message will be displayed at the bottom indicating if any viruses were found.
  • Click Select All, then choose Cure > Move incurable.
  • In the top menu, click file and choose save report list.
  • Save the DrWeb.csv report to your desktop.
  • Exit Dr.Web Cureit when done.
  • Important! Reboot your computer because it could be possible that files in use will be moved/deleted during reboot.
  • After reboot, post the contents of the log from Dr.Web in your next reply. (You can use Notepad to open the DrWeb.cvs report)


whew that took forever!

Process in memory: C:\Windows\system32\wininit.exe:424;;BackDoor.Tdss.565;Eradicated.;
psqx.tmp;C:\Windows\temp;Trojan.Packed.682;Deleted.;
RegUBP2b-mike.reg;C:\Documents and Settings\All Users\Application Data\Spybot - Search & Destroy\Snapshots2;Trojan.StartPage.1505;Deleted.;

fyi still have the problem, as i posted this avast alerted

Edited by clarkstar, 02 November 2009 - 04:04 AM.


#12 rigel

rigel

    FD-BC


  • Members
  • 12,944 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:South Carolina - USA
  • Local time:12:06 PM

Posted 02 November 2009 - 08:19 AM

BackDoor.Tdss.565


This is a sign of a rootkit that steals passwords. I recommend changing all on-line passwords from a know clean computer.

Please follow this guide from step (6). Post a HJT log to the HJT forum and a Team member will be along to help you as soon as possible. You may wish to post a link back to this topic to see what was discussed thus far.

If you need any help with the guide, please let me know.

"In a world where you can be anything, be yourself." ~ unknown

"Fall in love with someone who deserves your heart. Not someone who plays with it. Will Smith


#13 Satalink

Satalink

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Atlanta, GA
  • Local time:12:06 PM

Posted 02 November 2009 - 12:09 PM

Moderators, please don't cut and paste corrective actions unless you know for certain it will clean the malware. Doing so only wastes readers time and adds confusion to actually correcting the problem.

FYI: My manual temporary fix is working.

#14 rigel

rigel

    FD-BC


  • Members
  • 12,944 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:South Carolina - USA
  • Local time:12:06 PM

Posted 02 November 2009 - 01:13 PM

TDSS is a known infection associated with a rootkit. It is BleepingComputer's policy to route those persons to the HJT forum where they can receive advanced malware assistance. This insures the member's computer is analyzed and cleaned according to the standards set forth by this forum.

Also note that any further assistance given beyond this post will be a violation of this policy.

For your reading, please reference:
Rootkit removal
How do I get help? Who is helping me?


If you have any questions, please feel free to PM me.

rigel
BleepingComputer Forums Global Moderator

"In a world where you can be anything, be yourself." ~ unknown

"Fall in love with someone who deserves your heart. Not someone who plays with it. Will Smith


#15 clarkstar

clarkstar
  • Topic Starter

  • Members
  • 20 posts
  • OFFLINE
  •  
  • Local time:10:06 AM

Posted 02 November 2009 - 07:28 PM

fyi i also have used Satalink's temp fix as i must still use my computer for schoolwork even while its infected. the temp fix helped by me not getting repeated virus pop ups. my googgle search is still redirecting like mad though and my pc overall is slowed quite a bit :thumbsup:

i posted as you instructed rigel, thanks

Edited by clarkstar, 02 November 2009 - 07:39 PM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users