#purelogs
Live, measured metrics for the hashtag #purelogs from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #purelogs
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-07-30 17:17 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-07-30 17:17 UTCLive pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-07-30 17:17 UTCEverything below is measured over the latest 11 public posts (spanning ~23492 hours).
Posting hours (UTC)
Languages: English (11)
Avg boosts / post: 1.1
Top of the latest posts
zgRAT is a confusing catch-all label: both #PureLogs and #PureRAT commonly trigger "zgRAT" detections. Please don't label malware as #zgRAT. https://netresec.com/?b=267e877
📢🚨🎣 Fake purchase order emails are spreading fileless #PureLogs malware through malicious RAR archives, targeting Windows users and stealing browser credentials, crypto wallet data, VPN logins, Discord tokens, and more. Read: https://hac
📰 PureLogs Malware Variant Delivered via Multi-Stage Phishing Attack ⚠️ A new phishing campaign is deploying the PureLogs data-stealer! The attack uses a malicious JS file in a RAR attachment, then PowerShell & process hollowing to inject
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/purelogs