Telegram RegisterThe public register of Telegram

Channel

Apple Actively Exploited

@AppleActivelyExploited

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

3,047subscribers

-10 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001878225439
TypeChannel
Username@AppleActivelyExploited
CreatedBetween 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/AppleActivelyExploited

Growth

3,0473,0573,0526 August 2026 — 3,057 subscribers6 August 2026 — 3,057 subscribers7 August 2026 — 3,055 subscribers10 August 2026 — 3,052 subscribers13 August 2026 — 3,047 subscribers6 August 202613 August 2026
5 measurements spanning 7 days, net -10. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 3,046–3,059 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 13:173,047-5
10 Aug 2026, 09:523,052-3
7 Aug 2026, 15:143,055-2
6 Aug 2026, 23:453,057no change
6 Aug 2026, 23:333,057first reading

Engagement

20 posts held, back to 12 May 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pagesof Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 11 February 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

20 reactions across 10 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
20100.0%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 10 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 20reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 12 May 2025 to 11 February 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

11 Feb 2026, 18:45 UTC517 viewsread 8 August 2026

Update with a fix for an actively exploited vuln(s): visionOS 26.3 For: Apple Vision Pro (all models) Released: 11 Feb 2026 Security Document

11 Feb 2026, 18:45 UTC510 viewsread 8 August 2026

Update with a fix for an actively exploited vuln(s): watchOS 26.3 For: Apple Watch Series 6 and later Released: 11 Feb 2026 Security Document

11 Feb 2026, 18:45 UTC449 viewsread 8 August 2026

Update with a fix for an actively exploited vuln(s): tvOS 26.3 For: Apple TV HD and Apple TV 4K (all models) Released: 11 Feb 2026 Security Document

11 Feb 2026, 18:45 UTC409 views1 reactionsread 8 August 2026

Update with a fix for an actively exploited vuln(s): macOS Tahoe 26.3 For: macOS Tahoe Released: 11 Feb 2026 Security Document

1

11 Feb 2026, 18:45 UTC430 views1 reactionsread 8 August 2026

Update with a fix for an actively exploited vuln(s): iOS 26.3 and iPadOS 26.3 For: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 8th generation and later, and iPad mini 5th generation and later Released: 11 Feb 2026 Security Document

1

12 Dec 2025, 19:45 UTC586 views1 reactionsread 8 August 2026

Update with a fix for an actively exploited vuln(s): Safari 26.2 For: macOS Sonoma and macOS Sequoia Released: 12 Dec 2025 Security Document

1

12 Dec 2025, 19:30 UTC558 viewsread 8 August 2026

Update with a fix for an actively exploited vuln(s): visionOS 26.2 For: Apple Vision Pro (all models) Released: 12 Dec 2025 Security Document

12 Dec 2025, 19:30 UTC473 viewsread 8 August 2026

Update with a fix for an actively exploited vuln(s): watchOS 26.2 For: Apple Watch Series 6 and later Released: 12 Dec 2025 Security Document

12 Dec 2025, 19:30 UTC386 viewsread 8 August 2026

Update with a fix for an actively exploited vuln(s): tvOS 26.2 For: Apple TV HD and Apple TV 4K (all models) Released: 12 Dec 2025 Security Document

12 Dec 2025, 19:30 UTC763 views1 reactionsread 8 August 2026

Update with a fix for an actively exploited vuln(s): macOS Tahoe 26.2 For: macOS Tahoe Released: 12 Dec 2025 Security Document

1

12 Dec 2025, 19:30 UTC391 views2 reactionsread 8 August 2026

Update with a fix for an actively exploited vuln(s): iOS 18.7.3 and iPadOS 18.7.3 For: iPhone XS and later, iPad Pro 13-inch, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 7th generation and later, and iPad mini 5th generation and later Released: 12 Dec 2025 Security Document

2

12 Dec 2025, 19:30 UTC977 views3 reactionsread 8 August 2026

Update with a fix for an actively exploited vuln(s): iOS 26.2 and iPadOS 26.2 For: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 8th generation and later, and iPad mini 5th generation and later Released: 12 Dec 2025 Security Document

3

Showing the 12 most recent of 20 posts we hold for @AppleActivelyExploited. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Citation-graph rank

Citation-graph rank — 873,570 of 1,340,412entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 13 August 2026 — this entry's latest reading, not the date you are reading this.

“Apple Actively Exploited” (@AppleActivelyExploited), 3,047 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/AppleActivelyExploited.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.