#ChromeRemoteDesktop
Live, measured metrics for the hashtag #ChromeRemoteDesktop from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #chromeremotedesktop
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · mastodon.online (Mastodon public tags API) · fetched 2026-10-01 06:37 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.online (Mastodon public search API) · fetched 2026-10-01 06:37 UTCNo related tags with measured usage found for #chromeremotedesktop.
Live pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-10-01 06:37 UTCEverything below is measured over the latest 6 public posts (spanning ~34606 hours).
Posting hours (UTC)
Languages: English (3) · French (1) · Russian (1) · German (1)
Avg boosts / post: 0.5
Top of the latest posts
ENKI WhiteHat found Kimsuky abusing legitimate tools like Chrome Remote Desktop and AnyDesk for stealthy persistence in phishing campaigns against South Korea and Japan. #Kimsuky #ChromeRemoteDesktop #AnyDesk #Phishing #NorthKorea https://m
📢 Chrome Remote Desktop détourné en outil de surveillance furtive via patch de DLL 🔍 Contexte et découverte L'auteur, en cherchant à supprimer la bannière de notification de session CRD, a analysé les fichiers installés par l'application
# 🔒 Ransomware Alert ## Executive summary Chrome Remote Desktop can be repurposed as a covert remote‑access vector when an attacker installs the Windows MSI with local administrator privileges and configures a Google account to manage the
#chromeremotedesktop across platforms
every network with a public tag surfaceFollow #chromeremotedesktop straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/chromeremotedesktop