A notification from a site you barely remember allowing can still look official, and Microsoft says scammers count on that. The Edge Dev Blog describes how the browser's Scareware blocker surfaced malicious notification abuse using client-side detection.
No new Edge version ships with this post. If you want to act on it, open Edge notification settings and cut off the sites you don't recognize.
In this guide, I have covered:
Contents
What the Scareware blocker found in notifications
Website notifications are meant to be useful. Microsoft’s official Edge Dev Blog post names the everyday cases: a new message, an upcoming event, an important update from a service you trust.
Scammers use the same channel. The post says they are turning that browser feature into a path for abuse, and that client-side threat detection in Edge’s Scareware blocker is what surfaced the activity.
Two things are easy to blur here. The notification is the delivery route. The abuse is what rides on it.
Why there’s no Edge version to install
If you came looking for a build number, there isn’t one. This is a security research post about detecting notification abuse, not a release note.
The source names no stable or beta Edge version, no platform rollout, no phased schedule. Nothing to wait for, and nothing to update by hand because of this announcement.
What you can act on is the permission underneath the whole story: which sites Edge is allowed to send notifications for.
No version-specific manual update step follows from this announcement.
How to review Edge notification access
A notification you don’t remember signing up for is worth a two-minute check, and the control sits with you rather than with Microsoft.
The guide to configuring site notifications in Edge on the computer shows where the settings live. The quick pass:
- Open Site notification settings in Edge on the computer.
- Review the sites allowed to show notifications.
- Revoke access for any site you don’t recognize or no longer use.
You’ll know it worked when the list holds only sites you would expect to hear from. If a suspicious notification still arrives, verify it through the service itself before you click anything.
Frequently Asked Questions
A security post without a version number raises the same handful of questions every time.
Did Microsoft announce a new Edge version?
No. The post names no version number and no release channel. It covers the Scareware blocker’s client-side detection of malicious notification abuse, not a numbered browser release.
What does client-side threat detection mean here?
It is the detection approach Microsoft credits in its Scareware blocker account. According to the post, it surfaced malicious activity that abused website notifications.
Are all Edge notifications dangerous?
No. The source says notifications are useful for new messages, event reminders, and important updates from services you trust. It describes abuse by scammers, not a flaw in every notification.
What should I do if a notification looks suspicious?
Check that site’s notification permission and confirm the message through the service itself. A notification on its own is not proof it came from the real service.
