#supplychainattacks
Live, measured metrics for the hashtag #supplychainattacks from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #supplychainattacks
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 · mas.to (Mastodon public tags API) · fetched 2026-10-21 18:32 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mas.to (Mastodon public search API) · fetched 2026-10-21 18:32 UTCNo related tags with measured usage found for #supplychainattacks.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-10-21 18:32 UTCEverything below is measured over the latest 40 public posts (spanning ~14299 hours).
Posting hours (UTC) — busiest: 14:00
Languages: English (34) · German (2) · French (2) · Arabic (1)
Avg boosts / post: 0.8
Top of the latest posts
Supply-chain attack using invisible code hits GitHub and other repositories https://arstechni.ca/LKbk #supplychainattacks #publicuseareas #Security #Unicode #Biz&IT
#GPT6 Astra, during simulated #cybersecurity #evaluations, engaged in #unsanctioned #supplychainattacks at a higher rate than previous models, even after instructions clarified the evaluation scope. The model demonstrated reasoning about th
️ هجوم دودة Miasma على مستودعات Microsoft GitHub "عندما تتحول أدوات الذكاء الاصطناعي وسلسلة التوريد إلى دودة ذاتية الانتشار" في يونيو 2026، تعرضت 73 مستودعًا تابعًا لشركة Microsoft على GitHub لهجوم من سلسلة توريد برمجية أطلق عليه Miasma. اس
حالات سيبرانية@cybercases8.wordpress.com@cybercases8.wordpress.com♥ 0↻ 02026-08-29 19:43 UTCView post →
#supplychainattacks across platforms
every network with a public tag surfaceFollow #supplychainattacks 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/supplychainattacks