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 13 September 2026 and assigned it the closest of 31 fixed categories, at 93% 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.
Growth
17 measurements spanning 65 days, net +55. 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 4,215β4,373 and does not start at zero.
Measurement log β every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
11 Oct 2026, 23:40
4,288
-16
5 Oct 2026, 02:59
4,304
-9
26 Sept 2026, 04:01
4,313
-28
15 Sept 2026, 20:58
4,341
+2
11 Sept 2026, 22:01
4,339
-8
7 Sept 2026, 07:17
4,347
-7
2 Sept 2026, 05:04
4,354
+5
29 Aug 2026, 20:54
4,349
-2
27 Aug 2026, 01:12
4,351
+6
23 Aug 2026, 20:04
4,345
-1
20 Aug 2026, 09:52
4,346
-2
17 Aug 2026, 14:25
4,348
-7
14 Aug 2026, 16:54
4,355
+4
11 Aug 2026, 10:34
4,351
+77
8 Aug 2026, 09:33
4,274
+41
7 Aug 2026, 17:02
4,233
no change
7 Aug 2026, 16:49
4,233
first reading
Engagement
15 posts held, back to 28 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 4 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 15 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
37 reactions across 11 posts, in 3 distinct kinds. The most used accounts for 45.9% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
π₯
17
45.9%
β€
15
40.5%
π
5
13.5%
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 11 of the 15 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 37 reactions in total: the kind of figure the paragraph above means by βa reaction total printed elsewhere on the pageβ.
Measured over the 15 most recent posts we hold, published 28 July 2026 to 8 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.
π¨ Smuggler_Hunter can do more than scan real targets .
It can also be used against PortSwigger Web Security Academy labs.
In this test, Smuggler_Hunter:
β Discovered the endpoint
β Tested CL.TE
β Tested TE.CL
β Confirmed a TE.CL behavior
β Generated a report automatically
This is exactly how I want the tool to evolve:
Not just a scanner.
A practical research tool for understanding, testing and validating HTTP Rβ¦
π¨ You've seen the $62K+ HTTP Request Smuggling bounties.
You've seen the methodology.
Now... here's what I've been building.
Introducing Smuggler_Hunter.
A dedicated tool for HTTP Request Smuggling research, built from the workflow I've used in real-world bug bounty hunting.
The goal isn't to replace the researcher.
It's to automate the repetitive work and help you focus on finding and validating real vulnerabiβ¦
π New HTTP Request Smuggling Tool...
I've been working on a new tool focused on discovering HTTP Request Smuggling vulnerabilities. Would you like early access when it's released?
π₯ Absolutely!64%
π€ I need more details.14%
π Show me a demo first.18%
β Not interested.4%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
π₯ I secured a $3000 bounty using Secret Hunter π₯
π°OLD BUT GOLDπ°
Back when the tool was still private, I was testing its API PATH feature , a function that extracts hidden endpoints from JS files and source pages.
During the scan, I found an endpoint with debug mode enabled, leaking the database username and password.
Using the credentials, I accessed the database with full super admin privileges and closed the issβ¦
π‘ Everyone sees the bounty.
Very few people see what happens before it.
β Hours of reconnaissance.
β Understanding the application.
β Validating every assumption.
β Writing a report that gets accepted.
This is exactly why I wrote 3 Bugs That's Pay.
The book isn't a payload collection.
It's the methodology I personally use to find real-world vulnerabilities.
π₯ Current Offer
π 3 Bugs That's Pay β Volume II OR Voβ¦
π° Two more 3-digit bug bounty rewards XXX$
Both findings were discovered using Secret Hunter, the tool I built to automate reconnaissance and uncover hidden attack surfaces.
These are exactly the kinds of real-world findings that inspired 3 Bugs That's Pay β Volume II, where I explain the methodology behind discovering HTTP Request Smuggling vulnerabilities.
π₯ Special Offer
π 3 Bugs That's Pay β Volume II
β 1 Monβ¦
π Welcome to the Kassem_S94 Ecosystem
Many new members have joined our community recently, so here's a quick introduction to what we've been building over the years.
This isn't just a Telegram channel.
It's an ecosystem built for Bug Bounty Hunters and Security Researchers.
π Books
β’ 3 Bugs That's Pay β Volume I
β’ 3 Bugs That's Pay β Volume II (HTTP Request Smuggling)
π Recon & Automation
β’ Secret Hunter
β’ XOXO
β¦
β€2
Showing the 12 most recent of 15 posts we hold for @kassems94. 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.
Polls
The poll we hold for this entry, as Telegram rendered it when we read the post. A pollβs figures keep moving after that, so each one is dated.
π New HTTP Request Smuggling Tool...
I've been working on a new tool focused on discovering HTTP Request Smuggling vulnerabilities. Would you like early access when it's released?
π₯ Absolutely!64%
π€ I need more details.14%
π Show me a demo first.18%
β Not interested.4%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only β there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each optionβs share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each optionβs own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 15 most recent posts we hold, published 28 July 2026 to 8 August 2026. Telegram labels each poll by kind β an anonymous poll, a quiz, a closed set of final results β and that label is reproduced rather than paraphrased.
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 October 2026 β this
entry's latest reading, not the date you are reading this.
βBug-bounty-tipsππ°β (@kassems94), 4,288 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/kassems94.
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.