AlaDes
Active Member
- Reaction score
- 35
- Location
- White Sulphur Springs, WV
Sometime last night Malwarebytes updated itself as it normally would on a regular basis. However, after the last update, it kept reporting that several services were trying to access a malicious website: 127.0.0.1.
Although I could ping google using the command line and get a response, I could not use any apps that access the internet, except Teamviewer. D7 even reported that I had no internet access. So, I ran Malwarebytes's flash scan and came up with nothing. I then tried to update its definition database and it could not do so because of no internet access.
After thinking for a few minutes and noticing the popups Malwarebytes kept giving me about blocking access to my own machine, I thought that maybe something may be wrong with Malwarebytes itself. Sure enough, after disabling its malicious website blocking utility I had internet access and was then able to update to the latest database. After the update was completed, I then re-enabled "malicious website blocking" and all was well.
Has anyone else ever had this wierd problem? I think maybe the database was corrupted or during the update process or Malwarebytes may have made a booboo lol.
Although I could ping google using the command line and get a response, I could not use any apps that access the internet, except Teamviewer. D7 even reported that I had no internet access. So, I ran Malwarebytes's flash scan and came up with nothing. I then tried to update its definition database and it could not do so because of no internet access.
After thinking for a few minutes and noticing the popups Malwarebytes kept giving me about blocking access to my own machine, I thought that maybe something may be wrong with Malwarebytes itself. Sure enough, after disabling its malicious website blocking utility I had internet access and was then able to update to the latest database. After the update was completed, I then re-enabled "malicious website blocking" and all was well.
Has anyone else ever had this wierd problem? I think maybe the database was corrupted or during the update process or Malwarebytes may have made a booboo lol.