Новости платформы BI.ZONE Bug Bounty. Вы нам баги — мы вам деньги.
https://bugbounty.bi.zone
Чат сообщества багхантеров: @bizonebb
По всем вопросам: @BizoneBugBountySupport
Все согласия получены. Условий субъектами не установлено
Created
Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
Technology — 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 86% 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
25 measurements spanning 98 days, net +258. 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,426–6,775 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 25
Measured (UTC)
Subscribers
Change
12 Nov 2026, 12:01
6,735
+3
8 Nov 2026, 02:59
6,732
+1
4 Nov 2026, 14:30
6,731
+7
1 Nov 2026, 18:19
6,724
+2
29 Oct 2026, 07:51
6,722
-3
25 Oct 2026, 23:15
6,725
+8
22 Oct 2026, 18:59
6,717
+9
19 Oct 2026, 03:57
6,708
+12
15 Oct 2026, 20:35
6,696
+1
12 Oct 2026, 20:46
6,695
+20
6 Oct 2026, 01:56
6,675
+55
28 Sept 2026, 10:37
6,620
+16
18 Sept 2026, 16:20
6,604
+8
14 Sept 2026, 03:39
6,596
+4
10 Sept 2026, 05:00
6,592
-6
4 Sept 2026, 21:22
6,598
+2
1 Sept 2026, 08:45
6,596
-3
25 Aug 2026, 20:55
6,599
-11
22 Aug 2026, 17:56
6,610
+144
19 Aug 2026, 08:39
6,466
first reading
Engagement
28 posts held, back to 18 June 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 24 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
24.2%
avg views ÷ 6,735 subscribers
Avg views / post
1,630
1 post measured
Reaction rate
1.29%
reactions ÷ views · ER floor
Posts in window
1
of 28 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
What these figures were computed from
Window
Rolling 30 days · latest post in window 21 October 2026
Posts held
28 (18 June 2026 – 21 October 2026)
Views total
1,630
Reactions total
21
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
16 Nov 2026, 15:42 UTC
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
Photos
527
Videos
31
Links
341
Lifetime counters from Telegram’s own channel header, read 16 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.
Video runtime
10m 48s
Average length
2m 42s
Measured directly from 4 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
483 reactions across 24 posts, in 6 distinct kinds. The most used accounts for 39.3% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
190
39.3%
custom 5361619121131757412
136
28.2%
custom 5276225181193355960
122
25.3%
custom 5361959870952120096
13
2.69%
custom 5363988890812161724
11
2.28%
👨💻
11
2.28%
Custom emoji. 4 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 24 of the 28 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 483 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 28 most recent posts we hold, published 18 June 2026 to 21 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.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 1 post held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
🪲 Пора собираться в новую экспедицию! Анонсируем BUGS ZONE 9.0
🔹Старт хантинга — 23 ноября.
🔹Церемония и афтепати — 11 декабря в Москве.
Как всегда, готовим много интересного: закрытые скоупы, активности, доклады, мерч... И несколько вещей, о которых пока рано рассказывать.
Но одну интригу уже можем подкинуть.
В этот раз к нам присоединится одно хорошо знакомое комьюнити.
Кто именно? Пока оставим в секрете. Но е…
🪲 «Совкомбанк» вышел в паблик
Их программа долго была в приватке, а теперь доступна всем.
В скоупе — больше 40 ресурсов. Сможете исследовать безопасность веб-сервисов, мобильных приложений и других цифровых источников компании.
🔹Максимальное вознаграждение — 120 тысяч рублей.
Вперед, на охоту ;)
🪲 Итоги III квартала
Пришло время назвать тех, кто отличился в III квартале. Победители получают бонус 5% к каждой выплате на следующие 3 месяца.
King of reports
1️⃣rolegiv
2️⃣mykl
3️⃣thxStuck
Top moneymaker
1️⃣cutoffurmind
2️⃣mykl
3️⃣Beltas
Jack of all trades
1️⃣rolegiv
2️⃣mykl
3️⃣r0hack
Поздравляем лидеров квартала! И спасибо всем, кто исследует программы, приносит качественные находки и помогает делать продук…
🪲 Познакомимся?
Запустили анонимный опрос на 10 минут про багхантинг, ваши интересы и привычки.
Расскажите, что вам важно и интересно, — так мы сможем точнее подбирать темы и активности для вас.
Персональные данные не собираем, правильных ответов нет. Помогите нам узнать портрет комьюнити.
💙 Пройти опрос
🥂 Лучше пятницы может быть только пятница + дайджест новостей нашего комьюнити
Встречайте третий выпуск нашего нового и уже полюбившегося формата! Предыдущий можно посмотреть вот тут.
Не стесняйтесь ставить реакты, и приятного просмотра :)
🪲 С 1 октября выплаты через «Консоль» будут проходить по-новому
«Консоль» обновляет сервис, поэтому меняется и привычный путь до выплаты. Чтобы все прошло без задержек и неожиданных сюрпризов, нужно сделать несколько вещей.
Что меняется:
🔹Новый адрес «Консоли»
Вместо app.konsol.pro теперь используем app.konsol.ru.
🔹Новое приложение «Консоль.HRM»
Его нужно скачать всем, кто получает выплаты через «Консоль»: самозан…
🔥6,48 млн причин искать баги
Ровно столько получил наш багхантер cutoffurmind за один отчет на нашей платформе.
Это самая большая выплата на российских багбаунти-площадках!
cutoffurmind, поздравляем. Это сильно 💪🏻
🪲 VolgaCTF: флаги найдены, Самара пройдена
Немного выдохнули после поездки и наконец можем сказать: VolgaCTF, было классно.
За эти дни успели посмотреть, как участники упорно искали флаги, пообщаться с коллегами из индустрии, послушать разговоры про ИИ и образование и, конечно, выступить самим.
💙 До следующего раза!
🐞 VolgaCTF, второй день, полет нормальный
Пока участники VolgaCTF борются за победу, представители вузов, ИБ-компаний и региональных ведомств дискутируют за другим столом.
Обсуждают ИИ в высшем образовании: изменения в учебном процессе, потенциальные риски и как защитить данные, модели и инфраструктуру от вполне реальных угроз.
Showing the 12 most recent of 28 posts we hold for @bizone_bugbounty. 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 recorded as deleted after publishing
We recorded 2 posts on @bizone_bugbounty as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
First seen missing
7 August 2026
Most recent seen missing
7 August 2026
Median time before seen missing
8 days
Seen missing in the last 30 days
0
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Named by 7 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
Codeby @codeby_sec · 37,111 Telegram ranks this channel #18 of 76 here — alongside 75 others — read 1 September 2026
Positive Technologies @Positive_Technologies · 29,648 Telegram ranks this channel #26 of 87 here — alongside 86 others — read 9 September 2026
Positive Hack Days Media @positivehackmedia · 30,000 Telegram ranks this channel #26 of 88 here — alongside 87 others — read 6 September 2026
Life-Hack - Хакер @haccking · 62,998 Telegram ranks this channel #34 of 85 here — alongside 84 others — read 21 August 2026
The Bug Bounty Hunter @thebugbountyhunter · 52,367 Telegram ranks this channel #41 of 60 here — alongside 59 others — read 25 August 2026
Offensive Xwitter @OffensiveTwitter · 21,343 Telegram ranks this channel #48 of 53 here — alongside 52 others — read 25 September 2026
OSINT mindset @osint_mindset · 65,013 Telegram ranks this channel #52 of 83 here — alongside 82 others — read 21 August 2026
Хакер — Xakep.RU @xakep_ru · 40,322 Telegram ranks this channel #55 of 83 here — alongside 82 others — read 30 August 2026
Борьба с киберпреступностью | F6 @f6_cybersecurity · 22,362 Telegram ranks this channel #60 of 85 here — alongside 84 others — read 21 September 2026
Волгоград | События | Подслушано @Volgograd_podslushal · 35,766 Telegram ranks this channel #64 of 73 here — alongside 72 others — read 2 September 2026
Mr. Robot @elliot_cybersec · 38,866 Telegram ranks this channel #66 of 70 here — alongside 69 others — read 31 August 2026
SecAtor @true_secator · 42,222 Telegram ranks this channel #69 of 78 here — alongside 77 others — read 29 August 2026
Пакет Безопасности @package_security · 34,225 Telegram ranks this channel #71 of 82 here — alongside 81 others — read 4 September 2026
Этичный Хакер @hack_less · 242,543 Telegram ranks this channel #76 of 81 here — alongside 80 others — read 12 August 2026
SecurityLab.ru @SecLabNews · 86,623 Telegram ranks this channel #79 of 90 here — alongside 89 others — read 18 August 2026
Kaspersky @kasperskylab_ru · 29,326 Telegram ranks this channel #82 of 96 here — alongside 95 others — read 9 September 2026
Пост Лукацкого @alukatsky · 38,486 Telegram ranks this channel #84 of 89 here — alongside 88 others — read 31 August 2026
This channel appears in 17 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 12 November 2026 — this
entry's latest reading, not the date you are reading this.
“BI.ZONE Bug Bounty” (@bizone_bugbounty), 6,735 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/bizone_bugbounty.
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.