Ket

It's working fine now with updated package version 1.0.74973 Many thanks for the quick resolution.

Hi, cdn.ipsosinteractive.com.cdnga.net is being blocked by Malwarebytes. It is part of ipsos market research and I have been completing their surveys for years with no problems and they are a reputable company. It must be something with mbam's database, because at the same time it started blocking also www.tolunainsights.com.cdnga.net which is again a popular survey site. I have the Premium 4.6.1.280 version (upv 1.0.74969, cpv 1.0.2117) on windows 10. mbam 3.txt mbam 2.txt

Alright, this makes sense. Thank you very much for your support.

Hi, malwarebytes detected today WNetWatcher.exe as a riskware. The exe file is called Wireless Network Watcher by Nirsoft and can be found here: http://www.nirsoft.net/utils/wireless_network_watcher.html I have the current version v2.31 which I downloaded directly from Nirsoft's website. Below are the detection results: Malwarebytes www.malwarebytes.com -Log Details- Scan Date: 20/03/2023 Scan Time: 14:23 Log File: c49a439a-c72a-11ed-8d4a-10bf48939f89.json -Software Information- Version: 4.5.24.248 Components Version: 1.0.1952 Update Package Version: 1.0.66904 Licence: Premium -System Information- OS: Windows 10 (Build 19045.2728) CPU: x64 File System: NTFS User: DESKTOP-UTS7NHS\Laptop -Scan Summary- Scan Type: Threat Scan Scan Initiated By: Manual Result: Completed Objects Scanned: 336009 Threats Detected: 3 Threats Quarantined: 0 Time Elapsed: 4 min, 30 sec -Scan Options- Memory: Enabled Startup: Enabled Filesystem: Enabled Archives: Enabled Rootkits: Disabled Heuristics: Enabled PUP: Detect PUM: Detect -Scan Details- Process: 0 (No malicious items detected) Module: 0 (No malicious items detected) Registry Key: 0 (No malicious items detected) Registry Value: 0 (No malicious items detected) Registry Data: 0 (No malicious items detected) Data Stream: 0 (No malicious items detected) Folder: 0 (No malicious items detected) File: 3 RiskWare.NetworkWatcher, C:\USERS\LAPTOP\APPDATA\ROAMING\Microsoft\Windows\Recent\wnetwatcher.zip.lnk, No Action By User, 16967, 1133333, , , , , 18303BAA22EE3476283238F0408BBD4A, DB15CC04342E7E6364E0A660944826E51D26EF4EA3998EE58C5198E3E6B42434 RiskWare.NetworkWatcher, C:\USERS\LAPTOP\DOWNLOADS\WNETWATCHER.ZIP, No Action By User, 16967, 1133333, 1.0.66904, , ame, , 7BC2103E3EDD1BA5D78FE995817A6FA5, 3EC4F3BC8979E50F55505784E576519A29965FD5BE28244B97D3022F9FCEF4CB RiskWare.NetworkWatcher, C:\USERS\LAPTOP\PORTABLEAPPS\WNETWATCHER\WNETWATCHER.EXE, No Action By User, 16967, 1133333, 1.0.66904, , ame, , 60E1924798BB2B2F8608E26B37DA5B0B, 564D650EE9C6794B24C5A6497C316B9556F4866263664828EDF4A3CC03F2A8F3 Physical Sector: 0 (No malicious items detected) WMI: 0 (No malicious items detected) (end)

Malwarebytes www.malwarebytes.com -Log Details- Protection Event Date: 11/02/2023 Protection Event Time: 16:23 Log File: 6a053eea-aa28-11ed-87a1-10bf48939f89.json -Software Information- Version: 4.5.22.236 Components Version: 1.0.1909 Update Package Version: 1.0.65572 Licence: Premium -System Information- OS: Windows 10 (Build 19045.2486) CPU: x64 File System: NTFS User: System -Blocked Website Details- Malicious Website: 1 , C:\Program Files\Mozilla Firefox\firefox.exe, Blocked, -1, -1, 0.0.0, , -Website Data- Category: Phishing Domain: gateway.ipfs.io IP Address: 209.94.90.1 Port: 443 Type: Outbound File: C:\Program Files\Mozilla Firefox\firefox.exe (end)

Sorry, I should have done it already.

Hi, malwarebytes is blocking gateway.ipfs.io that I believe it's a false positive. I have reported it again in the past (see link below). Thank you.

Hi, recently mbam has started blocking ipfs.io. It is part of the hosting image facility of a private torrent tracker and I believe it to be safe. https://www.virustotal.com/gui/url/c6d1d72ff418cc18e5cde6e2c690737fa277e9a2b0c76957797ae4458f579248 Windows 10, malwarebytes 4.5.16.217 1.061437 1.01792

Hi, mbam seems to be blocking "anon.to" which is a URL redirector and shortener. Some websites use "anon.to" links to redirect to other sites. The ones I use are in this form: https://anon.to/?http://www.imdb.com/title/tt7270808 One out of 93 security vendors flagged it: https://www.virustotal.com/gui/url/bb5ce8d207b82ff000470d3ad3dba71dbadfe4626085bfc6ef81847c93664957?nocache=1

Hi and thanks for clarifying. My PC is i5 and therefore smart gesture is still needed. I'll whitelist it. Thanks a lot.

Hi, I scanned my PC today with adwcleaner and it detected Asus Smart Gesture as pre-installed software. I believe it is a false positive, as I only install drivers from Asus website. Please, see log below. AdwCleaner_Debug.log

At the moment I uninstalled completely malwarebytes, because the issue with starting up was affecting the mouse drivers update. The driver updates trigger mbam to start up with windows, and for some unknown reason, the drivers do not install properly, and I had to restart the computer several times in order for the update to work. Without mbam, drivers install fine. Just to remind you, in my case, the startup with windows is triggered with windows updates or driver updates or comodo software updates.

On my side definitely windows updates trigger it. Happened again with the recent windows 10 updates.

Hi and thanks for your help. At the moment I do not want to disable fast boot or enable UAC. I just hope that my observations may help in resolving the issue even for the particular settings I have. The startup issue was never there in previous versions of mbam and I have always had UAC disabled. The fast boot info are really interesting. I may give it a go at some point, though it still takes quite some time for my pc to start up. Cheers.

After all this time with mbam not starting at PC boot, it happened again yesterday. How it happened: I restarted my PC with comodo disabled and mbam started up, too. After that I scanned the pc with mbam and removed some PUPs and at restart mbam started again. I exited the program and at restart it did not start. Then I just happened to do some windows update and it started again at reboot. Exited mban and hasn't started since. So, for sure disabled (or updating) comodo and windows update trigger it. I think also use of adwCleaner may be triggering it.