Telegram RegisterThe public register of Telegram
Telegram profile photo for Bug Bounty Diary

Channel

Bug Bounty Diary

@bugbounty_diary

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry

7,406subscribers

+518 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001394394025
TypeChannel
Username@bugbounty_diary
DescriptionA diary documenting the journey of finding bugs, with daily notes and useful tricks. Follow for real experiences, discoveries, and practical tips in bug bounty hunting. Group: @BugBounty_Forum
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live13 November 2026
Measurements held24
Confirmed unchanged1 time, most recently 13 November 2026
On Telegramt.me/bugbounty_diary

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 76% 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

6,8847,4067,1458 August 2026 — 6,888 subscribers9 August 2026 — 6,887 subscribers11 August 2026 — 6,884 subscribers15 August 2026 — 6,946 subscribers18 August 2026 — 6,954 subscribers21 August 2026 — 6,985 subscribers24 August 2026 — 7,005 subscribers27 August 2026 — 7,023 subscribers30 August 2026 — 7,042 subscribers3 September 2026 — 7,093 subscribers7 September 2026 — 7,119 subscribers11 September 2026 — 7,141 subscribers15 September 2026 — 7,177 subscribers28 September 2026 — 7,275 subscribers5 October 2026 — 7,308 subscribers12 October 2026 — 7,318 subscribers18 October 2026 — 7,316 subscribers21 October 2026 — 7,331 subscribers24 October 2026 — 7,344 subscribers27 October 2026 — 7,349 subscribers30 October 2026 — 7,372 subscribers2 November 2026 — 7,395 subscribers8 November 2026 — 7,404 subscribers13 November 2026 — 7,406 subscribers8 August 202613 November 2026
24 measurements spanning 97 days, net +518. 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 6,806–7,484 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 24
Measured (UTC)SubscribersChange
13 Nov 2026, 03:007,406+2
8 Nov 2026, 11:117,404+9
2 Nov 2026, 17:547,395+23
30 Oct 2026, 08:597,372+23
27 Oct 2026, 11:597,349+5
24 Oct 2026, 15:597,344+13
21 Oct 2026, 11:017,331+15
18 Oct 2026, 13:567,316-2
12 Oct 2026, 15:297,318+10
5 Oct 2026, 13:217,308+33
28 Sept 2026, 02:197,275+98
15 Sept 2026, 20:207,177+36
11 Sept 2026, 20:377,141+22
7 Sept 2026, 15:367,119+26
3 Sept 2026, 00:537,093+51
30 Aug 2026, 22:337,042+19
27 Aug 2026, 18:467,023+18
24 Aug 2026, 23:227,005+20
21 Aug 2026, 08:476,985+31
18 Aug 2026, 18:286,954first reading

Engagement

27 posts held, back to 22 December 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 34 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 27 posts for this entry, the most recent from 5 October 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
30
Links
45

Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

578 reactions across 26 posts, in 8 distinct kinds. The most used accounts for 44.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤25844.6%
🔥18031.1%
❤‍🔥9316.1%
👍366.23%
💋71.21%
🤝20.346%
✍10.173%
😍10.173%

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 26 of the 27 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 578 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 27 most recent posts we hold, published 22 December 2025 to 5 October 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.

Telegram Stars

Stars received
3
across the posts below
Posts paid on
3
of 26 we hold a reading for · 12%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @bugbounty_diary. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 27 most recent posts we hold for this entry, published 22 December 2025 to 5 October 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

5 Oct 2026, 12:21 UTC≈2,470 views12 reactionsread 17 November 2026
Photo

✎ Implementing Network Services - Module 6 Chapter 6 - provides a brief review of the most important network services, including DNS, DHCP, and other core services. -- Implementing Network Services -- • Blog: Network Basics - Module 6 #bugbounty #network © T.me/BugBounty_Diary

❤5❤‍🔥4🔥2💋1

16 Sept 2026, 18:14 UTC≈3,670 views17 reactionsread 17 November 2026

✎ IDN Homograph Attacks: From Phishing to Account-Collision Bugs Most people know the classic IDN story: register a domain with lookalike Unicode characters ( á U+00E1 vs a U+0061 ), get it Punycode-encoded as xn--..., and trick a browser address bar into rendering something that looks like apple.com. That's old news from 2005/2017 and browsers mostly catch it now. ● The Core Bug Apps often accept Unicode in email…

❤11❤‍🔥5💋1

7 Sept 2026, 18:10 UTC≈3,780 views15 reactionsread 17 November 2026
Photo

✎ Network Basics - Module 5 Chapter 5 - Part 2 is live now — hope you find it useful! -- Configuring Routing and Advanced Switching — Part 2 -- If you're new to networking, this chapter might feel a bit overwhelming at first. Don't worry I’ve tried to include quick reviews throughout the article to help reinforce the key concepts step by step. The quick review sections can also help you identify topics you're str…

🔥9❤3❤‍🔥1💋1😍1

30 Aug 2026, 06:03 UTC≈3,990 views26 reactionsread 17 November 2026

Successfully identified an Account Takeover (ATO) vulnerability in a public program. The attack chain started with a flaw in the interaction between the web application and its WebSocket layer, which eventually led me down a rabbit hole into the Windows desktop client. I ended up reverse engineering its .dll files to understand the authentication flow and how JWTs were generated and signed. Definitely one of those…

🔥19❤6💋1

23 Aug 2026, 12:27 UTC≈4,930 views22 reactionsread 17 November 2026
Photo

✎ Unhar - Extract, Unminify, Beautify Javascript files from .Har file In the previous post, I explained my approach to capturing and downloading a website’s JavaScript resources into a .HAR file for further local analysis. Now, let’s take it a step further with unhar and process that HAR files. unhar turns a raw .HAR file into a structured set of web assets for local analysis. It extracts unique JavaScript and HTML…

🔥12❤6❤‍🔥2👍1💋1

23 Aug 2026, 11:50 UTC≈3,750 views16 reactionsread 17 November 2026
Photo

✎ Extract & Download All JavaScript Files for Recon For modern web apps, scraping <script> tags or relying on Burp's Site Map often isn't enough. Why? Because applications may dynamically load JavaScript from CDNs, cross-origin domains, specific routes (Lazy Loading), or after user interactions. My Approach: 1. Open DevTools → Network 2. Enable Preserve log 3. Crawl the target and visit relevant pages/features 4. I…

❤10🔥3❤‍🔥1👍1💋1

9 Aug 2026, 22:04 UTC≈4,390 views20 reactionsread 17 November 2026
Photo

✎ Using LLMs to Unminify JavaScript Most JavaScript minification is lossless. Transformations like true → !0 can be reversed with traditional AST-based tools such as Babel. Variable renaming is different: recovering meaningful names requires understanding the code's intent. This is where LLMs can help. Instead of letting an LLM rewrite the source directly, which can break functionality, we can use it only to sugge…

❤14🔥4❤‍🔥1💋1

16 Jul 2026, 12:59 UTC≈4,920 views15 reactionsread 17 November 2026
Photo

✎ Network Basics - Module 5 Chapter 5 - part1 is live now - hope you find it helpful! -- Configuring Routing and Advance Switching — part 1-- • Blog: Network Basics - Module 5 #bugbounty #network © T.me/BugBounty_Diary

🔥9❤3❤‍🔥1👍1🤝1

Signed Amir

12 Jul 2026, 00:27 UTC≈5,740 views37 reactionsread 17 November 2026

✎ cURL Cheatsheet — The Swiss Knife of HTTP Requests ● Basic Requests 1. GET request curl https://example.com 2. Save response to a file curl -o output.html https://example.com 3. Follow redirects curl -L https://example.com -------‐----------------------------- ● HTTP Methods 1. POST request curl -X POST https://example.com/login 2. Send JSON data curl -X POST https://api.example.com/users \ -H "Content-Typ…

🔥17❤10👍9❤‍🔥1

Signed Amir

1 Jul 2026, 19:20 UTC≈4,210 views19 reactionsread 17 November 2026
Photo

✎ FlareProx - Simple IP Rotation & URL Redirection via Cloudflare Workers FlareProx automatically deploys HTTP proxy endpoints on Cloudflare Workers for easy redirection of all traffic to any URL you specify. It supports all HTTP methods (GET, POST, PUT, DELETE, etc.) and provides IP masking through Cloudflare's global network. (100k requests per day are free.) ● How It Works? FlareProx deploys Cloudflare Workers …

❤‍🔥16❤2✍1

22 Jun 2026, 05:15 UTC≈6,170 views30 reactionsread 17 November 2026
Photo

✎ Hacking Google with A.I. for $500,000 After earning $500,000 in Google bug bounties, BruteCat shared the AI-powered prompts, workflows, and techniques used to analyze Google's massive attack surface, which offers valuable insights for security researchers looking to scale their reconnaissance and vulnerability discovery. I highly recommend you read this writeup because it gives you a good methodology for hacking …

❤‍🔥21👍5❤4

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

Posts edited after publishing

@bugbounty_diary edited 3 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
3 November 2026
Most recent edit
3 November 2026

Mentions

Named by 4 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.

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.

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.

The Bug Bounty Hunter
@thebugbountyhunter · 52,284
Telegram ranks this channel #28 of 60 here — alongside 59 others — read 25 August 2026
Jobscoupe
@jobscoupe · 36,760
Telegram ranks this channel #53 of 67 here — alongside 66 others — read 31 August 2026
کالی لینوکس | Kali linux | ترفند | کامپیوتر | تکنولوژی
@kali_linuxxx · 76,462
Telegram ranks this channel #59 of 60 here — alongside 59 others — read 19 August 2026

This channel appears in 3 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 13 November 2026 — this entry's latest reading, not the date you are reading this.

“Bug Bounty Diary” (@bugbounty_diary), 7,406 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/bugbounty_diary.

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.