69% of Browsers Worldwide Vulnerable: How Chrome Sync Enables Stealth Surveillance Without Malware
Google Chrome’s ordinary sync feature can be covertly exploited to transform the browser into a powerful surveillance instrument. Attackers require neither malware nor advanced technical skills—only a few minutes of physical access to the target device to sign in with their own Google account and enable synchronization.
Specialists at Certo identified the technique after investigating multiple reports of digital stalking by intimate partners. In one documented case, a woman researching family lawyers and visiting websites that assist victims of domestic abuse discovered that her partner was able to recount the exact pages she had opened and the precise times she had visited them—despite her using only her personal phone and noticing no new applications.
The partner had briefly obtained the device, opened Chrome, signed in under his own Google credentials, and activated sync. From that moment, the victim’s browsing history began automatically uploading to his profile, which he could access from any other phone or computer anywhere in the world. No password belonging to the victim was needed, and login notifications were delivered exclusively to the attacker’s account rather than the device owner.
The risk extends far beyond visited websites. Chrome can also synchronize bookmarks, open tabs, autofill information, and stored passwords. If a victim later saves credentials for any service while the attacker’s profile remains active, those passwords become visible to the attacker, potentially enabling further account takeovers.
Chrome displays no prominent alert when a new profile is added or when synchronization begins. Many users never inspect which Google account is currently linked to the browser. According to StatCounter, Chrome commanded 69.65% of the global browser market in June 2026, meaning the simple attack vector could affect millions of people. The same method functions on smartphones as well as on Windows and macOS computers.
Certo has urged Google to introduce temporary notifications whenever a new account is connected and to display the currently synced profile persistently. Such measures would allow device owners to detect unauthorized access quickly without disrupting normal browser operation.
Users can verify the connected profile through browser settings. On iPhone and iPad, the account address appears at the top of the settings section. On Android, Windows, and macOS, it is visible after clicking the profile icon. Any unfamiliar account should be removed immediately, and passwords for important services—especially those saved in Chrome—should be changed.
For sensitive searches, the Incognito mode can be used, as visited pages are not added to the synchronized history. Devices should be protected with strong passcodes and biometric authentication, and users should review whether additional fingerprints or facial-recognition data have been enrolled by third parties.
Related articles
Yandex Apps Leak Pre-Trigger Audio Buffers, Payment Data, and Contacts via Reverse Engineering
Reverse engineering of Yandex Search and Yandex Browser APKs reveals extensive data collection practices on Android devices. The apps maintain a server-controlled pre-trigger audio buffer that captures up to three seconds or more of microphone input before the wake word Alice is detected. WiFi fingerprinting, full contact book synchronization via ContentObserver, and transmission of PAN and CVV details to mobpayment.yandex.net occur before tokenization. Additional findings include 94 JavaScript Bridge methods, logcat exfiltration with AES encryption, hardcoded Yandex DNS servers, and a native surveillance library named libquarkenstein_daemons.so. The analysis also covers passive geolocation, cell tower data collection, and inventory of installed applications including competitors such as Chrome, Firefox, WhatsApp, and Telegram. These mechanisms operate under remote configuration flags and bypass several Android privacy restrictions through manifest queries.
TSPU Filtering Disrupts Timeweb Cloud Servers: Diagnosis, CDN Failures, and Reverse Proxy Bypass
Russian hosting provider Timeweb Cloud experienced widespread TSPU-based DPI filtering starting in early June that selectively blocked TLS handshakes on port 443 while leaving SSH, ICMP, and TCP connectivity intact. The issue affected multiple providers including Beget and Selectel, was publicly acknowledged by Timeweb on June 5, and proved highly variable by region, operator, and time of day. Attempts to mitigate via new IP addresses or Timeweb's own CDN failed due to poisoned caches and platform outages, while Yandex Cloud CDN blocked all POST requests required for WordPress functionality. A working solution involved deploying a minimal nginx reverse proxy on another Russian cloud VPS that preserves full HTTP methods, handles certificate synchronization, and routes ACME challenges correctly. Timeweb support later closed tickets without resolution after requesting ineffective mtr traces that cannot detect DPI behavior. The case highlights systemic challenges in diagnosing state-mandated filtering and the limitations of standard network diagnostics against selective TLS interference.
UnifiedPush and Public ntfy.sh: Why Push Notifications Fail on Android Without Google Services
Developers building a messenger without Google services adopted UnifiedPush with the public ntfy.sh instance as the default distributor and push server. Production logs revealed that four out of five delivery attempts failed from day one, with error codes 507, 429, and 400 dominating. The 507 errors occurred because ntfy from Google Play relies on Firebase for instant delivery, leaving no active subscriber visible to the server when FCM is unavailable. Rate-limit 429 responses were triggered against the recipient's IP rather than the sender, collapsing under carrier-grade NAT used by mobile users. WebPush endpoints additionally rejected requests missing the mandatory TTL header. The team ultimately deployed a self-hosted ntfy instance and an embedded distributor inside the app to bypass these constraints.
Innovative Tunneling Techniques Leverage File Storage, IMAP, Meek, and NTP for Covert Connectivity
A new wave of experimental tunneling tools has emerged for establishing network connectivity through unconventional channels such as shared file storage, email accounts, legacy CDN protocols, and NTP. File-Tunnel enables TCP proxying by writing data to common storage backends including S3 and WebDAV, allowing traffic to blend with ordinary object storage access. True IMAP Tunnel (Secure) turns an IMAP mailbox into a bidirectional transport by storing encrypted frames as draft messages, supporting providers like Gmail, Outlook, and Yandex while offering optional AES-256-GCM encryption. Meek, originally from the Tor project, is being repurposed as a standalone pluggable transport that uses HTTP POST requests with session headers to traverse CDNs and shared hosting environments. ntptun implements IP-over-NTP and UDP-over-NTP by embedding payloads in NTP extension fields, with poll and push modes for downstream traffic and integration options with GOST for KCP-based proxies. These methods target dissidents and network experimenters seeking resilient bypass techniques against filtering and surveillance.