Browser virus notifications: revoke the website permission at the source
A scary desktop alert can be a website notification; inspect its origin before following it.
Inspect the sender without clicking through
When an alarming browser notification appears, read the application and website name shown in the notification itself. Do not use its repair button, phone number, or payment link. A message that resembles an antivirus alert may have come from a website you previously allowed to send notifications. Take a redacted screenshot if you need help identifying it. This does not establish that every alert is harmless; it establishes that the source needs checking before action. Open the security application you actually use from its normal shortcut if you want to inspect its own status.
Open notification permissions directly
In Chrome, navigate through Settings, Privacy and security, Site Settings, and Notifications as described in Google's support guidance. Review the sites allowed to send notifications. Look for the origin displayed by the unwanted alert and change its permission through these controls. Read the exact domain carefully because similar-looking names can be different sites. Google also documents automatic restrictions for some intrusive or misleading notifications, but you can review your own permissions directly. Do not visit the suspect site again merely to request that it stop; the browser control provides the relevant authority.
Keep useful permissions selective
A calendar reminder or a work dashboard may have a legitimate notification role. Decide which permissions you intentionally want instead of either allowing everything or disabling all reminders permanently. For each retained site, ask whether you use it, whether its address matches the service you intended, and whether browser notifications provide a real benefit. A worked example is retaining a meeting site you recognize while blocking a news page that demanded permission before displaying an article. The decision is about the site origin and your preference, not about how official its notification graphics look.
Check what happened beyond the alert
If you only saw the notification and did not interact, revoking permission addresses that delivery channel. If you downloaded software, entered credentials, or paid someone through the message, investigate those separate actions through the appropriate official service. Keep a factual list of what you did and when. Use the real account provider's security page for credential concerns and the installed security tool's supported scan workflow for a downloaded program. Do not let an unsolicited remote helper turn a notification problem into remote access to your machine. The next step should match the actual exposure.
Verify the alerts stop
Close unwanted site tabs and observe whether notifications from that origin cease after the permission change. If alerts continue, compare the new sender rather than assuming the first action failed; another site or application may also be involved. Review the operating system's notification source information when needed. Teach other users of the shared computer to decline permission unless they want ongoing messages from that service. A clean notification list is easier to maintain when permission is a deliberate choice. The resolution is to control who can interrupt you and to handle any separate account or software issue with evidence.
Sources & further reading
Source links support the factual context. Practical examples and suggested workflows are original editorial guidance. Sources checked October 5, 2026.
Spotted something we should correct? Send a correction. Read our editorial policy.
