This is a read-only archive of malwareremoval.com. No new posts or registrations. Privacy Page
Malware Removal Forums

Lan Proxy Hijacked, .... no matter what I try!

1 min read

This thread's last reply is from December 21, 2011, 1:59 AM UTC. Software, malware, and removal-tool advice below may be out of date — treat specific steps and download links with caution.

Hello really need some help here.
Recently a file was scanned as safe but on running it all the bells went off in the ISP provided McAfee software. Removing of course resulted in more of the same. Scans and fixes were tempory until the next boot. SpyBot found nothing. McAfee Stinger did a bit more. But it wsa not until running Malware bytes that the PUP FUN malware was spotted and removed. Since then nothing shows up on any scans and I tried loads.

My LAN Proxy is hijacked on every reboot. ProxyServer = http://79.160.222.20:8080

That is the only symptom I have. I have gone through hIJack this and removed anything remotely suspicious. I have also gone through the registry and checked entries suggested from googles results.

Here is my lastest HiJackthis log atached:
_____________________________________________

I have no idea how compromised my system is and what to do next besides format and reinstall.

The other issue I notice is that my Network is not availible to be viewed from this PCanymore. I have internet access through the LAN GATEWAY, but cannot see any workgrouped PC's. Other on the workgroup can see me but cannot access it. System is firewalled by McAfee.

Looking very forward gratefully to some proper qualified help!

Thanks

Attachments:

Please familiarize yourself with the forum rules: >Forum Posting Rules - Please Read<

In order for us to help you it is necessary that you provide us with DDS logs. Please follow the guideline at the link below to start a new topic and post your DDS logs by pasting them into your post. Do not utilize attachments.

This topic is now closed. Please start a new topic by following the guideline posted here: >Guideline for posting your DDS logs<