Advice Request BD Online Threat Prevention Critical Warning

Please provide comments and solutions that are helpful to the author of this topic.

Divine_Barakah

Level 41
Thread author
Verified
Top Poster
Well-known
Forum Veteran
May 10, 2019
3,075
12,729
3,969
Gaza Strip
Hi,


I installed BDIS a few hours ago and now when I was checking the notification I saw a critical warning

"msegde.exe attempted to establish a connection relying on an unmatching security certificate to sync.pmbmonetize.live. We blocked the connection to keep your data safe since the user certificate was issued for a different web address than the targeted one."

I don't use MS Edge and I have the "keep running MSedge when closed" option disabled.

Should I be concerned?
 
Hi,


I installed BDIS a few hours ago and now when I was checking the notification I saw a critical warning

"msegde.exe attempted to establish a connection relying on an unmatching security certificate to sync.pmbmonetize.live. We blocked the connection to keep your data safe since the user certificate was issued for a different web address than the targeted one."

I don't use MS Edge and I have the "keep running MSedge when closed" option disabled.

Should I be concerned?
May be some extension on Edge trying to establish connection in the background.
 
Two users on Reddit posted the same warning but with no answers.


That's what I get when trying to visit

Screenshot_2-12-2025_205459_sync.pmbmonetize.live.jpeg
 
I have this disabled on settings, with no sign for Edge in process manager.
I have it disabled too.
A FP is when a normal thing is detected as malicious. You don't even use MsEdge, so it is not normal.
That's why I'm concerned. I will provide logs to BD support and see.
A FP could be detecting connection to a malicious domain, while there is no actual connection.
Hmmmm I'm not sure if that's what happened. But I don't think that was the case.
 
Your BD's failure to reach it's server is suspicious, by the way. DNS is DNS with it's standard commands. Doesn't matter if you use this or that DNS.
When I installed BD, I was not using a custom DNS so it probably was my ISP DNS. When BD failed to connect, I changed the DNS to CloudFlare systemwide (DNS over HTTPS in Windows settings) but that did not fix the issue, so I contacted BD support and they recommended using Google DNS which did fix the issue.

So I'm not sure what happened or what caused the block as I'm still waiting for BD support to confirm what was wrong.


Now I'm using NextDNS systemwide and in browser settings and everything seems to be running as intended.


Now BD has reported 4 different vulnerabilities in Internet Explorer which I thought was removed from Windows? Maybe it is still there because I'm using Windows LTSC?