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

i have something called MSIVXcount


  • Please log in to reply
9 replies to this topic

#1 qaws1900

qaws1900

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:11:01 PM

Posted 22 June 2009 - 01:58 PM

i have gotten rid of everything but this file: C:\Windows\System32\MSIVXcount
i have run mbam but it can't delete this file because my computer gets the blue screen when i restart in nonsafe mode.
i don't know what to do.

BC AdBot (Login to Remove)

 


#2 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,428 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:02:01 AM

Posted 22 June 2009 - 02:39 PM

Hi,I believe we can get that with this..

Next run ATF and SAS:

Note: On Vista, "Windows Temp" is disabled. To empty "Windows Temp" ATF-Cleaner must be "Run as an Administrator".

From your regular user account..
Download Attribune's ATF Cleaner and then SUPERAntiSpyware , Free Home Version. Save both to desktop ..
DO NOT run yet.
Open SUPER from icon and install and Update it
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 yet.

Now reboot into Safe Mode: How to enter safe mode(XP)
Using the F8 Method
Restart your computer.
When the machine first starts again it will generally list some equipment that is installed in your machine, amount of memory, hard drives installed etc. At this point you should gently tap the F8 key repeatedly until you are presented with a Windows XP Advanced Options menu.
Select the option for Safe Mode using the arrow keys.
Then press enter on your keyboard to boot into Safe Mode
.

Double-click ATF-Cleaner.exe to run the program.
Under Main "Select Files to Delete" choose: Select All.
Click the Empty Selected button.

If you use Firefox or Opera browser click that browser at the top and choose: Select All
Click the Empty Selected button.
If you would like to keep your saved passwords, please click No at the prompt.
Click Exit on the Main menu to close the program
.

NOW Scan with SUPER
Open from the desktop icon or the program Files list
On the left, make sure you check C:\Fixed Drive.
Perform a Complete scan. After scan,Verify they are all checked.
Click OK on the summary screen to quarantine all found items.
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.


Please ask any needed questions,post logs and Let us know how the PC is running now.
How do I get help? Who is helping me?For the time will come when men will not put up with sound doctrine. Instead, to suit their own desires, they will gather around them a great number of teachers to say what their itching ears want to hear....Become a BleepingComputer fan: Facebook

#3 qaws1900

qaws1900
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:11:01 PM

Posted 22 June 2009 - 07:22 PM

thank you for helping. I did what you asked and my computer is now running well.


SUPERAntiSpyware Scan Log
http://www.superantispyware.com

Generated 06/22/2009 at 04:39 PM

Application Version : 4.26.1004

Core Rules Database Version : 3950
Trace Rules Database Version: 1892

Scan type : Complete Scan
Total Scan Time : 00:56:26

Memory items scanned : 726
Memory threats detected : 0
Registry items scanned : 7273
Registry threats detected : 3
File items scanned : 29574
File threats detected : 66

Rogue.Component/Trace
HKLM\Software\Microsoft\1C66EF8C
HKLM\Software\Microsoft\1C66EF8C#1c66ef8c
HKLM\Software\Microsoft\1C66EF8C#Version

Adware.Tracking Cookie
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@cdn4.specificclick[2].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@questionmarket[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@ads.bootcampmedia[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@ads.us.e-planning[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@banner509[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@ad.doubleclick[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@ad.yieldmanager[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@serving-sys[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@clicksor[2].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@redirect.clickshield[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@ad2.adecn[2].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@realmedia[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@media6degrees[2].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@ad.zanox[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@ads.xapads[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@mediaplex[2].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@insightexpressai[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@socialmedia[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@iacas.adbureau[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@banners.bannersource[2].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@a1.interclick[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@pubmatic.lucidmedia[2].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@doubleclick[2].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@redhousebanner[2].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@dc.tremormedia[2].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@d3.zedo[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@ads.realtechnetwork[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@ads.lucidmedia[3].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@ads.lucidmedia[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@interclick[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@d.mediaforceads[2].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@adtech[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@adecn[2].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@metrics.ignitemedia[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@app.insightgrit[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@imrworldwide[2].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@collective-media[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@ads.imarketservices[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@atdmt[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@cache.trafficmp[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@myroitracking[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@statcounter[2].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@crackle[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@specificclick[2].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@validclick[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@specificmedia[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@tacoda[2].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@revsci[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@www.burstnet[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@adbrite[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@hits.revenuestreet[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@invitemedia[2].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@bs.serving-sys[2].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@burstnet[2].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@zedo[2].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@swi-adserver[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@trafficmp[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@rotator.adjuggler[3].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@rotator.adjuggler[4].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@rotator.adjuggler[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@rotator.adjuggler[5].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@apmebf[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@eas.apm.emediate[2].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@adserver.adtechus[1].txt
C:\Users\Owner\AppData\Roaming\Microsoft\Windows\Cookies\owner@ads.pointroll[1].txt

Trojan.Unclassified
C:\WINDOWS\SYSTEM32\MPFSERVICEFAILURECOUNT.TXT

#4 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,428 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:02:01 AM

Posted 22 June 2009 - 08:54 PM

Good job. Lets just Rerun MBAM like this:

Open MBAM in normal mode and click Update tab, select Check for Updates,when done
click Scanner tab,select Quick scan and scan.
After scan click Remove Selected, Post new scan log and Reboot into normal mode.
How do I get help? Who is helping me?For the time will come when men will not put up with sound doctrine. Instead, to suit their own desires, they will gather around them a great number of teachers to say what their itching ears want to hear....Become a BleepingComputer fan: Facebook

#5 qaws1900

qaws1900
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:11:01 PM

Posted 22 June 2009 - 09:06 PM

Malwarebytes' Anti-Malware 1.38
Database version: 2323
Windows 6.0.6002 Service Pack 2

6/22/2009 7:05:04 PM
mbam-log-2009-06-22 (19-05-04).txt

Scan type: Quick Scan
Objects scanned: 82296
Time elapsed: 7 minute(s), 55 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: 0

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:
(No malicious items detected)

#6 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,428 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:02:01 AM

Posted 22 June 2009 - 09:08 PM

Ok, good to go here.
Now you should Create a New Restore Point to prevent possible reinfection from an old one. Some of the malware you picked up could have been backed up, renamed and saved in System Restore. Since this is a protected directory your tools cannot access to delete these files, they sometimes can reinfect your system if you accidentally use an old restore point. Setting a new restore point AFTER cleaning your system will help prevent this and enable your computer to "roll-back" to a clean working state.

The easiest and safest way to do this is:
  • Go to Start > Programs > Accessories > System Tools and click "System Restore".
  • Choose the radio button marked "Create a Restore Point" on the first screen then click "Next". Give the R.P. a name, then click "Create". The new point will be stamped with the current date and time. Keep a log of this so you can find it easily should you need to use System Restore.
  • Then use Disk Cleanup to remove all but the most recently created Restore Point.
  • Go to Start > Run and type: Cleanmgr
  • Click "Ok". Disk Cleanup will scan your files for several minutes, then open.
  • Click the "More Options" tab, then click the "Clean up" button under System Restore.
  • Click Ok. You will be prompted with "Are you sure you want to delete all but the most recent restore point?"
  • Click Yes, then click Ok.
  • Click Yes again when prompted with "Are you sure you want to perform these actions?"
  • Disk Cleanup will remove the files and close automatically.
Vista Users can refer to these links: Create a New Restore Point and Disk Cleanup.
How do I get help? Who is helping me?For the time will come when men will not put up with sound doctrine. Instead, to suit their own desires, they will gather around them a great number of teachers to say what their itching ears want to hear....Become a BleepingComputer fan: Facebook

#7 fuzzes

fuzzes

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:02:01 AM

Posted 08 July 2009 - 01:41 PM

Hi,

I also got rid of everything but this file: C:\Windows\System32\MSIVXcount

I did the steps as described in this blog: ATF and SAS.
Here's my SAS log.

SUPERAntiSpyware Scan Log
http://www.superantispyware.com

Generated 07/08/2009 at 02:14 PM

Application Version : 4.26.1006

Core Rules Database Version : 3978
Trace Rules Database Version: 1918

Scan type : Custom Scan
Total Scan Time : 01:59:03

Memory items scanned : 271
Memory threats detected : 0
Registry items scanned : 6946
Registry threats detected : 0
File items scanned : 38850
File threats detected : 1

Rootkit.Agent/Gen
C:\WINDOWS\system32\MSIVXcount


I then rebooted normally and it seems to be running fine also but I reran MBAM again (after the update) and got the following log.


Malwarebytes' Anti-Malware 1.38
Database version: 2394
Windows 5.1.2600 Service Pack 3

2009-07-08 14:27:40
mbam-log-2009-07-08 (14-27-40).txt

Scan type: Quick Scan
Objects scanned: 102144
Time elapsed: 4 minute(s), 2 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\system32\MSIVXcount (Trojan.Agent) -> Delete on reboot.


It's the same thing as before. I don't know what else to do.
Any help is greatly appreciated.

#8 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,428 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:02:01 AM

Posted 08 July 2009 - 02:25 PM

Hi, did you run MBAM in Normal mode and reboot to normal after the scan? Rerun Rootrepeal also thanks.
How do I get help? Who is helping me?For the time will come when men will not put up with sound doctrine. Instead, to suit their own desires, they will gather around them a great number of teachers to say what their itching ears want to hear....Become a BleepingComputer fan: Facebook

#9 fuzzes

fuzzes

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:02:01 AM

Posted 08 July 2009 - 05:55 PM

Yeah, I had run MBAM in Normal Mode and rebooted to Normal.
But the Rootrepeal and MBAM combo worked like a charm! Here's the MBAM log after reboot from cleaning up with Rootrepeal.

Malwarebytes' Anti-Malware 1.38
Database version: 2394
Windows 5.1.2600 Service Pack 3

2009-07-08 18:52:40
mbam-log-2009-07-08 (18-52-40).txt

Scan type: Quick Scan
Objects scanned: 101904
Time elapsed: 5 minute(s), 47 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: 0

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:
(No malicious items detected)


All seems to be working fine now. I'll make sure to create a new restore point.
Thanks a bunch! Very appreciated!

#10 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,428 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:02:01 AM

Posted 08 July 2009 - 09:22 PM

:thumbsup: You're welcome ... Yes make a new Point.

Now you should Create a New Restore Point to prevent possible reinfection from an old one. Some of the malware you picked up could have been backed up, renamed and saved in System Restore. Since this is a protected directory your tools cannot access to delete these files, they sometimes can reinfect your system if you accidentally use an old restore point. Setting a new restore point AFTER cleaning your system will help prevent this and enable your computer to "roll-back" to a clean working state.

The easiest and safest way to do this is:
  • Go to Start > Programs > Accessories > System Tools and click "System Restore".
  • Choose the radio button marked "Create a Restore Point" on the first screen then click "Next". Give the R.P. a name, then click "Create". The new point will be stamped with the current date and time. Keep a log of this so you can find it easily should you need to use System Restore.
  • Then use Disk Cleanup to remove all but the most recently created Restore Point.
  • Go to Start > Run and type: Cleanmgr
  • Click "Ok". Disk Cleanup will scan your files for several minutes, then open.
  • Click the "More Options" tab, then click the "Clean up" button under System Restore.
  • Click Ok. You will be prompted with "Are you sure you want to delete all but the most recent restore point?"
  • Click Yes, then click Ok.
  • Click Yes again when prompted with "Are you sure you want to perform these actions?"
  • Disk Cleanup will remove the files and close automatically.
Vista Users can refer to these links: Create a New Restore Point and Disk Cleanup.
How do I get help? Who is helping me?For the time will come when men will not put up with sound doctrine. Instead, to suit their own desires, they will gather around them a great number of teachers to say what their itching ears want to hear....Become a BleepingComputer fan: Facebook




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users