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 · Polls · Citations · Telegram's recommendations · Cite this entry

37,041subscribers

+240 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 live26 September 2026
Measurements held33
Confirmed unchanged1 time, most recently 26 September 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 why it has no browse page of its own yet.

Growth

36,78337,04136,9126 August 2026 — 36,801 subscribers7 August 2026 — 36,794 subscribers8 August 2026 — 36,796 subscribers9 August 2026 — 36,783 subscribers11 August 2026 — 36,786 subscribers12 August 2026 — 36,791 subscribers13 August 2026 — 36,792 subscribers15 August 2026 — 36,793 subscribers16 August 2026 — 36,799 subscribers17 August 2026 — 36,796 subscribers18 August 2026 — 36,800 subscribers19 August 2026 — 36,845 subscribers20 August 2026 — 36,835 subscribers21 August 2026 — 36,832 subscribers23 August 2026 — 36,825 subscribers24 August 2026 — 36,837 subscribers26 August 2026 — 36,831 subscribers27 August 2026 — 36,836 subscribers27 August 2026 — 36,839 subscribers28 August 2026 — 36,836 subscribers30 August 2026 — 36,834 subscribers31 August 2026 — 36,837 subscribers1 September 2026 — 36,828 subscribers2 September 2026 — 36,832 subscribers3 September 2026 — 36,829 subscribers5 September 2026 — 36,935 subscribers8 September 2026 — 36,955 subscribers11 September 2026 — 36,956 subscribers13 September 2026 — 36,958 subscribers15 September 2026 — 36,957 subscribers16 September 2026 — 36,967 subscribers19 September 2026 — 36,985 subscribers26 September 2026 — 37,041 subscribers6 August 202626 September 2026
33 measurements spanning 51 days, net +240. 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,744–37,080 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
26 Sept 2026, 05:3937,041+56
19 Sept 2026, 08:5936,985+18
16 Sept 2026, 21:3636,967+10
15 Sept 2026, 01:0236,957-1
13 Sept 2026, 12:1736,958+2
11 Sept 2026, 14:1736,956+1
8 Sept 2026, 19:5636,955+20
5 Sept 2026, 15:0036,935+106
3 Sept 2026, 13:0036,829-3
2 Sept 2026, 03:5436,832+4
1 Sept 2026, 01:0636,828-9
31 Aug 2026, 03:0436,837+3
30 Aug 2026, 00:2536,834-2
28 Aug 2026, 21:2536,836-3
27 Aug 2026, 21:4336,839+3
27 Aug 2026, 00:1836,836+5
26 Aug 2026, 02:4436,831-6
24 Aug 2026, 23:3536,837+12
23 Aug 2026, 08:4536,825-7
21 Aug 2026, 19:1536,832first reading

Engagement

131 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 96 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
6.80%
avg views ÷ 37,041 subscribers
Avg views / post
2,520
61 posts measured
Reaction rate
0.583%
reactions ÷ views · ER floor
Posts in window
67
of 131 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. It is computed over the 60 of 61 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 26 September 2026
Posts held131 (29 July 2026 – 26 September 2026)
Views total153,720
Reactions total886
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken27 Sept 2026, 04:50 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,490
Videos
≈102
Links
≈8,260

Lifetime counters from Telegram’s own channel header, read 27 September 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
24s
Average length
12s

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

1,691 reactions across 117 posts, in 30 distinct kinds. The most used accounts for 32.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤54932.5%
👍44526.3%
🔥43225.5%
😁975.74%
👎331.95%
🤬331.95%
👀181.06%
⚡130.769%
🗿100.591%
❤‍🔥80.473%
🤔60.355%
🆒40.237%
🎉40.237%
👾40.237%
😭40.237%
😱40.237%
🥰40.237%
🍌30.177%
😢30.177%
🤝30.177%
10 further kinds140.828%

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 117 of the 131 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 1,691 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 131 most recent posts we hold, published 29 July 2026 to 26 September 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
1
across the posts below
Posts paid on
1
of 119 we hold a reading for · 0.8%
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 131 most recent posts we hold for this entry, published 29 July 2026 to 26 September 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
10.7%
14 of 131 posts carry an ad marker
Regulatory tokens
14
posts carrying an erid · 14 distinct tokens
Median views · ads
2,670
over 14 measured posts
Median views · rest
2,600
over 105 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
2VtzqufPmFy110 August 202610 August 2026
2VtzqupRrDS123 September 202623 September 2026
2Vtzqv2Wu9C15 August 20265 August 2026
2Vtzqv8amzK111 August 202611 August 2026
2VtzqvfS36K17 August 20267 August 2026
2VtzqvkLC7v16 September 20266 September 2026
2VtzqvoHDWc114 September 202614 September 2026
2VtzqvxzrRR118 August 202618 August 2026
2Vtzqw3YsU8117 September 202617 September 2026
2VtzqwiYmGf124 August 202624 August 2026
2VtzqwzZ83d117 August 202617 August 2026
2Vtzqx6EjdV14 September 20264 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. 2 further tokens are held for this entry and not listed here.

Measured over the 131 most recent posts we hold, published 29 July 2026 to 26 September 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

26 Sept 2026, 09:06 UTC920 views12 reactionsread 27 September 2026
Forwarded from @hacker_lab_proPhoto

🚩 Новые задания на платформе HackerLab! 👩‍💻 Категория Pentest Machines (Active Directory) — Первая работа Приятного хакинга!

❤6👍4🔥2

25 Sept 2026, 07:02 UTC≈1,500 views13 reactionsread 27 September 2026
Photo

Tookie-OSINT: Инструмент разведки по имени пользователя Tookie-OSINT — инструмент с открытым исходным кодом для проведения OSINT-исследований, предназначенный для поиска учетных записей пользователя на различных веб-сайтах и социальных платформах по заданному имени пользователя. Инструмент позиционируется как альтернатива известной утилите Sherlock, обеспечивая автоматизированный поиск цифровых следов в открытых ист…

🔥7❤3👍3

24 Sept 2026, 10:57 UTC≈1,850 viewsread 27 September 2026
Forwarded from @sergey_codebyPhoto

14 резюме за три дня. Где вакансии? За месяц работодатели не разместили на форуме ни одной. А специалисты по ИБ пришли сами: SOC, пентест, AppSec, Red Team, сети. Девять джунов, четыре мидла, один тимлид. Шестеро готовы выйти через неделю или сразу. Если ты нанимаешь безопасников, конкурентов у тебя сейчас нет. Кто разместит вакансию первым, окажется на вкладке один. Посмотреть, кто пришёл →

24 Sept 2026, 09:06 UTC≈1,860 views8 reactionsread 27 September 2026
Forwarded from @sergey_codebyPhoto

UDP-сканирование: ты доверяешь zenmap или запускаешь nmap руками? Дефолтный профиль zenmap не трогает UDP. Коллега советует создать кастомный и не мучиться. Формально он прав: под капотом тот же движок. Но второй коллега запускает nmap -sU из терминала, выставляет --max-retries и --host-timeout вручную. Говорит, что графическая обёртка прячет статусы вроде open|filtered, и на нестабильном канале ты просто не замети…

👍4❤2🔥2

24 Sept 2026, 07:05 UTC≈1,910 views7 reactionsread 27 September 2026
Photo

🌐HExHTTP Инструмент для тестирования HTTP-заголовков и анализа результатов с целью выявления уязвимостей и особенностей HTTP. Инструмент выполняет следующие проверки: ▶️Проверка ответа на ошибку сервера и виртуальных хостов; ▶️Анализ ответа при использовании заголовка Localhost; ▶️Анализ ответов на различные HTTP-методы; ▶️Анализ отладочных и нестандартных заголовков; ▶️Проверка CVE, связанных с HTTP; ▶️Методы DoS …

👍3🔥2❤1😁1

23 Sept 2026, 15:31 UTC≈1,790 views23 reactionsread 27 September 2026
Photo

🌐На мировую арену Lazarus вышли в 2014 году после атаки на Sony Pictures Entertainment. Причиной стал фильм «Интервью» — хакеры уничтожили файлы, украли конфиденциальные данные сотрудников (номера социального страхования, финансовые записи, зарплаты) и выложили в сеть. В утечку попали 4 ещё не выпущенных фильма, включая «Энни». Sony отменила театральный релиз «Интервью» под угрозой атак. Позже фильм вышел онлайн. В 2…

👍11❤6🔥4❤‍🔥1🥰1

23 Sept 2026, 09:44 UTC≈2,020 views16 reactionsread 27 September 2026
Advertisementerid 2VtzqupRrDSPhoto

От теории к реальным задачам: как учат веб-пентесту в Codeby 🚗 Можно знать OWASP Top 10, понимать, как работают SQLi и SSRF, и уметь пользоваться Burp Suite. Но в реальном проекте важно самостоятельно исследовать приложение, находить цепочки уязвимостей и доводить их до эксплуатации. Именно поэтому курс WAPT от Codeby построен вокруг практики: ⏺️поиск и эксплуатация уязвимостей из OWASP Top 10 ⏺️анализ защищённости…

🔥8❤4👍4

23 Sept 2026, 07:04 UTC≈1,970 views8 reactionsread 27 September 2026
Photo

Ваш терминал выполняет чужие команды — и вы этого не видите Представьте: вы читаете логи на скомпрометированном хосте через less, и вдруг заголовок окна tmux меняется, часть вывода пропадает. Запускаете cat -v — а там россыпь ^[[ последовательностей, вшитых в user-agent строки. Кто-то заминировал логи ANSI escape-кодами. Звучит экзотично? На практике это рабочий вектор атаки, который эксплуатируется в дикой природе.…

👍3🔥3❤2

22 Sept 2026, 15:10 UTC≈2,100 views11 reactionsread 27 September 2026

Posted without readable text

❤6🤔3👍1🔥1

22 Sept 2026, 11:20 UTC≈2,370 views13 reactionsread 27 September 2026

https://youtube.com/shorts/B-JlepDLJP0?feature=share Идеальный курс по ИБ MS SQL, ADCS, AD, Exchange Рассказывает Павел, автор курса нашего учебного центра по пентесту AD

🔥6❤4👍2😁1

Showing the 12 most recent of 131 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.

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 131 most recent posts we hold, published 29 July 2026 to 26 September 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 · 16,849
#1
SecurityLab.ru
@SecLabNews · 84,654
#2
Social Engineering
@Social_engineering · 125,008
#3
SecAtor
@true_secator · 41,748
#4
OFFZONE
@offzone_moscow · 7,400
#5
infosec
@it_secur · 61,761
#6
Life-Hack - Хакер
@haccking · 63,203
#7
Хакер — Xakep.RU
@xakep_ru · 39,610
#8
Пост Лукацкого
@alukatsky · 37,862
#9
YAH
@YAH_Channel · 7,569
#10
Cybred
@cybred · 11,118
#11
S.E.Reborn
@S_E_Reborn · 22,374
#12
APT
@APT_Notes · 16,685
#13
BI.ZONE
@bizone_channel · 11,212
#14
Positive Technologies
@Positive_Technologies · 29,062
#15
Russian OSINT
@Russian_OSINT · 47,701
#16
Hacker News
@HNews · 7,293
#17
BI.ZONE Bug Bounty
@bizone_bugbounty · 6,604
#18
Inside
@in51d3 · 7,996
#19
SHADOW:Group
@shadow_group_tg · 11,482
#20
S.E.Book
@S_E_Book · 23,146
#21
k8s (in)security
@k8security · 13,151
#22
Управление Уязвимостями и прочее
@avleonovrus · 12,122
#23
SecuriXy.kz
@securixy_kz · 10,202
#24
infosecurity
@tg_infosec · 26,779
#25
Hacker Lab
@hacker_lab_pro · 3,789
#26
CyberCamp
@CYBERCAMP_ONLINE · 8,666
#27
Open Source
@open_source_friend · 52,304
#28
Репорты простым языком
@critical_bug · 3,347
#29
PurpleBear
@purple_medved · 4,627
#30
Чёрный Треугольник
@black_triangle_tg · 63,850
#31
Investigation & Forensic TOOLS
@forensictools · 22,417
#32
PWN AI
@pwnai · 7,283
#33
ESCalator
@ptescalator · 8,127
#34
Blue (h/c)at Café
@bh_cat · 3,968
#35
Что-то на пентестерском
@pntests · 2,759
#36
Just Security
@justsecurity · 3,630
#37
T.Hunter
@tomhunter · 14,234
#38
AM Live
@anti_malware · 13,154
#39
no system is safe // cybersec
@nsis_cybersec · 21,653
#40
Positive Events
@PositiveEvents · 6,114
#41
Архив Безопасника
@secure_archive · 10,833
#42
Новости SPbCTF
@spbctfnews · 3,107
#43
RED Security
@redsecurity_co · 5,194
#44
Пакет Безопасности
@package_security · 33,011
#45
НеКасперский
@NeKaspersky · 16,061
#46
Борьба с киберпреступностью | F6
@f6_cybersecurity · 22,318
#47
Белый хакер
@bezopasno_soft · 29,706
#48
Kali Linux
@linuxkalii · 55,412
#49
Райтапы по CTF{2026}
@writeup_ctf · 4,485
#50
BugXplorer
@bugxplorer · 9,775
#51
КИБЕР МЕДИА
@secmedia · 5,902
#52
AlexRedSec
@alexredsec · 4,007
#53
Security Wine (бывший - DevSecOps Wine)
@sec_devops · 7,110
#54
Positive Development Community
@POSIdev · 3,186
#55
IT и безопасность
@tg_security · 26,560
#56
Омский багхантер
@bughunter_omsk · 1,580
#57
true_security
@true_sec · 2,441
#58
Записки Безопасника
@infosec_globe · 18,120
#59
Утечки информации
@dataleak · 119,401
#60
Багхантер
@bughunter_circuit · 3,514
#61
RuSecJobs Channel
@RuSecJobs · 11,322
#62
Вакансии в ИБ | infosec
@infosec_work · 15,755
#63
Information Security Memes
@infosecmemes · 9,677
#64
PRO:PENTEST
@pro_pentest · 10,096
#65
Эксплойт
@exploitex · 2,048,279
#66
Bounty On Coffee
@BountyOnCoffee · 4,763
#67
PT SWARM
@ptswarm · 7,502
#68
Mr. Robot
@elliot_cybersec · 38,917
#69
Offensive Xwitter
@OffensiveTwitter · 21,041
#70
🕷 BugBountyRu
@BugBountyRu · 2,990
#71
Яндекс | Охота за ошибками
@yandex_bugbounty · 2,446
#72
Информация опасносте
@alexmakus · 18,782
#73
DevSecOps Talks
@devsecops_weekly · 8,025
#74
r0 Crew (Channel)
@R0_Crew · 8,962
#75
vx-underground
@vxunderground · 52,032
#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,203
Telegram ranks this channel #3 of 85 here — alongside 84 others — read 21 August 2026
IT и безопасность
@tg_security · 26,560
Telegram ranks this channel #4 of 91 here — alongside 90 others — read 12 September 2026
S.E.Book
@S_E_Book · 23,146
Telegram ranks this channel #5 of 64 here — alongside 63 others — read 19 September 2026
Хакер — Xakep.RU
@xakep_ru · 39,610
Telegram ranks this channel #6 of 83 here — alongside 82 others — read 30 August 2026
TechNews
@techlucker · 43,532
Telegram ranks this channel #6 of 79 here — alongside 78 others — read 28 August 2026
S.E.Reborn
@S_E_Reborn · 22,374
Telegram ranks this channel #8 of 66 here — alongside 65 others — read 20 September 2026
Open Source
@open_source_friend · 52,304
Telegram ranks this channel #8 of 87 here — alongside 86 others — read 24 August 2026
Этичный Хакер
@hack_less · 229,400
Telegram ranks this channel #8 of 81 here — alongside 80 others — read 12 August 2026
infosec
@it_secur · 61,761
Telegram ranks this channel #9 of 81 here — alongside 80 others — read 22 August 2026
SecurityLab.ru
@SecLabNews · 84,654
Telegram ranks this channel #9 of 90 here — alongside 89 others — read 18 August 2026
CMD | IT
@cmd_it · 24,375
Telegram ranks this channel #10 of 82 here — alongside 81 others — read 16 September 2026
SecAtor
@true_secator · 41,748
Telegram ranks this channel #11 of 78 here — alongside 77 others — read 29 August 2026
infosecurity
@tg_infosec · 26,779
Telegram ranks this channel #12 of 74 here — alongside 73 others — read 11 September 2026
Russian OSINT
@Russian_OSINT · 47,701
Telegram ranks this channel #12 of 82 here — alongside 81 others — read 26 August 2026
Social Engineering
@Social_engineering · 125,008
Telegram ranks this channel #12 of 82 here — alongside 81 others — read 13 August 2026
Лаборатория хакера
@lab_hack · 25,556
Telegram ranks this channel #13 of 71 here — alongside 70 others — read 14 September 2026
Investigation & Forensic TOOLS
@forensictools · 22,417
Telegram ranks this channel #14 of 74 here — alongside 73 others — read 20 September 2026
Интернет-Розыск
@irozysk · 45,953
Telegram ranks this channel #14 of 79 here — alongside 78 others — read 27 August 2026
Борьба с киберпреступностью | F6
@f6_cybersecurity · 22,318
Telegram ranks this channel #15 of 85 here — alongside 84 others — read 21 September 2026
Task No Face
@TaskNoFace · 29,506
Telegram ranks this channel #15 of 78 here — alongside 77 others — read 8 September 2026
Kali Linux
@linuxkalii · 55,412
Telegram ranks this channel #17 of 89 here — alongside 88 others — read 23 August 2026
Бункер Хакера
@book_academ · 21,429
Telegram ranks this channel #18 of 72 here — alongside 71 others — read 23 September 2026
no system is safe // cybersec
@nsis_cybersec · 21,653
Telegram ranks this channel #19 of 71 here — alongside 70 others — read 23 September 2026
ZeroDay | Кибербезопасность
@cybersec_academy · 42,838
Telegram ranks this channel #19 of 70 here — alongside 69 others — read 29 August 2026

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

“Codeby” (@codeby_sec), 37,041 subscribers as measured 26 September 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.