■■■■■ OSINT: Gro-Tracking via plane sound spectrum.

Channel
cKure
@cKure
On this record: Topic · Previous handles · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
7,276subscribers
+348 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001291965324 |
|---|---|
| Type | Channel |
| Username | @cKure |
| Description | ﷽ This channel was created in 2018 and contains content from the information security domain. This channel is primarily run by AI bots (n8n). Archive: ckure.esy.es Criticals: @ckuRED linkedin.com/company/ckure Support 📨 [email protected] |
| Created | Between 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/cKure |
Topic
Hacking & security — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 12 September 2026 and assigned it the closest of 31 fixed categories, at 96% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
Previous handles
Recorded in 2019 as “[+] Offensive Security ✪” — the title held for this same channel (matched by Telegram id, not by handle) in the Pushshift Telegram Dataset, a third-party archive captured in 2019-2020, years before this register made its own first observation. CC BY 4.0, Baumgartner, Zannettou, Squire & Blackburn (2020), Zenodo. A third party’s dated snapshot, not a measurement this register made itself.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Nov 2026, 03:18 | 7,276 | +16 |
| 7 Nov 2026, 22:07 | 7,260 | +7 |
| 4 Nov 2026, 09:09 | 7,253 | +10 |
| 1 Nov 2026, 01:49 | 7,243 | +8 |
| 28 Oct 2026, 21:56 | 7,235 | +21 |
| 26 Oct 2026, 04:28 | 7,214 | +17 |
| 23 Oct 2026, 07:27 | 7,197 | +10 |
| 20 Oct 2026, 04:01 | 7,187 | +12 |
| 17 Oct 2026, 05:08 | 7,175 | +9 |
| 14 Oct 2026, 06:58 | 7,166 | +18 |
| 10 Oct 2026, 19:00 | 7,148 | +21 |
| 4 Oct 2026, 21:17 | 7,127 | +38 |
| 25 Sept 2026, 05:59 | 7,089 | +38 |
| 17 Sept 2026, 05:17 | 7,051 | +16 |
| 13 Sept 2026, 09:55 | 7,035 | +34 |
| 9 Sept 2026, 02:38 | 7,001 | +16 |
| 4 Sept 2026, 00:37 | 6,985 | +13 |
| 31 Aug 2026, 11:47 | 6,972 | +5 |
| 28 Aug 2026, 03:58 | 6,967 | +2 |
| 25 Aug 2026, 11:44 | 6,965 | first reading |
Engagement
61 posts held, back to 24 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 29 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 8.73%
- avg views ÷ 7,276 subscribers
- Avg views / post
- 635
- 26 posts measured
- Reaction rate
- 0.627%
- reactions ÷ views · ER floor
- Posts in window
- 30
- of 61 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 12 of 26 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 10 November 2026 |
|---|---|
| Posts held | 61 (24 July 2026 – 10 November 2026) |
| Views total | 16,506 |
| Reactions total | 48 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Nov 2026, 17:34 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
- Photos
- ≈1,410
- Videos
- ≈478
- Links
- ≈12,200
Lifetime counters from Telegram’s own channel header, read 11 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
- Video runtime
- 23m 16s
- Average length
- 1m 22s
Measured directly from 17 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
85 reactions across 28 posts, in 20 distinct kinds. The most used accounts for 23.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 20 | 23.5% | |
| ❤ | 14 | 16.5% | |
| 👍 | 9 | 10.6% | |
| 🥱 | 7 | 8.24% | |
| 👏 | 6 | 7.06% | |
| 😱 | 6 | 7.06% | |
| 🤣 | 5 | 5.88% | |
| 👨💻 | 2 | 2.35% | |
| 🕊 | 2 | 2.35% | |
| 😁 | 2 | 2.35% | |
| 😈 | 2 | 2.35% | |
| 🥰 | 2 | 2.35% | |
| 🌭 | 1 | 1.18% | |
| 👀 | 1 | 1.18% | |
| 👎 | 1 | 1.18% | |
| 😍 | 1 | 1.18% | |
| 😴 | 1 | 1.18% | |
| 🙏 | 1 | 1.18% | |
| 🤔 | 1 | 1.18% | |
| 🥴 | 1 | 1.18% |
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 30 of the 61 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 87 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 61 most recent posts we hold, published 24 July 2026 to 10 November 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
Telegram’s own ‘edited’ marker: 3 of 30 posts held from the last 30 days (10.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
■■■■□ Israeli spyware disguises itself as advertisements on websites to hack phones “This is from Citizen Lab, which is at the University of Toronto. They unearthed what they call AdFection. So this is non-click spyware infecting phones, and the report came out that 45 AlJazeera journalists had this spyware on their phone, and it goes back to Israel. This is a fake company, an Israeli company that makes itself look l…
An HDMI cable may inadvertently emit signals that reveal the content displayed on a screen. As demonstrated by a laptop positioned to the left of a monitor, it is possible to reconstruct video from radio signals leaking from the HDMI connection. This phenomenon is known as TempestSDR. The process involves an antenna capturing the leakage, a HackRF radio recording the signal, and software converting the data back into…
😱6👨💻2
■■■■■ Apple Pays Up to $5,000,000 for One iPhone Exploit. Now Claude Is in Its Security Credits. https://x.com/RayanSMX/status/2117695435741524109
■■■■■ Calif CEO @XorNinja reveals how his team hacked an iPhone and maintained root access even after rebooting or updating the device, challenging one of the most common pieces of iPhone security advice. https://x.com/MTSlive/status/2118858788094857673
Interesting thread 🧵 on AI based reverse engineering. https://x.com/cabbitar/status/2118771202554839140
cKure pinned «🐉Autonomous pentest legion — AI commander + worker swarm + layered fact-intent graph. 3rd Tencent Intelligent Attack-Defense online champion (634 teams · 8h unattended · 1B tokens beat 4.5B). The Nüwa Test: give AIs Create/Language/History, let a civilization…»
🐉Autonomous pentest legion — AI commander + worker swarm + layered fact-intent graph. 3rd Tencent Intelligent Attack-Defense online champion (634 teams · 8h unattended · 1B tokens beat 4.5B). The Nüwa Test: give AIs Create/Language/History, let a civilization grow. https://github.com/N1nEmAn/sapper-v2
■■■■□ Interesting thread on a funny bug. https://x.com/IntCyberDigest/status/2118354675942428860
👀1
■■□□□ Interesting thread 🧵| Samsung CVE-2026-21155 https://x.com/unsignedbytes/status/2117806641055932905
■■■■□ Privacy: signal_app President meredith._.meredith and the abundanceinstitute’s Neil Chilson light up the #MoSSummit stage with opentodebateorg discussing the trade-offs between AI innovation and personal security.
🌭1
■■□□□ Thirty countries. More than half a billion recorded exposures. A covert campaign spreading anti-Muslim, anti-migrant and anti-Qatar propaganda through paid advertising, fake organisations and manipulated online content. The investigation traces evidence pointing towards an Israeli origin, while the client funding the operation remains unidentified. Thank you to marcowenjones and dsouzasohan for their meticulous…
Showing the 12 most recent of 61 posts we hold for @cKure. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Mentions
Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
Handles this channel named that no longer answer
- Dead references
- 2
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 2
- vacant every time we have ever looked
@cKure named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 2 posts, 9 November 2026 – 10 November 2026
named in 2 posts, 8 August 2026 – 9 August 2026
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@OffensiveTwitter · 21,323
Telegram ranks this channel #6 of 53 here — alongside 52 others — read 25 September 2026
@IRCyberGuardians · 21,099
Telegram ranks this channel #9 of 53 here — alongside 52 others — read 30 September 2026
@PentestingNews · 28,110
Telegram ranks this channel #13 of 46 here — alongside 45 others — read 12 September 2026
@Hide01 · 35,985
Telegram ranks this channel #13 of 41 here — alongside 40 others — read 2 September 2026
@ctinow · 40,308
Telegram ranks this channel #14 of 42 here — alongside 41 others — read 31 August 2026
@cybdetective · 28,012
Telegram ranks this channel #15 of 49 here — alongside 48 others — read 11 September 2026
@thehackernews · 165,587
Telegram ranks this channel #15 of 58 here — alongside 57 others — read 13 August 2026
@cibsecurity · 29,268
Telegram ranks this channel #17 of 58 here — alongside 57 others — read 10 September 2026
@thebugbountyhunter · 52,192
Telegram ranks this channel #17 of 60 here — alongside 59 others — read 25 August 2026
@RedBlueTM · 21,497
Telegram ranks this channel #20 of 36 here — alongside 35 others — read 23 September 2026
@vxunderground · 52,872
Telegram ranks this channel #23 of 41 here — alongside 40 others — read 24 August 2026
@CyberSecurityJobs · 18,743
Telegram ranks this channel #24 of 47 here — alongside 46 others — read 5 October 2026
@AllSecurityEngineeringCourses · 19,294
Telegram ranks this channel #25 of 37 here — alongside 36 others — read 3 October 2026
@Cyber_Security_Channel · 57,266
Telegram ranks this channel #26 of 71 here — alongside 70 others — read 23 August 2026
@cloudandcybersecurity · 21,706
Telegram ranks this channel #28 of 62 here — alongside 61 others — read 22 September 2026
@BlueTeamOps · 28,388
Telegram ranks this channel #29 of 53 here — alongside 52 others — read 11 September 2026
@noobtooscp · 23,591
Telegram ranks this channel #31 of 41 here — alongside 40 others — read 19 September 2026
@learningnets · 31,085
Telegram ranks this channel #32 of 56 here — alongside 55 others — read 7 September 2026
@codelivly · 34,994
Telegram ranks this channel #38 of 41 here — alongside 40 others — read 8 September 2026
@pafiha · 34,674
Telegram ranks this channel #65 of 71 here — alongside 70 others — read 13 September 2026
This channel appears in 20 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 11 November 2026 — this entry's latest reading, not the date you are reading this.
“cKure” (@cKure), 7,276 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/cKure.
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.