Google Chrome Blocks Over 7 Billion Unwanted Notifications Daily on Android
Google stated that Chrome protection systems blocked more than 7 billion unwanted notifications daily on Android throughout the first quarter of 2026. Websites have increasingly turned to browser notifications to push phishing pages, fraudulent payment requests, malware downloads, and other unsolicited content.
Chrome employs a layered "Swiss cheese" defense strategy in which multiple protective mechanisms overlap to cover gaps left by any single filter. If a suspicious notification bypasses one layer, subsequent filters are designed to catch it. The browser can automatically revoke notification permissions from sites that have not been visited for a long time or that frequently trigger security warnings. When permission is withdrawn, Chrome can also cancel any active subscription associated with the site.
Users who wish to restore access can do so through the Safety Hub section. Protection mechanisms evaluate not only individual sites but also related networks and coordinated activity involving service workers. Key signals include message volume, frequency of permission requests, user dwell time, and actual engagement levels.
Resources classified as overly intrusive face a strict limit of 1,000 messages per minute; any traffic exceeding this threshold receives an HTTP 429 response. Repeat offenders encounter tighter restrictions that are lifted only after a sustained period of compliant behavior. On Android, Google also redesigned permission request dialogs to be less intrusive, resulting in lower background activity and reduced battery consumption.
Users can review which sites are allowed to send notifications in desktop Chrome via Settings → Privacy and security → Site settings → Notifications. On Android the equivalent controls are located under Settings → Notifications.
Related articles
Russian Minister Proposes Blocking All SIM Cards of Scammers Banned in MAX Messenger
The head of Russia's Ministry of Digital Development has suggested expanding account bans in the MAX messenger to include full disconnection of all mobile numbers belonging to the same owner. Maksut Shadaev stated that simply restricting the messenger account is insufficient and that operators must continue countermeasures. The proposal also includes a cooling-off period preventing the individual from registering new numbers after a ban. Details on the duration of restrictions, data transfer procedures to operators, and appeal mechanisms remain undisclosed. Questions around accurate owner identification and cases of compromised or misused numbers are highlighted as critical for implementation. The measures target fraudsters specifically and would not apply automatically to every MAX rule violation.
Avito Develops Cyberdetective Browser Game to Train Employees on Real-World Attacks Using MITRE ATT&CK Techniques
Avito security awareness specialist Ilya Nikiforov created the browser-based Cyberdetective game over 74 days to move beyond traditional courses and train practical responses to attacks. The game places players in the fictional company Lumi where they control mascot Spok the honey badger, investigating six cases based on authentic attack chains documented in MITRE ATT&CK. Scenarios cover physical access via unlocked laptops, invoice domain spoofing, voice cloning of executives, MFA fatigue attacks, and evidence preservation during incident response. The project relied heavily on AI agents including Claude Code and Codex for coding and testing while Nikiforov handled scenario design, methodology, and acceptance. Additional AI tools generated art, animations, voiceovers, and music, resulting in 80 JavaScript modules, roughly 2,200 automated tests, and 18 distinct interactive mechanics. The game emphasizes safe mistake-making, chain-of-events thinking, and specific actions such as callback verification rather than blanket refusal of all requests.
Scammers Use *#62# USSD Command to Fabricate Surveillance Claims and Steal Victims' Funds
Fraudsters are exploiting the USSD command *#62# to convince targets that their phones are being tapped, then directing them to hand over cash to supposed couriers. The scheme begins with a familiar pretext such as a doorphone replacement or parcel delivery, after which the victim is tricked into revealing a verification code that the attackers themselves sent. A fake government official then claims the victim's account has been compromised and an extremist has been granted power of attorney. Victims are instructed to visit a counterfeit state website, enter *#62#, and interpret the displayed forwarding number as proof of interception. In reality the code only reveals call-forwarding settings for when the phone is unreachable, often showing a voicemail or missed-call service number. T-Bank warns that the displayed number has no connection to surveillance and urges anyone receiving such calls to hang up and contact the real organization through official channels.
Aroshka Cloud Faces Scrutiny Over Alleged False Claims of SOC 24/7 Operations and High-End Infrastructure
StackWorks has published the fourth installment in its investigative series on Aroshka Cloud, detailing how the cloud storage provider accused the studio of orchestrating a DDoS attack shortly after the third part appeared. The service published five posts claiming technical evidence linked StackWorks to the attack, including IP traces from Moscow, Ufa, and Stavropol, while asserting that its SOC 24/7 team mitigated a 3.5 Gbit/s assault within seconds. StackWorks responded with a pre-trial claim demanding removal of the posts and a public retraction, which Aroshka Cloud rejected within seven minutes. Analysis of the provider’s own Kwork job postings reveals requests for template-based support staff, a five-VDS server pool, and later up to eight NVIDIA H200 GPUs with InfiniBand, contradicting public statements about multi-country data centers and round-the-clock security engineers. Further inconsistencies include mismatched time zones in email headers, inflated user statistics, and reliance on the BeDrive script rather than custom development. The investigation continues with plans to involve law enforcement regarding suspicious visitor logs.