Malware removal

Stop unwanted website notifications

Identify a website notification, block its permission in Chrome, Edge, Firefox, or Safari, and handle any downloads, payments, or account exposure separately.

6 initial stepsbeginner guidanceReview changes before applying them

If an unwanted website is sending desktop notifications, the targeted fix is to block that site’s notification permission in the browser that granted it. A message claiming your antivirus expired or your computer has hundreds of infections may be website content dressed up as a security alert. Its text does not establish the state of your computer.

Start with the sender and surface, then use the relevant browser controls below. This guide covers desktop Chrome, Edge, Firefox, and Safari on their supported systems. Safari’s examples apply to Mac. Blocking a permission does not remove installed software or reverse anything you already supplied to a deceptive page.

First identify the notification without opening it

Look for the browser or application name and website address shown with the notification. Record those details and the time. Do not click the message to find out whether its claim is true, visit its support number, or use its download button. Keep screenshots private if they show account information or personal messages.

Separate the source from the wording. A website can display a security-company logo inside its message; that does not make the notification come from your installed security product. Open the installed product independently through the normal app menu if you need to check its actual status and recorded findings.

What you observeNext checkAppropriate route
A desktop alert names a website and browserThat browser’s saved notification permissionBlock the unwanted site below
A separate tab or window opens an advertisementPage content and pop-up settingsInvestigate random pop-ups
A named installed application sends its own promotionThe application’s settings and purposeReview that app; a website permission may be unrelated
Search or startup pages keep changingSettings, extensions, or their controllerInvestigate redirects
Your security app records a detectionFinding, item, action, and completionUse the appropriate security investigation

Seeing a notification after closing the browser is not by itself proof of a hidden infection. Microsoft documents that Edge notifications can continue with Edge closed; Apple describes the same possibility for Safari. Inspect the saved permission before concluding that closing the last browser window should have ended delivery.

If the device instead has active file locking or unexplained remote control, start urgent triage and get suitable help. Do not spend that incident’s first steps trying to silence notifications.

Block the unwanted site in Chrome or Edge

Reach settings from the browser’s own menu. You can change a saved permission without revisiting the suspicious website. Use the address shown by the browser or notification details rather than a domain invented from the advertisement’s logo.

In Chrome, open Settings → Privacy and security → Site settings → Notifications. Review the permitted sites and change the unwanted site’s permission to blocked. Google’s notification instructions also describe adding its address to the blocked list. Avoid blocking a similar-looking but different address and assuming the sender was handled.

In Edge, Microsoft’s current route is Settings → Privacy, search, and services → Site permissions → All sites. Select the recorded website, find its notification permission, and choose Block. If your installed version has a different arrangement, search settings for site permissions or notifications and use the current instructions for that version.

If more than one browser profile or browser is in use, inspect the one associated with the alert first. A block in one profile does not establish that every separate permission has changed. On a work or school browser, a locked or managed setting belongs with the administrator rather than a registry-editing workaround.

Revoke Firefox permission and save the change

Open Firefox’s own Settings and find Notifications in its permission settings. The section name varies by version; Mozilla’s current page includes Privacy & Security and Permissions and data terminology. Choose the settings button beside Notifications, locate the unwanted site, set its status to Block, then Save Changes.

Mozilla distinguishes Block from Remove Website. Removing the entry revokes its current grant but can allow a future request; blocking is the appropriate choice when you also want that site’s requests denied. Confirm that the change was saved rather than closing the dialog midway.

If you do not want new sites asking, the same permission controls offer a separate option to block new notification requests. That is a choice about future prompts, so review the existing allowed sites as well. Do not assume preventing new requests removed all earlier grants.

Handle Safari’s website and system controls on Mac

In Safari → Settings → Websites → Notifications, locate the unwanted website and choose Deny. Apple’s website-settings reference documents that per-site choice. It affects the website’s permission, rather than an unrelated application’s alerts.

Apple’s notification guide also describes System Settings → Notifications → Application Notifications, where the website can have Allow Notifications switched off. Deny the site’s permission in Safari when you want its website permission removed; merely changing the system presentation is a different control.

To stop future requests in Safari, deselect the option allowing websites to ask for notification permission in the Notifications section of Websites settings. Check the version selector in Apple’s guide if your Mac’s menus differ. Keep legitimate reminders only where you intentionally want them.

Check the result without inviting another exposure

Dismiss old notifications already present in the notification center using the normal system controls. An earlier stored alert is not evidence that a new message arrived after the block. Record the time of any genuinely new notification and compare its sender with the permission you changed.

For verification, use ordinary browsing you already intended to do; do not reopen the deceptive page or allow its prompt again. If new alerts continue, check whether they name another domain, browser profile, browser, installed web app, or desktop app. Each could need its own supported control. If the recorded site appears allowed again, note when that happened and whether the setting is managed.

Use extension removal when an unwanted browser add-on is involved and adware investigation when an installed application or broader unwanted advertising needs assessment. Clearing all browser data or resetting the whole computer is not the first answer to one identified notification permission.

Respond to what you already clicked or shared

Blocking notifications ends that permission’s role in delivery; it does not assess a program downloaded from an earlier alert. If you only saw or dismissed the message, do not invent a deeper exposure. If you followed it, record whether a file stayed closed, software ran, credentials were entered, payment was made, or remote control was approved.

Microsoft’s scam guidance explains impersonation and urgency. Use independent support routes rather than the number or chat embedded in the warning. For a saved but unopened item, follow download checks. For software execution, use the beginner flow and the platform-specific investigation. For shared credentials, use account recovery from a trusted device.

If money or private financial information was supplied, reach the relevant provider through its established channel. Do not pay an additional “cleanup” charge to the same warning. Keep this response separate from whether the unwanted alerts stopped.

This article is researched guidance. No website permission was granted, notification campaign was visited, or suspicious item was executed to prepare it.

Sources & documentation

Sources checked on 6 Oct 2026. Documentation research does not establish independent testing.

MalwareCleanupTools

Guides based on official documentation. About our content · Corrections policy