Telegram RegisterThe public register of Telegram
Telegram profile photo for infosec

Channel

infosec

@it_secur

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

61,439subscribers

+429 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-1001418901040
TypeChannel
Username@it_secur
DescriptionCopyright: @SEAdm1n Вакансии: @infosec_work Информационная безопасность. Литература для ИТ специалистов. Пентест, DevOps, Администрирование. Приобрести рекламное размещение: https://telega.in/c/it_secur РКН: https://vk.cc/cN3VCI
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live7 September 2026
Measurements held29
Confirmed unchanged1 time, most recently 7 September 2026
On Telegramt.me/it_secur

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 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 why it has no browse page of its own yet.

Growth

61,01061,43961,224.56 August 2026 — 61,010 subscribers6 August 2026 — 61,023 subscribers7 August 2026 — 61,060 subscribers8 August 2026 — 61,056 subscribers9 August 2026 — 61,055 subscribers10 August 2026 — 61,061 subscribers11 August 2026 — 61,065 subscribers12 August 2026 — 61,066 subscribers13 August 2026 — 61,050 subscribers14 August 2026 — 61,078 subscribers16 August 2026 — 61,094 subscribers17 August 2026 — 61,111 subscribers18 August 2026 — 61,115 subscribers19 August 2026 — 61,103 subscribers20 August 2026 — 61,101 subscribers22 August 2026 — 61,139 subscribers23 August 2026 — 61,174 subscribers25 August 2026 — 61,189 subscribers25 August 2026 — 61,209 subscribers27 August 2026 — 61,216 subscribers28 August 2026 — 61,243 subscribers29 August 2026 — 61,264 subscribers29 August 2026 — 61,292 subscribers30 August 2026 — 61,320 subscribers31 August 2026 — 61,330 subscribers1 September 2026 — 61,343 subscribers3 September 2026 — 61,350 subscribers4 September 2026 — 61,359 subscribers7 September 2026 — 61,439 subscribers6 August 20267 September 2026
29 measurements spanning 32 days, net +429. 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 60,946–61,503 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 29
Measured (UTC)SubscribersChange
7 Sept 2026, 13:0061,439+80
4 Sept 2026, 15:3961,359+9
3 Sept 2026, 00:4361,350+7
1 Sept 2026, 19:1561,343+13
31 Aug 2026, 19:5861,330+10
30 Aug 2026, 17:4361,320+28
29 Aug 2026, 20:4661,292+28
29 Aug 2026, 00:0561,264+21
28 Aug 2026, 02:4261,243+27
27 Aug 2026, 00:4961,216+7
25 Aug 2026, 21:1461,209+20
25 Aug 2026, 00:0561,189+15
23 Aug 2026, 12:0861,174+35
22 Aug 2026, 00:1761,139+38
20 Aug 2026, 21:4461,101-2
19 Aug 2026, 19:3461,103-12
18 Aug 2026, 18:5261,115+4
17 Aug 2026, 18:5361,111+17
16 Aug 2026, 14:3861,094+16
14 Aug 2026, 23:1661,078first reading

Engagement

112 posts held, back to 3 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 69 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
11.1%
avg views ÷ 61,439 subscribers
Avg views / post
6,830
93 posts measured
Reaction rate
1.07%
reactions ÷ views · ER floor
Posts in window
93
of 112 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 8 September 2026
Posts held112 (3 August 20268 September 2026)
Views total635,217
Reactions total6,803
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Sept 2026, 09:15 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,620
Videos
148
Links
2,390

Lifetime counters from Telegram’s own channel header, read 8 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
1m 10s
Average length
18s

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

7,893 reactions across 109 posts, in 61 distinct kinds. The most used accounts for 21.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥1,65521.0%
👍1,06313.5%
😁89611.4%
86811.0%
custom 54587248699506770627809.88%
custom 53460396555465148443844.87%
🤣3654.62%
custom 53639749021036990112863.62%
🎉1802.28%
custom 53955426583262409751431.81%
😭1251.58%
🫡1051.33%
custom 54565845889628316651011.28%
👏971.23%
custom 5235930206044167357961.22%
🤬780.988%
💯600.76%
👎580.735%
🤯520.659%
🤮460.583%
41 further kinds4555.76%

Custom emoji. 6 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 112 of the 112 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 8,043 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 112 most recent posts we hold, published 3 August 2026 to 8 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
182
across the posts below
Posts paid on
88
of 112 we hold a reading for · 79%
Most on one post
4
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @it_secur. 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 112 most recent posts we hold for this entry, published 3 August 2026 to 8 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
7.14%
8 of 112 posts carry an ad marker
Regulatory tokens
8
posts carrying an erid · 8 distinct tokens
Median views · ads
6,450
over 8 measured posts
Median views · rest
6,670
over 104 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
2VSb5y2nmMt111 August 202611 August 2026
2Vtzquau9YF115 August 202615 August 2026
2VtzqvwcGu9126 August 202626 August 2026
2Vtzqvy6Cuh114 August 202614 August 2026
2W5zFGGzvdo113 August 202613 August 2026
2W5zFGMWwZ318 September 20268 September 2026
2W5zFGYjDo717 September 20267 September 2026
2W5zFGtXGjb120 August 202620 August 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.

Measured over the 112 most recent posts we hold, published 3 August 2026 to 8 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

8 Sept 2026, 09:09 UTC437 views6 reactionsread 8 September 2026
Advertisementerid 2W5zFGMWwZ3Photo

Информационная безопасность в эпоху ИИ: о чем важно знать уже сейчас? Обсудим 8 октября на бесплатной конференции Selectel ТехноДень о кибербезопасности, ИТ-инфраструктуре, ИИ и данных. Эксперты топовых технологических компаний расскажут: 🔺Как применение нейросетей меняет рабочие процессы с точки зрения ИБ и как снизить риски. 🔺Где проходит граница между безопасностью и развитием бизнеса. Должен ли CISO ограничива

2👍2🔥1custom 53955426583262409751

7 Sept 2026, 14:38 UTC≈4,850 views67 reactionsread 8 September 2026
Photo

🤭 Инженер Google Cloud устроил сбой, случайно отключив от сети оборудование, которое обслуживал - об этом инциденте написали в блоге Google Cloud. • Проблему зафиксировали в 07:41 по тихоокеанскому времени. В разгар инцидента объем трафика в пострадавшей области упал на 100%, виртуальные машины были недоступны. Сбой повлиял на работу Compute Engine, Kubernetes Engine, Cloud Run / Google App Engine, AlloyDB для Post

custom 545658458896283166540😁19🔥61👍1

7 Sept 2026, 10:04 UTC≈5,120 views35 reactions1 Starread 8 September 2026
Photo

• Книгу "Computer Networks: A Systems Approach" актуализировали и добавили тонну полезного материала. • Напомню, что эта книга посвящена принципам построения сетей и работе с сетевыми технологиями. В материале смогут разобраться даже те, кто только знакомится с темой! Благодаря этой книге вы можете изучить ключевые концепции и принципы построения сетей, а также разберете ряд примеров современных технологий и серви

🔥19👍123🙏1

7 Sept 2026, 07:04 UTC≈5,120 views19 reactionsread 8 September 2026
Advertisementerid 2W5zFGYjDo7Photo

🚨 82% компаний МСБ уже сталкивались с киберинцидентами. А почтовые атаки становятся только сложнее. Фишинг, BEC, mail bombing, новые домены и обходы защиты — разберём, как меняются угрозы и чем им отвечать. 📡 10 сентября в 11:00 МСК — стрим «Лаборатории Касперского» «Не верь входящим! Почтовые угрозы 2026 и новые возможности KSMG 3.1» На стриме покажут: — что нового в решении для защиты почты — как выявлять BEC и н

👍8😁4🥰3custom 54565845889628316652💋1💘1

7 Sept 2026, 04:33 UTC≈5,560 views111 reactionsread 8 September 2026
Photo

• Доброе утро 🫠 #Понедельник

😭78😁1810🔥5

6 Sept 2026, 08:40 UTC≈6,070 views92 reactions3 Starsread 8 September 2026
Photo

• Немного статистики: по данным statcounter процент использования Linux и MacOS на десктопах летит в космос! • Если месяц назад процент использования Linux составлял 7.53%, то сейчас он вырос до 8.88%. Такой показатель был достигнут впервые! • MacOS также фиксирует рекорд - доля использования составляет 15.31%. В прошлом месяце этот показатель был на уровне 7.61%. • А вот у окошек случился отрицательный рост -

👍51custom 534603965554651484421🔥127🍾1

5 Sept 2026, 10:32 UTC≈6,090 views50 reactions2 Starsread 8 September 2026
Photo

💪 Самый мощный суперкомпьютер 60-х. • 46 лет назад, 5 сентября 1980 года в Университете Бригама Янга был навсегда выключен последний суперкомпьютер IBM Stretch. Этот сверхмощный мейнфрейм, известный также под наименованием IBM 7030, стал результатом научно-исследовательского проекта, который корпорация IBM начала еще в 1955 году - его целью было построить суперкомпьютер, в сотни раз превосходящий по мощности все, ч

👍22custom 534603965554651484414🔥73🤔2👏1custom 53955426583262409751

4 Sept 2026, 18:40 UTC≈5,640 views65 reactions1 Starread 8 September 2026

Posted without readable text

👍39🔥14🎉73custom 53460396555465148441custom 53639749021036990111

4 Sept 2026, 17:25 UTC≈8,490 views116 reactionsread 8 September 2026
Photo

• Произошла классика: "криптоинвестор" Alex решил спросить Chat GPT, где можно обменять токены sFLR на WFLR. В ответ нейронка выдала результат, в котором была ссылка на фишинговый ресурс. • Alex перешел по ссылке, подключил кошелек и спустя несколько секунд потерял более 2.1 млн. баксов (180 млн. рублей). Средства сразу начали прогонять через миксеры и переводить на другие кошельки. • Сейчас Alex просит помощи в

🤣66custom 545872486995067706224custom 536397490210369901110🔥7custom 52359302060441673574😁31👍1

4 Sept 2026, 14:32 UTC≈5,990 views54 reactions1 Starread 8 September 2026
Photo

• Ребята из Бастион заказали сейф с электрическим замком на одном из маркетплейсов и вскрыли его китайскими палочками для суши за 5 минут. Статья получилась максимально интересной и будет полезна для специалистов по информационной безопасности: ➡️ https://habr.com/post/1075124 #Security

👍30🔥1373🥱1

4 Sept 2026, 11:33 UTC≈6,670 views76 reactions1 Starread 8 September 2026
Photo

• В 1998 году, на финальном этапе производства мультика "История игрушек 2" кто-то в Pixar выполнил /bin/rm -r -f * не в том каталоге, и примерно 90% фильма удалилось на глазах у команды. Бэкапы, конечно, были, но есть два "но". Система резервного копирования не работала (переполненный диск маскировал ошибки), а восстановленная копия оказалась частично битой, и это вскрылось не сразу. • Фильм спасла копия на домаш

custom 534603965554651484441👍16🔥96🤔3🤡1

3 Sept 2026, 16:33 UTC≈7,650 views84 reactions1 Starread 8 September 2026
Photo

• Немного вечернего оффтопа: в Бразилии есть пивоварня, которая производит WinRAR Session IPA - это крафтовое пиво с отсылкой на бесконечный пробный период архиватора WinRaR. К слову, у пива нет какой-то фиксированной цены, а выпускается оно ограниченными партиями как сувенирный крафт. • Забавно, что SMM-специалист WinRaR благодарит и репостит всех, кто пишет в Х о покупке лицензии, мерча, а теперь еще и пива. #О

custom 534603965554651484438🔥27👍8🍾74

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Mentions

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

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.

Social Engineering
@Social_engineering · 125,064
#1
S.E.Reborn
@S_E_Reborn · 22,355
#2
SecurityLab.ru
@SecLabNews · 83,998
#3
Этичный Хакер
@hack_less · 228,204
#4
SecAtor
@true_secator · 41,627
#5
Похек
@poxek · 16,707
#6
infosecurity
@tg_infosec · 26,807
#7
S.E.Book
@S_E_Book · 23,175
#8
Codeby
@codeby_sec · 36,935
#9
Чёрный Треугольник
@black_triangle_tg · 63,847
#10
Пост Лукацкого
@alukatsky · 37,739
#11
Admin Guides | Сисадмин
@admguides · 11,883
#12
no system is safe // cybersec
@nsis_cybersec · 21,652
#13
Архив Безопасника
@secure_archive · 10,748
#14
Лаборатория хакера
@lab_hack · 25,666
#15
ZeroDay | Кибербезопасность
@cybersec_academy · 42,850
#16
Life-Hack - Хакер
@haccking · 63,216
#17
Cybred
@cybred · 11,052
#18
Записки Безопасника
@infosec_globe · 18,193
#19
Kali Linux
@linuxkalii · 55,240
#20
Интернет-Розыск
@irozysk · 46,119
#21
Белый хакер
@bezopasno_soft · 29,691
#22
OFFZONE
@offzone_moscow · 7,346
#23
Не хакинг, а ИБ
@searchack · 18,292
#24
APT
@APT_Notes · 16,340
#25
ServerAdmin.ru
@srv_admin · 32,526
#26
Серверная Админа | Компьютерные сети
@school_network · 26,662
#27
Positive Technologies
@Positive_Technologies · 28,808
#28
k8s (in)security
@k8security · 13,081
#29
CyberINS // Лаборатория ИБешника
@cyberins · 11,506
#30
Бункер Хакера
@book_academ · 21,462
#31
BI.ZONE
@bizone_channel · 11,148
#32
Inf0 | ИБ, OSINT
@info_cybersecurity · 10,205
#33
SecuriXy.kz
@securixy_kz · 10,123
#34
Investigation & Forensic TOOLS
@forensictools · 22,294
#35
BashMaster
@bash_help · 8,880
#36
Сетевик Джонни // Network Admin
@iscode · 5,803
#37
Пакет Безопасности
@package_security · 33,214
#38
IT MEGA облако
@it_mega_disk · 11,326
#39
Типичный Сисадмин
@sysodmins · 37,988
#40
YAH
@YAH_Channel · 7,558
#41
PWN AI
@pwnai · 7,145
#42
White Hat
@kind_hack · 12,002
#43
Network Admin
@networkadm · 12,415
#44
IT-KB 🤖
@ITKB_channel · 7,983
#45
DevSecOps Talks
@devsecops_weekly · 8,017
#46
AM Live
@anti_malware · 13,162
#47
Арсенал Безопасника
@arsenal_security · 15,202
#48
Linux / Линукс
@linux_gram · 13,530
#49
Секреты сисадмина | DevOps, Linux, SRE
@sysadmin_library · 25,369
#50
Хабр
@habr_com · 132,178
#51
Blue (h/c)at Café
@bh_cat · 3,965
#52
КИБЕР МЕДИА
@secmedia · 5,929
#53
Мыслить как безопасник
@artemov_security · 9,022
#54
OSINT | Форензика
@osintkanal · 14,325
#55
Системный администратор
@i_odmin · 26,654
#56
Mr. Robot
@elliot_cybersec · 39,084
#57
Хакер — Xakep.RU
@xakep_ru · 39,389
#58
Open Source
@open_source_friend · 52,042
#59
CyberYozh
@cyberyozh_official · 62,680
#60
Вакансии в ИБ | infosec
@infosec_work · 15,513
#61
Russian OSINT
@Russian_OSINT · 47,551
#62
Эксплойт
@exploitex · 2,022,579
#63
Утечки информации
@dataleak · 119,766
#64
Управление Уязвимостями и прочее
@avleonovrus · 11,996
#65
STEIN: ИБ, OSINT
@secur_researcher · 14,025
#66
Information Security Memes
@infosecmemes · 9,709
#67
Bash Days | Linux | DevOps
@bashdays · 23,701
#68
Standoff 365
@standoff_365 · 8,229
#69
RuSecJobs Channel
@RuSecJobs · 11,255
#70
Бэкдор
@whackdoor · 1,613,979
#71
Offensive Xwitter
@OffensiveTwitter · 20,875
#72
PRO:PENTEST
@pro_pentest · 10,102
#73
linkmeup
@linkmeup_podcast · 17,346
#74
Hacker News
@HNews · 7,298
#75
[PYTHON:TODAY]
@python2day · 63,836
#76
Physics.Math.Code
@physics_lib · 146,369
#77
T.Hunter
@tomhunter · 14,247
#78
SHADOW:Group
@shadow_group_tg · 11,488
#79
Багхантер
@bughunter_circuit · 3,548
#80
vx-underground
@vxunderground · 51,951
#81

Read from Telegram’s recommendation API, most recently 22 August 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.

Social Engineering
@Social_engineering · 125,064
Telegram ranks this channel #1 of 82 here — alongside 81 others — read 13 August 2026
ZeroDay | Кибербезопасность
@cybersec_academy · 42,850
Telegram ranks this channel #2 of 70 here — alongside 69 others — read 29 August 2026
Этичный Хакер
@hack_less · 228,204
Telegram ranks this channel #2 of 81 here — alongside 80 others — read 12 August 2026
Белый хакер
@bezopasno_soft · 29,691
Telegram ranks this channel #3 of 78 here — alongside 77 others — read 8 September 2026
Kali Linux
@linuxkalii · 55,240
Telegram ranks this channel #3 of 89 here — alongside 88 others — read 23 August 2026
Кладовка Pavlu
@KladovkaPavlu · 65,163
Telegram ranks this channel #4 of 76 here — alongside 75 others — read 4 September 2026
Life-Hack - Хакер
@haccking · 63,216
Telegram ranks this channel #5 of 85 here — alongside 84 others — read 21 August 2026
Codeby
@codeby_sec · 36,935
Telegram ranks this channel #6 of 76 here — alongside 75 others — read 1 September 2026
Чёрный Треугольник
@black_triangle_tg · 63,847
Telegram ranks this channel #6 of 87 here — alongside 86 others — read 21 August 2026
SecurityLab.ru
@SecLabNews · 83,998
Telegram ranks this channel #7 of 90 here — alongside 89 others — read 18 August 2026
SecAtor
@true_secator · 41,627
Telegram ranks this channel #8 of 78 here — alongside 77 others — read 29 August 2026
Интернет-Розыск
@irozysk · 46,119
Telegram ranks this channel #9 of 79 here — alongside 78 others — read 27 August 2026
Пакет Безопасности
@package_security · 33,214
Telegram ranks this channel #10 of 82 here — alongside 81 others — read 4 September 2026
ServerAdmin.ru
@srv_admin · 32,526
Telegram ranks this channel #11 of 96 here — alongside 95 others — read 5 September 2026
Task No Face
@TaskNoFace · 29,714
Telegram ranks this channel #12 of 78 here — alongside 77 others — read 8 September 2026
Типичный Сисадмин
@sysodmins · 37,988
Telegram ranks this channel #13 of 93 here — alongside 92 others — read 31 August 2026
Selectel
@Selectel · 63,435
Telegram ranks this channel #13 of 96 here — alongside 95 others — read 21 August 2026
Termux, please
@termuxplz0x41 · 32,844
Telegram ranks this channel #15 of 54 here — alongside 53 others — read 4 September 2026
TechNews
@techlucker · 43,594
Telegram ranks this channel #16 of 79 here — alongside 78 others — read 28 August 2026
Physics.Math.Code
@physics_lib · 146,369
Telegram ranks this channel #17 of 72 here — alongside 71 others — read 13 August 2026
Open Source
@open_source_friend · 52,042
Telegram ranks this channel #22 of 87 here — alongside 86 others — read 24 August 2026
Пост Лукацкого
@alukatsky · 37,739
Telegram ranks this channel #24 of 89 here — alongside 88 others — read 31 August 2026
CyberYozh
@cyberyozh_official · 62,680
Telegram ranks this channel #24 of 81 here — alongside 80 others — read 21 August 2026
Троянский конь | IT, технологии
@trojan_anonym · 64,700
Telegram ranks this channel #24 of 82 here — alongside 81 others — read 21 August 2026

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

“infosec” (@it_secur), 61,439 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/it_secur.

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.