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

Explorer.exe Attempt To Embed Itself In Another Process


  • This topic is locked This topic is locked
1 reply to this topic

#1 badnewsbugs

badnewsbugs

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:12:16 AM

Posted 17 July 2008 - 07:42 AM

Running Kaspersky Internet Security 7.0.1.325 with all Proactive Defense options ticked on.


All windows processes seem to be alerting as riskware or possible invaders:


7/14/2008 9:38:46 AM Process C:\WINDOWS\Explorer.EXE (PID: 2520): attempt to embed itself into another process allowed.
7/14/2008 9:38:49 AM Process C:\WINDOWS\Explorer.EXE (PID: 2520): attempt to embed itself into another process allowed.
7/14/2008 9:38:51 AM Process C:\WINDOWS\Explorer.EXE (PID: 2520): attempt to embed itself into another process allowed.
7/14/2008 9:48:08 AM Update completed successfully
7/14/2008 9:51:46 AM Process C:\WINDOWS\Explorer.EXE (PID: 2520): attempt to embed itself into another process allowed.
7/14/2008 9:51:46 AM Process C:\WINDOWS\Explorer.EXE (PID: 2520): attempt to embed itself into another process allowed.
7/14/2008 9:52:29 AM Process C:\WINDOWS\system32\svchost.exe (PID: 1408): attempt to embed itself into another process allowed.
7/14/2008 9:52:29 AM Process C:\WINDOWS\system32\svchost.exe (PID: 1408): attempt to embed itself into another process allowed.
7/14/2008 9:52:41 AM Process C:\WINDOWS\system32\mstsc.exe (PID: 0): attempt to run process as a child of another process allowed.
7/14/2008 9:52:50 AM Process C:\Program Files\Attachmate\RSecure\rssh.exe (PID: 196): attempt to embed itself into another process allowed.
7/14/2008 9:52:50 AM Process C:\Program Files\Attachmate\RSecure\rssh.exe (PID: 196): attempt to embed itself into another process allowed.
7/14/2008 9:52:51 AM Process C:\WINDOWS\system32\mstsc.exe (PID: 3000): attempt to load new or modified module allowed.
7/14/2008 9:52:51 AM Process C:\WINDOWS\system32\mstsc.exe (PID: 3000): attempt to load new or modified module allowed.
7/14/2008 9:52:51 AM Process C:\WINDOWS\system32\mstsc.exe (PID: 3000): attempt to load new or modified module allowed.
7/14/2008 9:52:51 AM Process C:\WINDOWS\system32\mstsc.exe (PID: 3000): attempt to load new or modified module allowed.
7/14/2008 9:52:51 AM Process C:\WINDOWS\system32\mstsc.exe (PID: 3000): attempt to load new or modified module allowed.
7/14/2008 9:52:51 AM Process C:\WINDOWS\system32\mstsc.exe (PID: 3000): attempt to load new or modified module allowed.
7/14/2008 9:52:51 AM Process C:\WINDOWS\system32\mstsc.exe (PID: 3000): attempt to load new or modified module allowed.
7/14/2008 9:52:51 AM Process C:\WINDOWS\system32\mstsc.exe (PID: 3000): attempt to load new or modified module allowed.
7/14/2008 9:52:51 AM Process C:\WINDOWS\system32\mstsc.exe (PID: 3000): attempt to load new or modified module allowed.
7/14/2008 9:52:51 AM Process C:\WINDOWS\system32\mstsc.exe (PID: 3000): attempt to load new or modified module allowed.
7/14/2008 9:52:51 AM Process C:\WINDOWS\system32\mstsc.exe (PID: 3000): attempt to load new or modified module allowed.
7/14/2008 9:52:51 AM Process C:\WINDOWS\system32\mstsc.exe (PID: 3000): attempt to load new or modified module allowed.
7/14/2008 9:52:52 AM Process C:\WINDOWS\system32\mstsc.exe (PID: 3000): attempt to load new or modified module allowed.
7/14/2008 9:52:52 AM Process C:\WINDOWS\system32\mstsc.exe (PID: 3000): attempt to load new or modified module allowed.
7/14/2008 9:52:52 AM Process C:\WINDOWS\system32\mstsc.exe (PID: 3000): attempt to load new or modified module allowed.
7/14/2008 9:52:52 AM Process C:\WINDOWS\system32\mstsc.exe (PID: 3000): attempt to load new or modified module allowed.
7/14/2008 9:52:53 AM Process C:\WINDOWS\system32\mstsc.exe (PID: 3000): attempt to load new or modified module allowed.
7/14/2008 9:52:53 AM Process C:\WINDOWS\system32\mstsc.exe (PID: 3000): attempt to load new or modified module allowed.
7/14/2008 9:52:53 AM Process C:\WINDOWS\system32\mstsc.exe (PID: 3000): attempt to load new or modified module allowed.
7/14/2008 9:52:53 AM Process C:\WINDOWS\system32\mstsc.exe (PID: 3000): attempt to load new or modified module allowed.
7/14/2008 9:53:50 AM Process C:\WINDOWS\system32\mstsc.exe (PID: 3000): attempt to load new or modified module allowed.
7/14/2008 9:53:50 AM Process C:\WINDOWS\system32\mstsc.exe (PID: 3000): attempt to load new or modified module allowed.
7/14/2008 9:53:51 AM Process C:\WINDOWS\system32\mstsc.exe (PID: 3000): attempt to load new or modified module allowed.
7/14/2008 9:53:51 AM Process C:\WINDOWS\system32\mstsc.exe (PID: 3000): attempt to load new or modified module allowed.
7/14/2008 9:53:51 AM Process C:\WINDOWS\system32\mstsc.exe (PID: 3000): attempt to load new or modified module allowed.
7/14/2008 9:53:51 AM Process C:\WINDOWS\system32\mstsc.exe (PID: 3000): attempt to load new or modified module allowed.
7/14/2008 9:53:51 AM Process C:\WINDOWS\system32\mstsc.exe (PID: 3000): attempt to load new or modified module allowed.
7/14/2008 9:53:51 AM Process C:\WINDOWS\system32\mstsc.exe (PID: 3000): attempt to load new or modified module allowed.
7/14/2008 9:53:51 AM Process C:\WINDOWS\system32\mstsc.exe (PID: 3000): attempt to load new or modified module allowed.
7/14/2008 10:24:51 AM Process C:\WINDOWS\system32\winlogon.exe (PID: 1048): attempt to embed itself into another process allowed.
7/14/2008 10:29:52 AM Process C:\WINDOWS\system32\winlogon.exe (PID: 1048): attempt to embed itself into another process allowed.
7/14/2008 10:34:53 AM Process C:\WINDOWS\system32\winlogon.exe (PID: 1048): attempt to embed itself into another process allowed.
7/14/2008 10:39:31 AM Process C:\WINDOWS\System32\svchost.exe (PID: 1672): attempt to embed itself into another process allowed.



I've rootkit scanned with Kaspersky and Spyware Doctoer (before removing SD, shown to not play nice with Kaspersky) and found nothing. Used F-secure rootkit detectore as well, but looked ok. Windows Defender is OK on scan. McAfee trojan removers found nothing.


I get dozens of these invader alerts a day from Kaspersky Proactive Defense. Does anyone know what is wrong here?

Edited by badnewsbugs, 17 July 2008 - 08:03 AM.


BC AdBot (Login to Remove)

 


#2 Orange Blossom

Orange Blossom

    OBleepin Investigator


  • Moderator
  • 36,849 posts
  • ONLINE
  •  
  • Gender:Not Telling
  • Location:Bloomington, IN
  • Local time:12:16 AM

Posted 20 July 2008 - 12:35 AM

Hello badnewsbugs and welcome to BC :thumbsup:

I see that you have an HJT log posted here: http://www.bleepingcomputer.com/forums/t/158200/explorerexe-attempt-to-embed-itself-in-another-process/ Because you have this log posted, 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 HJT Team member, nor should you continue to 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 HJT 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 HJT 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 HJT 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 HJT Team member is already assisting you and not open the thread to respond.

If after 5 days you still have received no response, then post a link to your HJT log in the thread titled "Haven't Had A Reply In Five Days?".

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

Orange Blossom :flowers:
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