Telegram RegisterThe public register of Telegram
Telegram profile photo for Web_Priv8

Channel

Web_Priv8

@web_priv8

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

712subscribers

-14 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001193897992
TypeChannel
Username@web_priv8
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live30 October 2026
Measurements held9
Confirmed unchanged1 time, most recently 30 October 2026
On Telegramt.me/web_priv8

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 20 September 2026 and assigned it the closest of 31 fixed categories, at 62% 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.

Growth

7127267196 August 2026 — 726 subscribers6 August 2026 — 726 subscribers14 August 2026 — 725 subscribers22 August 2026 — 724 subscribers30 August 2026 — 722 subscribers8 September 2026 — 724 subscribers1 October 2026 — 717 subscribers10 October 2026 — 716 subscribers30 October 2026 — 712 subscribers6 August 202630 October 2026
9 measurements spanning 84 days, net -14. 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 710–728 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Oct 2026, 04:39712-4
10 Oct 2026, 09:39716-1
1 Oct 2026, 05:16717-7
8 Sept 2026, 06:20724+2
30 Aug 2026, 00:55722-2
22 Aug 2026, 07:58724-1
14 Aug 2026, 01:57725-1
6 Aug 2026, 23:16726no change
6 Aug 2026, 23:04726first reading

Engagement

20 posts held, back to 13 January 2022 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page 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 March 2024. An engagement rate over an empty window would be a number about nothing.

Reaction mix

44 reactions across 7 posts, in 3 distinct kinds. The most used accounts for 61.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍2761.4%
🔥1125.0%
👏613.6%

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 9 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 44 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 13 January 2022 to 15 March 2024, 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

15 Mar 2024, 14:00 UTC≈2,320 views0 reactionsread 6 August 2026

Source Code Disclosure in ASP.NET apps https://swarm.ptsecurity.com/source-code-disclosure-in-asp-net-apps/ #ASP @web_priv8

Signed Sina Doosti

15 Mar 2024, 13:56 UTC≈2,030 viewsread 6 August 2026

CRLF Injection https://moopinger.github.io/blog/crlf/injection/2024/03/12/CRLF-Injection-Shenanigans.html #CRLFi @web_priv8

Signed Sina Doosti

25 Sept 2023, 20:29 UTC≈2,240 views11 reactionsread 6 August 2026
Photo

LinkedIn - HTTP Request Smuggling (CL.0) leads to mass redirect users to attacker server without user interaction https://twitter.com/r00t98/status/1706400919695274128 سعی میکنم بقیه رو هم منتشر کنم... #Smuggling #BugBounty @web_priv8

🔥6👍5

Signed Sina Doosti

11 Sept 2023, 00:36 UTC≈1,910 views5 reactionsread 6 August 2026

Knocking on the Front Door (client side desync attack on Azure CDN) https://blog.jeti.pw/posts/knocking-on-the-front-door/ یه محقق تونسته آسیب پذیری CSD روی CDN آژور مایکروسافت کشف کنه، حدود دو ماه پیش بود که خودم هم تونستم همچین چیزی ازش کشف کنم اما یکم متفاوت تر، 6k بانتی داد و اگه شد رایتاپش رو مینویسم بعدا. #Smuggling @web_priv8

👍4👏1

Signed Sina Doosti

4 Sept 2023, 01:29 UTC≈1,710 views3 reactionsread 6 August 2026

Web AppSec Interview Questions https://tib3rius.com/interview-questions.html @web_priv8

🔥2👍1

Signed Sina Doosti

14 Mar 2023, 08:52 UTC≈2,700 viewsread 6 August 2026

Convert reflected XSS to DOM-based XSS to bypass length limit filter https://www.sudokaikan.com/2019/03/convert-reflected-xss-to-dom-based-xss.html This method also works for stored XSS. #XSS #Bypass @web_priv8

Signed Sina Doosti

21 Dec 2022, 10:55 UTC≈2,920 views15 reactionsread 6 August 2026
Photo

Soon I will published my tool in github for detect http request smuggling vulnerability. https://twitter.com/r00t98/status/1605330608372453376 #Tool #Smuggling #BugBounty #BugBountyTip @web_priv8

👍9👏3🔥3

Signed Sina Doosti

9 Dec 2022, 12:46 UTC≈2,530 views7 reactionsread 6 August 2026
Photo

code.jquery.com hacked :) https://twitter.com/r00t98/status/1601195883152158721 رایتاپ این هک و آسیب پذیری به زودی منتشر میشود... @web_priv8

👍6👏1

Signed Sina Doosti

26 Nov 2022, 21:11 UTC≈2,060 views2 reactionsread 6 August 2026
Photo

https://twitter.com/r00t98/status/1596611819413569544 #CDN #Smuggling #BugBounty @web_priv8

👍1👏1

Signed r00t98

20 Aug 2022, 10:41 UTC≈2,410 viewsread 6 August 2026

https://twitter.com/r00t98/status/1560939871841255424 #Smuggling #BugBounty @web_priv8

Signed r00t98

19 Aug 2022, 21:09 UTC≈2,270 views0 reactionsread 6 August 2026

رسیدن به باگ های RCE و SQLi از طریق کانفیگ اشتباه Reverse Proxy. https://infosecwriteups.com/how-i-made-25000-usd-in-bug-bounties-with-reverse-proxy-d29dba4570d7 #RCE #SQLi #ReverseProxy @web_priv8

Signed r00t98

19 Aug 2022, 21:02 UTC≈1,630 viewsread 6 August 2026

حملاتی که روی Reverse Proxy ها میشه انجام داد. https://www.acunetix.com/blog/articles/a-fresh-look-on-reverse-proxy-related-attacks/ #ReverseProxy @web_priv8

Signed r00t98

Showing the 12 most recent of 20 posts we hold for @web_priv8. 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.

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 30 October 2026 — this entry's latest reading, not the date you are reading this.

“Web_Priv8” (@web_priv8), 712 subscribers as measured 30 October 2026. Telegram Register, tgregister.com/channel/web_priv8.

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.