About:Blank..se.dll..hijacker..etc

Discussion in 'Malware Help (A Specialist Will Reply)' started by jovo, Mar 14, 2005.

  1. chaslang

    chaslang MajorGeeks Admin - Master Malware Expert Staff Member

    Are you sure you properly changed ALL occurrences of NotWindows to Windows?

    Do not delete the other key yet and do not reboot yet?

    I want you to try the below first. We were trying to rename the HKLM\software\microsoft\NOTwindows key by taking permission of it. Adrynalyne suggested to me that we select HKLM and take ownership at that level. Try that! But obviously since you already merged in a new Windows registry hive you cannot rename NotWindows to Windows. So try changing it to OldWindows and see what happens.
     
  2. jovo

    jovo Private E-2

    Hi Chaslang,

    Yes I'm pretty sure. Took a good few minutes for notepad to make all the changes. After I added the reg file my Windows Explorer view was restored to how it was before. Also testing my network connection proved successfull. Whereas just after the erroneous renaming I was prompted for the Windows disc! So I'm inclined to *think* that we're back on track!

    What is your opinion?

    No I've not deleted the incorrect value nor have I rebooted.

    I went ahead and took ownership of HKLM. The entiries in the "Key properties"... "Including all subkeys:" cycled through again!? What's the significance of this. Previously it was owned by Builtin/Administrators after successfully taking ownership it is now owned by Zeon/Administrator.

    How do I reverse this ownership?

    I was then able to successfully rename "NotWindows" to "oldWindows". Again the egg timer cursor appeared for a while during the renaming. No flagged messages at all.

    Yesterday, I had disconnected my troubled PC from the router and had no "attacks". This morning I needed to transfer a registry backup file (Erunt) to my older PC (the one I'm using for mail and forum comms at the mo). I connected up to the router, completed the data transfer and triggered Norton for a LiveUpdate..while that was happening I had an attack.

    I attach a current HJT log file. I've not "fixed" anything. All the usual suspects are there except for an additional 02 BHO (no name) entry that usually relates to the dll found in the two 018 rows! This has been seen before, sometimes it's there, sometimes it's not. The important fact is that the prefix of the dll found at 02 (when it is present) and both 018 rows keep changing between "fixes" and re-infection!

    'scuse the novel but I want you to have as much info as possible!

    Where do we go from here?

    Thanks
     

    Attached Files:

  3. chaslang

    chaslang MajorGeeks Admin - Master Malware Expert Staff Member

    Okay! At some point we will have to delete the OldWindows registry hive but not yet. It would be a good idea to use Erunt to backup your registry since you are familiar with this program.

    You still have the original problem we were trying to fix. I need you to go back to what I gave you in message #27 and what you answered in message #28 to see if the AppInit_DLL still exist and to see what it is named now (it could have changed).

    Then you would procede to msg #29 and be careful to execute that step properly.

    Let me know when you complete this.
     
  4. jovo

    jovo Private E-2

    Value had not changed. Carried out process of deleting and renaming successfully. Exited and reloaded Reglite but value is back!
     
  5. chaslang

    chaslang MajorGeeks Admin - Master Malware Expert Staff Member

    Did you erase the AppInit_DLLs entry while it was renamed to Not Windows?
     
  6. jovo

    jovo Private E-2

    Yes.
     
  7. jovo

    jovo Private E-2

    Also do remember that I'm in normal mode with all normal services/ processes running and I had that attack earlier. I've not "fixed" anything as per your earlier request. I've also not rebooted yet.
     
  8. chaslang

    chaslang MajorGeeks Admin - Master Malware Expert Staff Member

    Yes I remember. We need to get the AppInit_DLL entry removed.

    Try fixing it again but this time do it in the real key:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\\AppInit_DLLs

    and in the one we named OldWindows
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OldWindows NT\CurrentVersion\Windows\\AppInit_DLLs

    Then reload reglite. Is it gone in either of them?

    Also try this:
    Copy the contents of the Quote Box below to Notepad. Then click File and then Save As. Change the Save as Type to All Files. Name the file appfix.reg and then click save. (make sure you save it somewhere you can find it. Saving it to your Desktop may make that easy.) Then double-click on the appfix.reg file on your desktop (or locate it with Windows Explorer and double click on it if not saved to the Desktop) and when it prompts to merge say yes
    Now use Registrar Lite again and tell me if the same filename appears in AppInit_DLLs or is it gone.
     
  9. jovo

    jovo Private E-2

    Correction, the key I incorrectly renamed is this one:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OldWindows, not oldWindowsNT !

    I tried deleting value in real key but it just came back.

    Trying the second fix now.
     
  10. jovo

    jovo Private E-2

    No, it came back! Same value.
     
  11. jovo

    jovo Private E-2

    What if I were to delete the key: "AppInit_DLLs" entirely not just its value?
     
  12. jovo

    jovo Private E-2

    Nope, that doesn't work either. Both when renaming Windows and when not.
     
  13. chaslang

    chaslang MajorGeeks Admin - Master Malware Expert Staff Member

    NO!!! Only the value that it there is to be erased. The AppInit_DLLs key is required.

    Read all of the below before proceding.

    I think it is time we reboot this system and run the same commands to erase that AppInit_DLLs entry from safe mode.

    And while in safe mode after erasing the entry but before renaming the registry key back to Windows. Locate the c:\windows\system32\hlpadm.dll file. And first right click on it and get Properties and Version information. Let's see if there is a company name associated with it. Then try renaming the file (by right clicking on it and selecting rename) to hlpadm.ddd.

    Then change the registry key back to Windows. Now see if the AppInit_DLLs field is empty.

    Then reboot in normal mode and post a new HJT log and tell me what happened. Double check the AppInit_DLLs field after reboot too.
     
  14. jovo

    jovo Private E-2

    [/QUOTE] Locate the c:\windows\system32\hlpadm.dll file.[/QUOTE]

    File does not exist :confused: Folder ops set to show hidden files & folders also system files.
     
  15. chaslang

    chaslang MajorGeeks Admin - Master Malware Expert Staff Member

    Did you look for it in safe mode after changing the Windows registry key to NotWindows?

    Are you using this PC to send messages here now?
     
  16. jovo

    jovo Private E-2

    Yes, I rebooted into safe mode. Loaded Reglite renamed Windows, deleted value only, did visual search in Windows Explorer, then Search function three times. Have not changed notWindows back yet.

    No, I'm using another PC running Win 98 SE, been using it all along.
     
  17. chaslang

    chaslang MajorGeeks Admin - Master Malware Expert Staff Member

    Okay rename the Registry Key back! And tell me if you can see the file now.

    Windows Search will not show hidden/system files unless setup correctly (similar to what we did for Windows Explorer).


    If you use Search, you need to do the following:
    Click Search and the Select "All files and folders"
    Enter the filename in the "All or part of the file name:" box
    Now select "More advanced options"
    Make sure the following check boxes are checked:
    - Search system folders
    - Search hidden files and folders
    - Search subfolders
    Then click the Search button.
     
  18. jovo

    jovo Private E-2

    Search set-up was correct. No joy finding that file I'm afraid!
     
  19. chaslang

    chaslang MajorGeeks Admin - Master Malware Expert Staff Member

    Okay while still in safe mode look for the below two files and if found, try to delete them:

    C:\Documents and Settings\Administrator\Local Settings\Temp\se.dll
    C:\WINDOWS\system32\fipa.dll

    Tell me the results. Then reboot to normal mode and post a new HJT log.
     
  20. jovo

    jovo Private E-2

    Neither files where found. I attached the new log.
     

    Attached Files:

  21. chaslang

    chaslang MajorGeeks Admin - Master Malware Expert Staff Member

    Do you see this file now:

    C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\se.dll
     
  22. jovo

    jovo Private E-2

    No.

    FYI: When I get these attacks NAV messages say that a virus has been detected and deleted, usually something like fipa.dll or fodo.dll seemingly random characters followed by .dll. Normally at about the same time Windows flags an error message stating that "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\se.dll module could not be found"

    Attached are some screen grabs.
     

    Attached Files:

  23. jovo

    jovo Private E-2

    Again just for more info. I've attached my NAV virus alerts log file.

    Interestingly, the top 11 or 12 lines are entries that happened not too long ago ( it's 23.20 GMT now) while I was trying the deleting of the AppInit_DLLs value. The 10th one down is the file "fipa.dll" that you referred to earlier from my previous HJT log!

    NAV appears to be deleting the file se.dll (and others) and Windows then reports that an error in loading has occurred because the module could not be found?
     

    Attached Files:

  24. chaslang

    chaslang MajorGeeks Admin - Master Malware Expert Staff Member

    Since NAV is apparently not doing a complete job in fixing the problem all it ends up doing is getting in the way of us properly fixing the problem. I think we are going to have to uninstall NAV and maybe Spybot too (if it is blocking things) so we can bring everything to the surface and fix it. We are not seeing what we need to see. And I'm surprised we could not fix the AppInit_DLL we saw. Perhaps Symantec was blocking that too. I would recommend leaving the PC physically disconnected (unplug cable) from the internet while we work on this since you have another PC to communicate with. Then uninstall NAV and Spybot. Reboot and post a new HJT log. And run Registar Lite and find out what is in AppInit_DLLs now.
     
  25. jovo

    jovo Private E-2

    Uninstall NAV! What would be the implications regarding my subscription history and Live update service? Would a re-install look like a fresh/ new install to Symantec? Any idea?

    PC has been unplugged for most of the post history, I'll keep it that way.

    It's approaching midnight now so I'm of to bed. Thanks for your efforts again.
     
  26. chaslang

    chaslang MajorGeeks Admin - Master Malware Expert Staff Member

    Yes! It would look like you re-installed it and you would have to get any updates. But it is preventing the removal of this problem because it is not fixing the source. It is only seeing the symptom. The other approach would be for you to call them and ask them why they do not fix the problem properly. You paid for the program and expect it to work. Ask them when they are going to have a real fix.

    This kind of problem happens often in trying to fix some malware infections. Sometimes the cleaning tools themselves can get in the way causing conflicts with each other or with the manual removal steps. This happens because the see the actions of the other program (or our manual steps) as typical malware actions and they block them.
     
  27. jovo

    jovo Private E-2

    An update,

    Following the difficulty we had with deleting the:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\\AppInit_DLLs value, I did a bit of digging and came up with this:

    Since there is a value there and it refers to a dll file I used a command I found while trawling that unregisters a dll file.

    Start, Run, Type "regsvr32 /u /s hlpadm.dll" . Doing a HJT scan now reveals this file.
    Now I simply use the technique of renaming Windows to Windows1, deleting the value "c:\windows\system32\hlpadm.dll". Then after renaming Windows1 back to Windows I rebooted.

    Job done! The value does not appear in the new HJT log! It is also gone from the Reglite app view.

    I am hopeful that now my PC is clean and that I can keep it that way!

    Finally thanks for a great site, resource and support.

    Jovo
     
  28. chaslang

    chaslang MajorGeeks Admin - Master Malware Expert Staff Member

    Thanks for getting back to us with this info Jovo. Quite often we do use regsvr to unregister DLL files. For some reason I just did not think of it here. Most of the time it has not been necessary to unregister these AppInit_DLLs inorder to remove them. Your may have been a new breed that we now have come to understand.

    So have you deleted the DLL file and all the SE.DLL file? And all associated bad lines are now gone from your HJT log?
     
  29. jovo

    jovo Private E-2

    Yes I have and I think so. I'll attach the latest one for your info and check back to see if you recommend any further action. I'm going to go online again tomorrow using the newly cleansed PC. Hopefully I won't have to start posting again asking for help!

    Finally if you have any further tips or links to info that I can use to help prevent these hijacks please feel free to post them.
     

    Attached Files:

  30. chaslang

    chaslang MajorGeeks Admin - Master Malware Expert Staff Member


MajorGeeks.Com Menu

Downloads All In One Tweaks \ Android \ Anti-Malware \ Anti-Virus \ Appearance \ Backup \ Browsers \ CD\DVD\Blu-Ray \ Covert Ops \ Drive Utilities \ Drivers \ Graphics \ Internet Tools \ Multimedia \ Networking \ Office Tools \ PC Games \ System Tools \ Mac/Apple/Ipad Downloads

Other News: Top Downloads \ News (Tech) \ Off Base (Other Websites News) \ Way Off Base (Offbeat Stories and Pics)

Social: Facebook \ YouTube \ Twitter \ Tumblr \ Pintrest \ RSS Feeds