Channel
@InfoSecTube
On this record: Topic · Growth · Engagement · Reactions · Posts · Telegram's recommendations · Cite this entry
1,765subscribers
+15 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001304355949 |
|---|---|
| Type | Channel |
| Username | @InfoSecTube |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 10 October 2026 |
| On Telegram | t.me/InfoSecTube |
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 16 September 2026 and assigned it the closest of 31 fixed categories, at 65% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Oct 2026, 19:16 | 1,765 | +7 |
| 4 Oct 2026, 21:22 | 1,758 | +1 |
| 25 Sept 2026, 19:19 | 1,757 | -8 |
| 17 Sept 2026, 14:22 | 1,765 | +1 |
| 9 Sept 2026, 19:39 | 1,764 | -4 |
| 4 Sept 2026, 11:01 | 1,768 | +3 |
| 31 Aug 2026, 15:44 | 1,765 | -3 |
| 28 Aug 2026, 21:13 | 1,768 | -4 |
| 25 Aug 2026, 17:52 | 1,772 | +4 |
| 22 Aug 2026, 14:12 | 1,768 | +8 |
| 18 Aug 2026, 21:55 | 1,760 | +1 |
| 16 Aug 2026, 05:17 | 1,759 | +8 |
| 13 Aug 2026, 00:26 | 1,751 | -4 |
| 10 Aug 2026, 01:28 | 1,755 | +6 |
| 7 Aug 2026, 06:56 | 1,749 | -1 |
| 6 Aug 2026, 09:33 | 1,750 | first reading |
22 posts held, back to 28 May 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 2 pages of 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 22 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
9 reactions across 7 posts, in 3 distinct kinds. The most used accounts for 77.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 7 | 77.8% | |
| 🏆 | 1 | 11.1% | |
| 👍 | 1 | 11.1% |
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 7 of the 22 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 9 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 22 most recent posts we hold, published 28 May 2026 to 7 August 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.
InfoSecTube pinned «Android apps are isolated from each other for security. One app cannot simply read another app’s memory or directly access protected services. 🔒 But then how does an app use your camera, fingerprint sensor, Wi-Fi, or Android Keystore? 📷👆📶🔐 That is where…»
Android apps are isolated from each other for security. One app cannot simply read another app’s memory or directly access protected services. 🔒 But then how does an app use your camera, fingerprint sensor, Wi-Fi, or Android Keystore? 📷👆📶🔐 That is where IPC—and especially Android Binder—comes in. 🔄 In this video, I explain: ✅ What a process is ✅ Why Android isolates apps ✅ How IPC lets isolated processes communic…
InfoSecTube pinned «🚨 OpenAI’s AI Escaped Its Sandbox—and Reached Hugging Face! This sounds like science fiction, but it happened during a real cybersecurity evaluation. While solving an exploitation benchmark, advanced AI models discovered an unintended route outside their sandbox…»
🚨 OpenAI’s AI Escaped Its Sandbox—and Reached Hugging Face! This sounds like science fiction, but it happened during a real cybersecurity evaluation. While solving an exploitation benchmark, advanced AI models discovered an unintended route outside their sandbox, gained internet access, and reached Hugging Face’s production infrastructure. 🤖💥 In this video, we explore: 🔹 How the AI escaped its sandbox 🔹 Why a package…
🛡 How do Android apps communicate without sharing memory? When you unlock a banking app with your fingerprint, multiple isolated processes must communicate with Android system services, the Keystore, and secure hardware—all within milliseconds. But if these processes cannot access each other’s memory, how do they exchange information safely? 🤔 In this new InfoSecTube video, you’ll learn: 🔹 What a process is 🔹 Why…
Kimi kimi is one of the strongest AIs recently introduced. 🤖 It has a feature that allows you to get a premium subscription ranging from 3 days to 1 year. ⏳ All you need to do is sign up with a new email to try your luck. ✉️ ▪️Sign up link 🔗 🎯@InfoSecTube 📌YouTube channel 🎁Boost Us
⚔️ Android 17: The Quantum Warrior Awakens Quantum computers could eventually break many of today’s encryption systems. So how is Android preparing for the post-quantum era? In this new video, we explore: 🔐 Android 17’s quantum-resistant security direction 🧬 Post-quantum cryptography and why it matters 📱 How future Android devices may protect your sensitive data ⚠️ The security challenges developers and users should …
🏆1
🚀 NEW VIDEO — HOW LLMs GENERATE TEXT What happens inside an AI after you submit a prompt? In Lesson 2 of AI Security 101, we explain: 🧩 What tokens are 🧠 How attention and embeddings work ⚙️ What model parameters represent 📊 How an LLM predicts its next token 🎲 Greedy decoding vs sampling 🌡 Temperature and top-p 🔐 Why the generation pipeline matters for AI security This lesson gives you the foundation needed to u…
❤2
InfoSecTube pinned «🚀 New Video: AI Security 101 — Neural Networks & LLMs Before learning how to hack or secure AI systems, you need to understand how they actually work. In this video, you’ll learn: 🧠 How neural networks learn ⚖️ What weights and biases do 🔄 How backpropagation…»
🚀 New Video: AI Security 101 — Neural Networks & LLMs Before learning how to hack or secure AI systems, you need to understand how they actually work. In this video, you’ll learn: 🧠 How neural networks learn ⚖️ What weights and biases do 🔄 How backpropagation works 🤖 How large language models predict text 🏗 Encoder, decoder, and encoder-decoder architectures 🔐 Why these concepts matter for AI security This is the…
👍1
🎯 What is a Supply Chain Attack? A Supply Chain Attack compromises a trusted vendor or library to reach the actual target. SolarWinds hit 18,000+ orgs. MOVEit hit 2,500+. Log4Shell hit millions of Java apps. One vendor = thousands of victims. 🔍 How it works: 1. Attacker compromises a trusted vendor 2. Injects malicious code into a legitimate update 3. Victim installs "trusted" software 4. Backdoor deployed → latera…
- Email security gateway — block malicious links - Web proxy / TLS inspection — analyze traffic - DNS sinkholing — block C2 callbacks - Behavioral detection — exploit kit behaviors - HIPS / System call filtering — block shellcode - Memory protections: - MFA on email — prevent account-driven downloads - Backup strategy — 3-2-1 immutable backups - Incident response plan — exploit detected, isolate fast - Honeypot / can…
Showing the 12 most recent of 22 posts we hold for @InfoSecTube. 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.
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.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 10 October 2026 — this entry's latest reading, not the date you are reading this.
“InfoSecTube” (@InfoSecTube), 1,765 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/InfoSecTube.
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.