Telegram RegisterThe public register of Telegram
Telegram profile photo for infosecurity

Channel

infosecurity

@tg_infosec

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

26,786subscribers

-57 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001203496893
TypeChannel
Username@tg_infosec
CreatedBetween 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live19 September 2026
Measurements held31
Confirmed unchanged2 times, most recently 19 September 2026
On Telegramt.me/tg_infosec

Topic

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

26,78626,84826,8176 August 2026 — 26,843 subscribers6 August 2026 — 26,843 subscribers7 August 2026 — 26,842 subscribers8 August 2026 — 26,848 subscribers9 August 2026 — 26,846 subscribers10 August 2026 — 26,839 subscribers11 August 2026 — 26,840 subscribers12 August 2026 — 26,834 subscribers13 August 2026 — 26,835 subscribers14 August 2026 — 26,830 subscribers16 August 2026 — 26,827 subscribers17 August 2026 — 26,822 subscribers18 August 2026 — 26,818 subscribers19 August 2026 — 26,812 subscribers20 August 2026 — 26,805 subscribers21 August 2026 — 26,798 subscribers23 August 2026 — 26,818 subscribers24 August 2026 — 26,832 subscribers26 August 2026 — 26,830 subscribers27 August 2026 — 26,836 subscribers28 August 2026 — 26,838 subscribers30 August 2026 — 26,833 subscribers31 August 2026 — 26,826 subscribers1 September 2026 — 26,824 subscribers3 September 2026 — 26,812 subscribers5 September 2026 — 26,807 subscribers9 September 2026 — 26,804 subscribers11 September 2026 — 26,805 subscribers13 September 2026 — 26,794 subscribers15 September 2026 — 26,788 subscribers17 September 2026 — 26,786 subscribers6 August 202617 September 2026
31 measurements spanning 41 days, net -57. 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 26,777–26,857 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 31
Measured (UTC)SubscribersChange
17 Sept 2026, 02:1826,786-2
15 Sept 2026, 01:4126,788-6
13 Sept 2026, 10:1626,794-11
11 Sept 2026, 13:2126,805+1
9 Sept 2026, 00:0226,804-3
5 Sept 2026, 19:1926,807-5
3 Sept 2026, 21:3626,812-12
1 Sept 2026, 12:2526,824-2
31 Aug 2026, 15:5326,826-7
30 Aug 2026, 14:2326,833-5
28 Aug 2026, 07:5826,838+2
27 Aug 2026, 05:5726,836+6
26 Aug 2026, 02:3426,830-2
24 Aug 2026, 23:0926,832+14
23 Aug 2026, 07:0726,818+20
21 Aug 2026, 22:1426,798-7
20 Aug 2026, 16:5726,805-7
19 Aug 2026, 17:1326,812-6
18 Aug 2026, 14:1626,818-4
17 Aug 2026, 12:2826,822first reading

Engagement

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

ERR · 30 days
7.86%
avg views ÷ 26,786 subscribers
Avg views / post
2,100
23 posts measured
Reaction rate
0.908%
reactions ÷ views · ER floor
Posts in window
23
of 63 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 20 of 23 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 3 September 2026
Posts held63 (3 August 20263 September 2026)
Views total48,408
Reactions total377
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 11:45 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

Video runtime
1m 47s
Average length
27s

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

1,155 reactions across 58 posts, in 26 distinct kinds. The most used accounts for 27.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁32127.8%
👍29225.3%
16614.4%
🤣13111.3%
🔥625.37%
😭373.20%
💯322.77%
🤩201.73%
🤯161.39%
❤‍🔥110.952%
90.779%
🆒80.693%
60.519%
😎60.519%
😢60.519%
🤔50.433%
🤬50.433%
🗿40.346%
🙈40.346%
🐳30.26%
6 further kinds110.952%

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

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

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @tg_infosec. 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 63 most recent posts we hold for this entry, published 3 August 2026 to 3 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
4.76%
3 of 63 posts carry an ad marker
Regulatory tokens
3
posts carrying an erid · 3 distinct tokens
Median views · ads
1,580
over 3 measured posts
Median views · rest
2,280
over 60 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. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2VtzqvHNzx3112 August 202612 August 2026
2VtzqvwcGu912 September 20262 September 2026
2W5zFGgkREh13 September 20263 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.

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

3 Sept 2026, 11:33 UTC335 views4 reactionsread 3 September 2026
Photo

• Журнал "Хакер" - 1999 год. #Разное #Юмор

4

3 Sept 2026, 07:04 UTC983 views0 reactionsread 3 September 2026
Advertisementerid 2W5zFGgkREhPhoto

Клиент просит бэкап и DRaaS, а своей инфраструктуры у вас нет Вы ведёте ИТ у нескольких компаний. Приходит запрос — вынести 1С в облако, поднять терминальный сервер, настроить бэкап под 152-ФЗ. Строить под это своё железо смысла нет, и запрос уходит на сторону вместе с деньгами. Партнёрская программа LanCloud закрывает этот разрыв. Клиента ведёте вы. Мы берём инфраструктуру: помогаем подобрать конфигурацию, рассчит

2 Sept 2026, 18:45 UTC≈1,180 views7 reactionsread 3 September 2026
Photo

• Более 5000 аккаунтов Dropbox были взломаны через Lenovo ID. Хакеры могли просматривать и скачивать все файлы пользователей, которые хранились в Dropbox. • Соль в том, что хакеры воспользовались учетной записью для доступа к продуктам и сервисам Lenovo, так как Dropbox позволял входить в свои аккаунты через подтвержденные Lenovo ID. • Косяк обнаружили в механизме проверки почты Lenovo. Из-за нее хакеры могли со

😁52

2 Sept 2026, 11:33 UTC≈1,630 views9 reactionsread 3 September 2026
Photo

• А вы знали, что 16 лет назад в России был журнал с Linux? Дело в том, что в 2009 году компания Americhip представила технологию под названием Video in Print, которая позволяла встроить в обычный бумажный журнал специальную страницу с полноценным видеороликом. Понятное дело, что основной ориентир был на рекламодателей, да и такая реклама была отнюдь не дешевой из-за необходимости ручной сборки страницы, но тем не м

🔥7🆒2

2 Sept 2026, 08:04 UTC≈1,580 viewsread 3 September 2026
Advertisementerid 2VtzqvwcGu9Photo

Week Offer для инженеров AppSec, InfraSec и SOC L3 Приглашаем инженеров по информационной безопасности с опытом от 2 лет получить офер в Яндекс за неделю. Как всё устроено: ♒️Зарегистрируйтесь до 4 сентября. ♒️Пройдите технические секции 12 и 13 сентября. ♒️Познакомьтесь с нанимающими менеджерами и получите офер 14–18 сентября. Формат полностью удалённый, от вас нужен только ноутбук и тихое место, где вас никто н

1 Sept 2026, 15:33 UTC≈1,680 views5 reactionsread 3 September 2026
Photo

✍️ Откуда взялся security.txt ? • 10 лет назад, ИБ-исследователь и бывший аналитик компании HackerOne Эд Фодил, предложил реализовать стандарт security.txt. Он описывает содержимое специального файла - того самого security.txt - который размещается в директории /.well-known и включает контактную информацию и инструкции для оповещения об уязвимостях. По сути, это - аналог robots.txt, только для специалистов по инфор

👍5

1 Sept 2026, 11:33 UTC≈2,050 views46 reactionsread 3 September 2026
Photo

• Текущие реалии... #Юмор

🤣33😁6😢6👍1

31 Aug 2026, 15:33 UTC≈2,000 views5 reactionsread 3 September 2026
Photo

• В январе этого года компания Apple выпустила обновлённые метки AirTag, которые используются для отслеживания и поиска потерянных вещей (ключей, чемоданов, кошельков и т.д.). В устройство установили более громкий динамик и UWB-чип с увеличенной зоной покрытия. • Функционал метки действительно очень крутой и нужный, вот только сталкеры могут использовать AirTag для слежки за людьми. • Несмотря на меры Apple и Go

👍5

31 Aug 2026, 12:33 UTC≈1,670 views8 reactionsread 3 September 2026
Photo

• 50 лет назад молодой Билл Гейтс начал сражаться с первыми в мире пиратами софта. Он написал "Открытое письмо к энтузиастам" (фото выше), жалуясь на то, что его самая первая коммерческая программа подверглась пиратству. • Билл создал версию языка программирования BASIC для Altair 8800, работая с 22-летним Полом Алленом. Именно Altair 8800 стал первым в мире коммерчески успешным домашним компьютером. Глава компани

3🌚2🤔2🕊1

31 Aug 2026, 09:14 UTC≈1,950 views21 reactionsread 3 September 2026
Video

Не можете вспомнить пароль от корпоративных сервисов? Это классика. Оставьте ее для музеев. А для работы используйте менеджер паролей. Kaspersky Password Manager для бизнеса поможет вашим сотрудникам безопасно хранить и использовать пароли и другие конфиденциальные данные. Чтобы узнать, как перестать писать пароли на стикерах, подключайтесь к стриму 3 сентября в 11:00: эксперты компании расскажут о ключевых функци

😁15❤‍🔥3🔥3

29 Aug 2026, 11:33 UTC≈2,570 views10 reactionsread 3 September 2026
Photo

• Пост выходного дня: Где лучше хранить холодные данные? Полный обзор на все типы физических носителей от FDD до LTO и M-disk. • Автор этого материала сделал максимально полный обзор на все типы физических носителей которые доступны обычному человеку (FDD, NAND, CD, DVD, BD, SSD, HDD, LTO) и подходят для архивного хранения данных! ➡️ https://habr.com/ru/post/988926 • К слову, информация из этой статьи есть такж

👍10

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

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 4 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

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,008
#1
infosec
@it_secur · 61,761
#2
Похек
@poxek · 16,779
#3
Архив Безопасника
@secure_archive · 10,786
#4
SecurityLab.ru
@SecLabNews · 84,459
#5
S.E.Reborn
@S_E_Reborn · 22,374
#6
Вакансии в ИБ | infosec
@infosec_work · 15,677
#7
SecAtor
@true_secator · 41,700
#8
Белый хакер
@bezopasno_soft · 29,706
#9
Чёрный Треугольник
@black_triangle_tg · 63,891
#10
ZeroDay | Кибербезопасность
@cybersec_academy · 42,838
#11
Codeby
@codeby_sec · 36,985
#12
Не хакинг, а ИБ
@searchack · 18,244
#13
Пост Лукацкого
@alukatsky · 37,862
#14
S.E.Book
@S_E_Book · 23,170
#15
Записки Безопасника
@infosec_globe · 18,120
#16
Russian OSINT
@Russian_OSINT · 47,701
#17
OFFZONE
@offzone_moscow · 7,369
#18
Хакер — Xakep.RU
@xakep_ru · 39,506
#19
Life-Hack - Хакер
@haccking · 63,203
#20
Admin Guides | Сисадмин
@admguides · 11,926
#21
Mr. Robot
@elliot_cybersec · 38,957
#22
Cybred
@cybred · 11,091
#23
Inf0 | ИБ, OSINT
@info_cybersecurity · 10,238
#24
SecuriXy.kz
@securixy_kz · 10,166
#25
no system is safe // cybersec
@nsis_cybersec · 21,653
#26
Бункер Хакера
@book_academ · 21,467
#27
Лаборатория хакера
@lab_hack · 25,564
#28
Positive Technologies
@Positive_Technologies · 28,968
#29
APT
@APT_Notes · 16,571
#30
Пакет Безопасности
@package_security · 33,106
#31
YAH
@YAH_Channel · 7,567
#32
BI.ZONE
@bizone_channel · 11,212
#33
RuSecJobs Channel
@RuSecJobs · 11,322
#34
ИБ Книга | Библиотека ИБ
@itbook_library · 15,826
#35
CyberINS // Лаборатория ИБешника
@cyberins · 11,451
#36
k8s (in)security
@k8security · 13,119
#37
Investigation & Forensic TOOLS
@forensictools · 22,368
#38
Inside
@in51d3 · 7,996
#39
Hacker News
@HNews · 7,293
#40
DevSecOps Talks
@devsecops_weekly · 8,025
#41
Арсенал Безопасника
@arsenal_security · 15,214
#42
White Hat
@kind_hack · 11,972
#43
IT-KB 🤖
@ITKB_channel · 7,992
#44
Project Omega | ИБ
@omega_cybersec · 8,825
#45
CyberCamp
@CYBERCAMP_ONLINE · 8,668
#46
Кибербез образование | cybersecurity-roadmap.ru
@cyber_edu · 6,023
#47
Linux / Линукс
@linux_gram · 13,636
#48
Хабр
@habr_com · 132,465
#49
Order of Six Angles
@orderofsixangles · 5,289
#50
Мыслить как безопасник
@artemov_security · 9,043
#51
AM Live
@anti_malware · 13,147
#52
Open Source
@open_source_friend · 52,224
#53
Kali Linux
@linuxkalii · 55,349
#54
Управление Уязвимостями и прочее
@avleonovrus · 12,130
#55
Серверная Админа | Компьютерные сети
@school_network · 26,624
#56
Standoff 365
@standoff_365 · 8,268
#57
Эксплойт
@exploitex · 2,041,128
#58
Утечки информации
@dataleak · 119,401
#59
PRO:PENTEST
@pro_pentest · 10,096
#60
Information Security Memes
@infosecmemes · 9,694
#61
PWN AI
@pwnai · 7,283
#62
Бэкдор
@whackdoor · 1,603,481
#63
ServerAdmin.ru
@srv_admin · 32,537
#64
Bash Days | Linux | DevOps
@bashdays · 23,674
#65
Blue (h/c)at Café
@bh_cat · 3,975
#66
SHADOW:Group
@shadow_group_tg · 11,482
#67
RED Security
@redsecurity_co · 5,191
#68
Сетевик Джонни // Network Admin
@iscode · 5,798
#69
Offensive Xwitter
@OffensiveTwitter · 21,001
#70
T.Hunter
@tomhunter · 14,234
#71
AlexRedSec
@alexredsec · 4,007
#72
Linux Academy
@linuxacademiya · 28,422
#73
Багхантер
@bughunter_circuit · 3,514
#74

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

Social Engineering
@Social_engineering · 125,008
Telegram ranks this channel #3 of 82 here — alongside 81 others — read 13 August 2026
Белый хакер
@bezopasno_soft · 29,706
Telegram ranks this channel #6 of 78 here — alongside 77 others — read 8 September 2026
ZeroDay | Кибербезопасность
@cybersec_academy · 42,838
Telegram ranks this channel #6 of 70 here — alongside 69 others — read 29 August 2026
infosec
@it_secur · 61,761
Telegram ranks this channel #7 of 81 here — alongside 80 others — read 22 August 2026
S.E.Book
@S_E_Book · 23,170
Telegram ranks this channel #8 of 64 here — alongside 63 others — read 19 September 2026
S.E.Reborn
@S_E_Reborn · 22,374
Telegram ranks this channel #9 of 66 here — alongside 65 others — read 20 September 2026
Mr. Robot
@elliot_cybersec · 38,957
Telegram ranks this channel #13 of 70 here — alongside 69 others — read 31 August 2026
Life-Hack - Хакер
@haccking · 63,203
Telegram ranks this channel #16 of 85 here — alongside 84 others — read 21 August 2026
Чёрный Треугольник
@black_triangle_tg · 63,891
Telegram ranks this channel #16 of 87 here — alongside 86 others — read 21 August 2026
Этичный Хакер
@hack_less · 229,400
Telegram ranks this channel #16 of 81 here — alongside 80 others — read 12 August 2026
Лаборатория хакера
@lab_hack · 25,564
Telegram ranks this channel #18 of 71 here — alongside 70 others — read 14 September 2026
Пакет Безопасности
@package_security · 33,106
Telegram ranks this channel #19 of 82 here — alongside 81 others — read 4 September 2026
Хакер — Xakep.RU
@xakep_ru · 39,506
Telegram ranks this channel #19 of 83 here — alongside 82 others — read 30 August 2026
CYBER HUNTER - Кибербезопасность
@cyberbezopasno · 53,341
Telegram ranks this channel #19 of 50 here — alongside 49 others — read 26 August 2026
Интернет-Розыск
@irozysk · 46,000
Telegram ranks this channel #20 of 79 here — alongside 78 others — read 27 August 2026
Termux, please
@termuxplz0x41 · 32,763
Telegram ranks this channel #22 of 54 here — alongside 53 others — read 4 September 2026
Codeby
@codeby_sec · 36,985
Telegram ranks this channel #25 of 76 here — alongside 75 others — read 1 September 2026
IT и безопасность
@tg_security · 26,613
Telegram ranks this channel #26 of 91 here — alongside 90 others — read 12 September 2026
Task No Face
@TaskNoFace · 29,568
Telegram ranks this channel #27 of 78 here — alongside 77 others — read 8 September 2026
SecAtor
@true_secator · 41,700
Telegram ranks this channel #27 of 78 here — alongside 77 others — read 29 August 2026
Russian OSINT
@Russian_OSINT · 47,701
Telegram ranks this channel #27 of 82 here — alongside 81 others — read 26 August 2026
SecurityLab.ru
@SecLabNews · 84,459
Telegram ranks this channel #27 of 90 here — alongside 89 others — read 18 August 2026
Секреты сисадмина | DevOps, Linux, SRE
@sysadmin_library · 25,649
Telegram ranks this channel #31 of 85 here — alongside 84 others — read 13 September 2026
Системный администратор
@i_odmin · 26,662
Telegram ranks this channel #31 of 89 here — alongside 88 others — read 12 September 2026

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

“infosecurity” (@tg_infosec), 26,786 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/tg_infosec.

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.