Telegram RegisterThe public register of Telegram
Telegram profile photo for Codeby

Channel

Codeby

@codeby_sec

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

37,071subscribers

+270 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001049181524
TypeChannel
Username@codeby_sec
DescriptionБлог сообщества Кодебай Чат: @codeby_one Форум: codeby.net Обучение: codeby.academy CTF: hackerlab.pro VK: vk.com/codeby YT: clck.ru/XG99c Сотрудничество: @KinWiz Реклама: @Savchenkova_Valentina
Created11 April 2016 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live9 November 2026
Measurements held61
Confirmed unchanged1 time, most recently 9 November 2026
On Telegramt.me/codeby_sec

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

36,78337,15136,96737,0716 August 20269 November 2026
61 measurements spanning 95 days, net +270. 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 36,728–37,206 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 61
Measured (UTC)SubscribersChange
9 Nov 2026, 17:4837,071+16
8 Nov 2026, 09:4937,055-3
7 Nov 2026, 06:2737,058+1
6 Nov 2026, 02:4837,057+4
4 Nov 2026, 23:3637,053+10
4 Nov 2026, 00:1837,043+9
3 Nov 2026, 01:4137,034+7
1 Nov 2026, 02:0037,027-41
30 Oct 2026, 23:4637,068-21
29 Oct 2026, 22:1637,089-38
28 Oct 2026, 22:2137,127-24
27 Oct 2026, 21:3037,151+21
26 Oct 2026, 19:4837,130-5
25 Oct 2026, 17:3837,135+4
24 Oct 2026, 21:0537,131+1
23 Oct 2026, 19:5737,130+2
22 Oct 2026, 21:5537,128-13
21 Oct 2026, 17:4537,141-4
20 Oct 2026, 15:4637,145+5
19 Oct 2026, 14:4637,140first reading

Engagement

233 posts held, back to 29 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 189 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
6.74%
avg views ÷ 37,071 subscribers
Avg views / post
2,500
64 posts measured
Reaction rate
0.611%
reactions ÷ views · ER floor
Posts in window
70
of 233 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
WindowRolling 30 days · latest post in window 10 November 2026
Posts held233 (29 July 2026 – 10 November 2026)
Views total159,840
Reactions total977
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Nov 2026, 18:10 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
≈2,580
Videos
≈110
Links
≈8,340

Lifetime counters from Telegram’s own channel header, read 10 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
1m 05s
Average length
9s

Measured directly from 7 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

3,227 reactions across 211 posts, in 38 distinct kinds. The most used accounts for 33.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1,06433.0%
👍91728.4%
🔥82925.7%
😁1675.18%
👎531.64%
🤬341.05%
👀200.62%
🗿200.62%
⚡170.527%
❤‍🔥80.248%
😭70.217%
🤔70.217%
🍌60.186%
💯60.186%
😢60.186%
🎉50.155%
👏50.155%
👾50.155%
😨50.155%
🆒40.124%
18 further kinds421.30%

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 211 of the 233 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 3,227 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 233 most recent posts we hold, published 29 July 2026 to 10 November 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
2
across the posts below
Posts paid on
2
of 213 we hold a reading for · 0.9%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @codeby_sec. 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 233 most recent posts we hold for this entry, published 29 July 2026 to 10 November 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.

Advertising

Ad load
9.44%
22 of 233 posts carry an ad marker
Regulatory tokens
22
posts carrying an erid · 22 distinct tokens
Median views · ads
2,770
over 22 measured posts
Median views · rest
2,580
over 191 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. They are printed side by side with the count behind each rather than as a ratio: an ad and an ordinary post are not otherwise matched — for topic, for length, for hour of day — so the gap between them is a description of two groups and not the effect of one being an ad.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2VtzqujwTHF17 October 20267 October 2026
2VtzqufPmFy110 August 202610 August 2026
2Vtzqug24nr15 November 20265 November 2026
2VtzqupRrDS123 September 202623 September 2026
2Vtzqv2Wu9C15 August 20265 August 2026
2Vtzqv8amzK111 August 202611 August 2026
2VtzqvJkKR7115 October 202615 October 2026
2VtzqvTKRcA19 November 20269 November 2026
2VtzqvfS36K17 August 20267 August 2026
2VtzqvhEyiM127 October 202627 October 2026
2VtzqvkLC7v16 September 20266 September 2026
2VtzqvoHDWc114 September 202614 September 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it. 10 further tokens are held for this entry and not listed here.

Measured over the 233 most recent posts we hold, published 29 July 2026 to 10 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

Telegram’s own ‘edited’ marker: 10 of 70 posts held from the last 30 days (14.3%) 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).

10 Nov 2026, 15:07 UTC≈1,030 views10 reactionsread 10 November 2026
Photo

❗️ИИ помог Linux! 🔎CVE-2026-98432: как ИИ нашёл уязвимость в ядре Linux и почему дистрибутивы спорят об опасности 🧾В конце октября 2026 года в центре внимания безопасности оказалась уязвимость в TCP-стеке ядра Linux — CVE-2026-98432. 🧠Её особенность в том, что баг обнаружила и превратила в рабочий эксплойт ИИ-модель Claude из Anthropic. Проблема затрагивает множество дистрибутивов — Ubuntu, Red Hat Enterprise Linu…

🔥5👍3❤2

10 Nov 2026, 11:50 UTC≈1,320 views11 reactionsread 10 November 2026
Photo

⭐ Что ждет полуфиналистов Студенческого чемпионата «Кибербезопасность в финансах»Молодежной программы 365? Лучшие команды киберчемпионата отправятся в Екатеринбург и примут участие в очном этапе. Он пройдет в рамках Уральского форума «Кибербезопасность в финансах» – крупнейшего отраслевого мероприятия Банка России. В Екатеринбурге участников ждут: *️⃣ Полуфинал на киберполигоне — защита виртуальной цифровой инфраст…

🔥7❤2👍2

10 Nov 2026, 08:11 UTC≈1,490 views15 reactionsread 10 November 2026
Photo

11.11 в Codeby: скидка 11% на все курсы Академии Спешим сообщить: уже завтра при оплате любого курса Codeby Academy будет действовать скидка 11%. Практические курсы по пентесту, SOC, реверс-инжинирингу, OSINT, Kubernetes и другим направлениям информационной безопасности. На курсах вас ждут: 👌Онлайн-формат, гибкий график и поддержка кураторов. 👌Обучение с использованием актуальных инструментов на реальных кейсах. 👌…

❤4👍4🔥4🍌1🗿1😁1

9 Nov 2026, 16:02 UTC≈1,800 views12 reactionsread 10 November 2026
Photo

❗️Новости недели (02 ноября – 08 ноября) Росстат под атакой, Beget лежит, Sega без сети, а рынок теряет триллионы - разберем события недели! 1️⃣Росстат атаковали, но данные отрицают С 29 октября по 1 ноября инфраструктура Росстата пережила серию атак. Сайт ведомства какое-то время выглядел иначе (на нём появилась символика хакерских группировок). ▶️ответственность взяли на себя «Киберпартизаны BY» и Silent Crow ▶️он…

❤5🔥4👍3

9 Nov 2026, 09:00 UTC≈1,840 views11 reactionsread 10 November 2026
Advertisementerid 2VtzqvTKRcAPhoto

Релиз прошёл. Через неделю в API находят SQLi. AppSec переносит безопасность туда, где уязвимость ещё можно исправить в процессе разработки. AppSec-инженер в Codeby Academy — 7 месяцев практики на реальных приложениях и инструментах, которые используют в продакшене. Внутри курса: ⏺️ разбор уязвимостей OWASP на реальных приложениях ⏺️ SAST/DAST инструменты, которые используют в боевых командах ⏺️ Threat Modeling и S…

👍4🔥4❤3

9 Nov 2026, 07:04 UTC≈2,070 views16 reactionsread 10 November 2026
Photo

Хакеры прячут Linux Backdoor в Веб-панели управления сервером, чтобы запускать команды без логирования Backdoor был найден прятаным на веб-сервере который держал CWP (Control Web Panel) - бесплатная панель для управления Linux хостами сервера - сказали исследователи из QiAnXin's XLab. Веб серверы которые имели backdoor запускали команды которые атакующие отправляли через веб-запросы, и эти запросы никогда не попада…

👍6❤5🔥4😁1

8 Nov 2026, 07:49 UTC≈2,760 views15 reactionsread 10 November 2026
Photo

🔥 ИИ уже в SOC: кого он заменит первым — L1 или всех сразу? Один участник форума спросил прямо: что ИИ забирает на себя в SOC, как быстро идёт переход и какие навыки нужны, чтобы не остаться за бортом? Ответов пока ноль, и нам нужны вы. Работаете в SOC? Расскажите, что у вас делает ИИ, а что по-прежнему приходится делать руками. Только входите в профессию? Напишите, чему стоит учиться уже сейчас. Ваш опыт может ок…

👍7❤4🔥3😐1

7 Nov 2026, 09:26 UTC≈2,290 views13 reactionsread 10 November 2026
Forwarded from @hacker_lab_proPhoto

🚩 Новые задания на платформе HackerLab! 🌍 Категория Веб — Слепой оттиск Приятного хакинга!

❤5👍4🔥4

6 Nov 2026, 15:55 UTC≈2,630 views7 reactionsread 10 November 2026

Posted without readable text

👍3❤2🔥2

6 Nov 2026, 10:02 UTC≈2,590 views17 reactionsread 10 November 2026
Photo

⚡️ Регистрация на Студенческий чемпионат «Кибербезопасность в финансах» Молодежной программы 365 продолжается! К участию в соревновании приглашаются команды из 4–5 человек: ➖ все участники команды должны быть студентами вузов в возрасте от 18 до 25 лет; ➖ минимум 2 человека должны учиться по направлениям информационной безопасности и (или) информационных технологий. Рассказываем, как собрать и зарегистрировать кома…

👍6❤5🔥5🤬1

6 Nov 2026, 07:03 UTC≈2,450 views11 reactionsread 10 November 2026
Photo

VulnRisk 💻 VulnRisk — это открытая платформа для оценки рисков уязвимостей. Её главная идея - учитывать контекст: критичность актива, вероятность эксплуатации и другие факторы. 🔎 VulnRisk помогает процессу vulnerability management: CVSS сам по себе не показывает, насколько уязвимость опасна для конкретной организации. Платформа добавляет контекстную оценку риска и прозрачную методику расчёта, где видно, почему нахо…

🔥5❤3👍3

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

@codeby_sec edited 2 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
20 October 2026
Most recent edit
6 November 2026

Posts recorded as deleted after publishing

We recorded 12 posts on @codeby_sec 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
9 August 2026
Most recent seen missing
4 November 2026
Median time before seen missing
3 days
Seen missing in the last 30 days
2

Polls

The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

7 Aug 2026, 14:30 UTCAnonymous Quiz515 voters

Как называется такая категория уязвимостей?

  1. DOM Clobbering30%
  2. Prototype Pollution41%
  3. Type Confusion16%
  4. Deserialization13%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

31 Jul 2026, 16:03 UTCAnonymous Quiz600 voters

В каком случае риск SQL-инъекции сохраняется?

  1. Использование Prepared Statements10%
  2. Динамическое формирование имен таблиц или столбцов из пользовательского ввода61%
  3. Применение HTTPS22%
  4. Использование ORM8%

Shares as published, totalling 101%. 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 233 most recent posts we hold, published 29 July 2026 to 10 November 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.

Forward network

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 1 registered channel — 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.

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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

Похек
@poxek · 17,302
#1
SecurityLab.ru
@SecLabNews · 86,532
#2
Social Engineering
@Social_engineering · 124,696
#3
SecAtor
@true_secator · 42,194
#4
OFFZONE
@offzone_moscow · 7,536
#5
infosec
@it_secur · 63,401
#6
Life-Hack - Хакер
@haccking · 63,021
#7
Хакер — Xakep.RU
@xakep_ru · 40,313
#8
Пост Лукацкого
@alukatsky · 38,431
#9
YAH
@YAH_Channel · 7,632
#10
Cybred
@cybred · 11,415
#11
S.E.Reborn
@S_E_Reborn · 22,459
#12
APT
@APT_Notes · 17,360
#13
BI.ZONE
@bizone_channel · 11,609
#14
Positive Technologies
@Positive_Technologies · 29,449
#15
Russian OSINT
@Russian_OSINT · 48,508
#16
Hacker News
@HNews · 7,260
#17
BI.ZONE Bug Bounty
@bizone_bugbounty · 6,732
#18
Inside
@in51d3 · 7,962
#19
SHADOW:Group
@shadow_group_tg · 11,456
#20
S.E.Book
@S_E_Book · 23,090
#21
k8s (in)security
@k8security · 13,332
#22
Управление Уязвимостями и прочее
@avleonovrus · 12,628
#23
SecuriXy.kz
@securixy_kz · 10,381
#24
infosecurity
@tg_infosec · 26,847
#25
Hacker Lab
@hacker_lab_pro · 3,865
#26
CyberCamp
@CYBERCAMP_ONLINE · 8,742
#27
Open Source
@open_source_friend · 52,669
#28
Репорты простым языком
@critical_bug · 3,340
#29
PurpleBear
@purple_medved · 4,667
#30
Чёрный Треугольник
@black_triangle_tg · 63,957
#31
Investigation & Forensic TOOLS
@forensictools · 22,609
#32
PWN AI
@pwnai · 7,655
#33
ESCalator
@ptescalator · 8,385
#34
Blue (h/c)at Café
@bh_cat · 4,007
#35
Что-то на пентестерском
@pntests · 2,778
#36
Just Security
@justsecurity · 3,710
#37
T.Hunter
@tomhunter · 14,174
#38
AM Live
@anti_malware · 13,159
#39
no system is safe // cybersec
@nsis_cybersec · 21,166
#40
Positive Events
@PositiveEvents · 6,116
#41
Архив Безопасника
@secure_archive · 10,964
#42
Новости SPbCTF
@spbctfnews · 3,162
#43
RED Security
@redsecurity_co · 5,199
#44
Пакет Безопасности
@package_security · 33,728
#45
НеКасперский
@NeKaspersky · 16,203
#46
Борьба с киберпреступностью | F6
@f6_cybersecurity · 22,363
#47
Белый хакер
@bezopasno_soft · 29,601
#48
Kali Linux
@linuxkalii · 55,842
#49
Райтапы по CTF{2026}
@writeup_ctf · 4,644
#50
BugXplorer
@bugxplorer · 10,043
#51
КИБЕР МЕДИА
@secmedia · 6,091
#52
AlexRedSec
@alexredsec · 4,034
#53
Security Wine (бывший - DevSecOps Wine)
@sec_devops · 7,051
#54
Positive Development Community
@POSIdev · 3,243
#55
IT и безопасность
@tg_security · 26,812
#56
Омский багхантер
@bughunter_omsk · 1,583
#57
true_security
@true_sec · 2,454
#58
Записки Безопасника
@infosec_globe · 17,894
#59
Утечки информации
@dataleak · 117,768
#60
Багхантер 2.0
@bughunter_circuit · 18,747
#61
RuSecJobs Channel
@RuSecJobs · 11,614
#62
Вакансии в ИБ | infosec
@infosec_work · 16,337
#63
Information Security Memes
@infosecmemes · 9,619
#64
PRO:PENTEST
@pro_pentest · 10,223
#65
Эксплойт
@exploitex · 2,022,997
#66
Bounty On Coffee
@BountyOnCoffee · 4,821
#67
PT SWARM
@ptswarm · 7,613
#68
Mr. Robot
@elliot_cybersec · 38,923
#69
Offensive Xwitter
@OffensiveTwitter · 21,323
#70
🕷 BugBountyRu
@BugBountyRu · 3,101
#71
Яндекс | Охота за ошибками
@yandex_bugbounty · 2,664
#72
Информация опасносте
@alexmakus · 18,748
#73
DevSecOps Talks
@devsecops_weekly · 8,085
#74
r0 Crew (Channel)
@R0_Crew · 9,001
#75
vx-underground
@vxunderground · 52,873
#76

Read from Telegram’s recommendation API, most recently 1 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

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.

Life-Hack - Хакер
@haccking · 63,021
Telegram ranks this channel #3 of 85 here — alongside 84 others — read 21 August 2026
IT и безопасность
@tg_security · 26,812
Telegram ranks this channel #4 of 91 here — alongside 90 others — read 12 September 2026
S.E.Book
@S_E_Book · 23,090
Telegram ranks this channel #5 of 64 here — alongside 63 others — read 19 September 2026
Хакер — Xakep.RU
@xakep_ru · 40,313
Telegram ranks this channel #6 of 83 here — alongside 82 others — read 30 August 2026
TechNews
@techlucker · 42,607
Telegram ranks this channel #6 of 79 here — alongside 78 others — read 28 August 2026
S.E.Reborn
@S_E_Reborn · 22,459
Telegram ranks this channel #8 of 66 here — alongside 65 others — read 20 September 2026
Open Source
@open_source_friend · 52,669
Telegram ranks this channel #8 of 87 here — alongside 86 others — read 24 August 2026
Этичный Хакер
@hack_less · 243,065
Telegram ranks this channel #8 of 81 here — alongside 80 others — read 12 August 2026
infosec
@it_secur · 63,401
Telegram ranks this channel #9 of 81 here — alongside 80 others — read 22 August 2026
SecurityLab.ru
@SecLabNews · 86,532
Telegram ranks this channel #9 of 90 here — alongside 89 others — read 18 August 2026
CMD | IT
@cmd_it · 24,075
Telegram ranks this channel #10 of 82 here — alongside 81 others — read 16 September 2026
SecAtor
@true_secator · 42,194
Telegram ranks this channel #11 of 78 here — alongside 77 others — read 29 August 2026
infosecurity
@tg_infosec · 26,847
Telegram ranks this channel #12 of 74 here — alongside 73 others — read 11 September 2026
Russian OSINT
@Russian_OSINT · 48,508
Telegram ranks this channel #12 of 82 here — alongside 81 others — read 26 August 2026
Social Engineering
@Social_engineering · 124,696
Telegram ranks this channel #12 of 82 here — alongside 81 others — read 13 August 2026
Лаборатория хакера
@lab_hack · 25,423
Telegram ranks this channel #13 of 71 here — alongside 70 others — read 14 September 2026
Investigation & Forensic TOOLS
@forensictools · 22,609
Telegram ranks this channel #14 of 74 here — alongside 73 others — read 20 September 2026
Интернет-Розыск
@irozysk · 45,728
Telegram ranks this channel #14 of 79 here — alongside 78 others — read 27 August 2026
PulSe
@Pulsechanel · 20,004
Telegram ranks this channel #15 of 69 here — alongside 68 others — read 29 September 2026
Борьба с киберпреступностью | F6
@f6_cybersecurity · 22,363
Telegram ranks this channel #15 of 85 here — alongside 84 others — read 21 September 2026
Task No Face
@TaskNoFace · 28,996
Telegram ranks this channel #15 of 78 here — alongside 77 others — read 8 September 2026
Kali Linux
@linuxkalii · 55,842
Telegram ranks this channel #17 of 89 here — alongside 88 others — read 23 August 2026
Бункер Хакера
@book_academ · 21,293
Telegram ranks this channel #18 of 72 here — alongside 71 others — read 23 September 2026
no system is safe // cybersec
@nsis_cybersec · 21,166
Telegram ranks this channel #19 of 71 here — alongside 70 others — read 23 September 2026

This channel appears in 61 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 9 November 2026 — this entry's latest reading, not the date you are reading this.

“Codeby” (@codeby_sec), 37,071 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/codeby_sec.

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.