Telegram RegisterThe public register of Telegram
Telegram profile photo for Лаборатория хакера

Channel

Лаборатория хакера

@lab_hack

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

25,423subscribers

-499 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-1001822391833
TypeChannel
Username@lab_hack
DescriptionОбзоры иб-инструментов с github, книги, курсы по ИБ. Сотрудничество: @workhouse_price Канал на бирже: https://telega.in/c/lab_hack Канал в реестре РКН: https://clck.ru/3Fzjwv
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live10 November 2026
Measurements held64
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/lab_hack

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 10 September 2026 and assigned it the closest of 31 fixed categories, at 100% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Growth

25,42325,92225,672.56 August 202610 November 2026
64 measurements spanning 96 days, net -499. 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 25,348–25,997 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)SubscribersChange
10 Nov 2026, 16:4925,423-16
9 Nov 2026, 02:5025,439-10
7 Nov 2026, 17:2125,449-8
6 Nov 2026, 17:3625,457-11
5 Nov 2026, 17:4025,468-1
4 Nov 2026, 21:0625,469-7
3 Nov 2026, 19:5125,476-19
2 Nov 2026, 16:5625,495-14
1 Nov 2026, 15:1125,509-11
31 Oct 2026, 18:2725,520-1
30 Oct 2026, 18:1725,521-12
29 Oct 2026, 15:4625,533-12
28 Oct 2026, 16:3925,545-3
27 Oct 2026, 19:2725,548-13
26 Oct 2026, 19:0925,561-6
25 Oct 2026, 17:5125,567+1
24 Oct 2026, 20:5025,566-2
23 Oct 2026, 22:3925,568-4
22 Oct 2026, 23:1525,572-7
21 Oct 2026, 19:5625,579first reading

Engagement

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

ERR · 30 days
7.04%
avg views ÷ 25,423 subscribers
Avg views / post
1,790
35 posts measured
Reaction rate
0.337%
reactions ÷ views · ER floor
Posts in window
35
of 122 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 33 of 35 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 10 November 2026
Posts held122 (19 July 2026 – 10 November 2026)
Views total62,683
Reactions total203
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Nov 2026, 23:13 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
≈1,340
Videos
≈33
Links
≈1,430

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
26s
Average length
26s

Measured directly from 1 video 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,064 reactions across 120 posts, in 27 distinct kinds. The most used accounts for 30.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍32130.2%
❤22721.3%
👎12611.8%
⚡11310.6%
🆒918.55%
🔥545.08%
❤‍🔥272.54%
✍222.07%
🖕211.97%
🤔151.41%
🤣70.658%
😡50.47%
🌭40.376%
😁40.376%
🤨40.376%
🍌30.282%
💔30.282%
💯30.282%
🤬30.282%
☃20.188%
7 further kinds90.846%

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

Measured over the 122 most recent posts we hold, published 19 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.

Advertising

Ad load
3.28%
4 of 122 posts carry an ad marker
Regulatory tokens
3
posts carrying an erid · 3 distinct tokens
Median views · ads
941
over 4 measured posts
Median views · rest
2,140
over 118 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
2VtzqvpVTyW122 September 202622 September 2026
2W5zFGDRwj819 November 20269 November 2026
2W5zFHYdfvS110 November 202610 November 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 122 most recent posts we hold, published 19 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: 0 of 35 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

10 Nov 2026, 19:01 UTC377 viewsread 10 November 2026
Photo

🖥 Выпуск Apache Cloudberry 2.2.0, открытой альтернативы СУБД Greenplum Представлен выпуск распределенной СУБД Apache Cloudberry 2.2.0, продолжающей развитие открытой кодовой базы СУБД Greenplum, которая была превращена компанией Broadcom в закрытый продукт после приобретения VMware. Проект пока находится в инкубаторе Apache и будет переведен в число первичных проектов Apache после готовности инфраструктуры и сопрово…

10 Nov 2026, 16:52 UTC564 views7 reactionsread 10 November 2026
Photo

🔴В 2025 году Россияне заработали 5,3 млрд рублей на арбитраже криптовалют По данным Минфин 32% граждан покинули своё место работы поскольку в среднем уже в первый месяц смогли заработать 250 000 рублей, а через 2-3 месяца с легкостью вышли на семизначные числа. Самое смешное, что лишь 8% россиян что-то слышали об этой профессии хотя все инструкции бесплатно лежат на канале Арбитраж Криптовалют Там объясняют, как и…

👎5🍌2

10 Nov 2026, 09:26 UTC831 views1 reactionsread 10 November 2026
Photo

🖥 Как ориентироваться в пакете правил корреляции SIEM-системы? | Блог Касперского В описании контента SIEM-системы акцент практически всегда делается на количественные показатели: из коробки доступно cтолько-то правил корреляции, столько-то добавлено за год, они покрывают столько-то техник MITRE ATT&CK. Это, конечно, важные цифры, они действительно помогают оценить эффективность системы, и мы тоже периодически расск…

🤔1

10 Nov 2026, 06:26 UTC941 views5 reactionsread 10 November 2026
Advertisementerid 2W5zFHYdfvSVideo

Страшный сон любой компании — взлом. Что делать в первые часы и какие процессы восстанавливать в первую очередь? А если злоумышленники ещё внутри? Серия видеоподкастов «НЕ ЗАЩИЩЕНЫ. 24 часа после взлома» — это опыт работы команды «Инфосистемы Джет» на 100+ крупных инцидентах. 🔹Взлом произошёл. Что происходит с инфраструктурой, кто принимает решения и на чём теряется драгоценное время. 🔹Контроль возвращён, но бизнес…

✍3⚡1👍1

9 Nov 2026, 12:24 UTC≈1,200 views1 reactionsread 10 November 2026
Photo

🖥 Бэкдор с паролем 123456 и ключи в коде: как ИИ вскрывал «шифрованные» USB-накопители У «защищенной» флешки было два скрытых аккаунта с паролями 123456 и SECZURE.COM, и любым из них файлы расшифровывались без пароля администратора. В трех других продуктах для шифрования и защиты от копирования ключ вообще не зависел от пароля пользователя: его удавалось достать из самой программы и файлов на накопителе. В начале э…

✍1

9 Nov 2026, 10:23 UTC≈1,180 views5 reactionsread 10 November 2026
Advertisementerid 2W5zFGDRwj8Photo

Маршрут построен: выбираем свой путь в ИБ Защита или пентест, вендор или интегратор, собственная практика или большая компания — у карьеры в кибербезопасности много сценариев. На public talk от K2 Кибербезопасность: ✅ разберем плюсы и минусы разных карьерных треков ✅ сравним работу в Blue и Red командах ✅ обсудим, как не потеряться среди множества ролей После — попрактикуемся проходить собесы, поедим пиццу и разы…

❤2🔥2💋1

9 Nov 2026, 09:17 UTC≈1,170 views4 reactionsread 10 November 2026
Photo

🖥 Безопасность систем виртуализации: атаки на разных уровнях и последствия ошибок в конфигурации В виртуальных средах инциденты безопасности могут происходить из-за уязвимостей в программном обеспечении, ошибок персонала, небезопасных конфигураций или сочетания этих факторов. Расследование таких инцидентов зачастую выходит за рамки анализа рабочих нагрузок. Гипервизоры, среды выполнения контейнеров, административны…

✍3❤1

8 Nov 2026, 11:25 UTC≈1,320 views2 reactionsread 10 November 2026
Photo

🖥 Выпуск системы мониторинга Zabbix 8.0 Состоялся релиз открытой системы мониторинга Zabbix 8.0, который отнесен к версиям с длительным сроком официальной поддержки (LTS). Zabbix - универсальная система для мониторинга производительности и доступности серверов, инженерного и сетевого оборудования, приложений, баз данных, систем виртуализации, контейнеров, IT-сервисов, web-сервисов и облачной инфраструктуры. Система…

🤔2

7 Nov 2026, 14:31 UTC≈1,380 views2 reactionsread 10 November 2026
Photo

🖥 Как упростить GitLab CI: семь приемов для настройки пайплайна Разберем семь возможностей GitLab CI, доступных без платной подписки, от простого к сложному: начнем с того, как сделать граф пайплайна компактнее, и закончим распределением тестов между параллельными задачами. Пайплайн успешно завершился, несмотря на найденные линтером ошибки. Тесты прошли дважды: для процента покрытия и для XML-отчета завели разные з…

✍2

6 Nov 2026, 08:34 UTC≈1,510 views2 reactionsread 10 November 2026
Photo

🖥 redb Route XML для VS Code: проекты из шаблонов, разметка, граф и диаграммы Mermaid Расширение для VS Code в Marketplace: проект из шаблона, подсказки по схеме, ссылки на бины, дерево и граф маршрутов, Mermaid, путь до воркера Tsak. Интеграционный маршрут в redb.Route можно написать на C#, а можно разметкой: файл .route.xml кладется в пакет, пакет в папку воркера Tsak, и маршрут начинает работать. Формату редакто…

❤1👍1

5 Nov 2026, 18:00 UTC≈1,600 views2 reactionsread 10 November 2026
Photo

🖥 Как развернуть личную IDE в браузере с помощью code-server В свободное время я потихоньку развиваю свою лабораторию. Мне нравятся маломощные и компактные устройства, но проблема заключается в том, что не все рабочие инструменты доступны на таком железе. Я решил погрузиться в вопрос и начал изучать решения, но концепция удаленного доступа к ПК мне не понравилась. Разные операционные системы и платформы сильно огра…

👍2

5 Nov 2026, 14:55 UTC≈1,540 views7 reactionsread 10 November 2026
Photo

🖥 Анализ трафика Wi-Fi в Wireshark. Как найти причину сбоев Телефон может хорошо слышать точку доступа, но ждать свободного эфира, повторять передачи или безрезультатно запрашивать сетевой адрес. Симптомы похожи. Сеть подключена, а страница не открывается. Захват трафика помогает различать причины. Но неподходящий адаптер или слишком строгий фильтр способны создать картину неисправности в работающей сети. Разбере…

✍6❤1

Showing the 12 most recent of 122 posts we hold for @lab_hack. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Posts recorded as deleted after publishing

We recorded 18 posts on @lab_hack 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
10 August 2026
Most recent seen missing
8 November 2026
Median time before seen missing
4 days
Seen missing in the last 30 days
7

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

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

infosec
@it_secur · 63,401
#1
Social Engineering
@Social_engineering · 124,696
#2
Mr. Robot
@elliot_cybersec · 38,923
#3
no system is safe // cybersec
@nsis_cybersec · 21,166
#4
Архив Безопасника
@secure_archive · 10,964
#5
Записки Безопасника
@infosec_globe · 17,894
#6
Open Source
@open_source_friend · 52,669
#7
CyberINS // Лаборатория ИБешника
@cyberins · 11,503
#8
ZeroDay | Кибербезопасность
@cybersec_academy · 42,588
#9
S.E.Reborn
@S_E_Reborn · 22,459
#10
Белый хакер
@bezopasno_soft · 29,601
#11
Не хакинг, а ИБ
@searchack · 18,098
#12
Codeby
@codeby_sec · 37,071
#13
White Hat
@kind_hack · 11,916
#14
SecAtor
@true_secator · 42,194
#15
Похек
@poxek · 17,302
#16
SecurityLab.ru
@SecLabNews · 86,532
#17
infosecurity
@tg_infosec · 26,845
#18
S.E.Book
@S_E_Book · 23,090
#19
Чёрный Треугольник
@black_triangle_tg · 63,957
#20
Life-Hack - Хакер
@haccking · 63,021
#21
Russian OSINT
@Russian_OSINT · 48,508
#22
Бункер Хакера
@book_academ · 21,293
#23
Inf0 | ИБ, OSINT
@info_cybersecurity · 10,792
#24
ИБ Книга | Библиотека ИБ
@itbook_library · 15,938
#25
Cybred
@cybred · 11,435
#26
Арсенал Безопасника
@arsenal_security · 15,040
#27
Хакер — Xakep.RU
@xakep_ru · 40,313
#28
AP Security
@ap_security · 4,248
#29
Project Omega | ИБ
@omega_cybersec · 8,690
#30
APT
@APT_Notes · 17,360
#31
Пакет Безопасности
@package_security · 33,728
#32
Investigation & Forensic TOOLS
@forensictools · 22,609
#33
SHADOW:Group
@shadow_group_tg · 11,456
#34
Библиотека Программиста
@code_library · 17,529
#35
T.Hunter
@tomhunter · 14,174
#36
[PYTHON:TODAY]
@python2day · 63,348
#37
Пост Лукацкого
@alukatsky · 38,431
#38
Архив Программиста
@storage_it · 8,660
#39
Библиотека хакера | Hacking, Infosec, ИБ, информационная безопасность
@hackproglib · 12,612
#40
NetStalkers
@netstalkerscom · 7,805
#41
BI.ZONE
@bizone_channel · 11,609
#42
CyberYozh Academy
@cyberyozh_academy · 15,291
#43
Mycroft Intelligence
@mycroftintel · 20,691
#44
🌳☀️Digital-Разведка & OSINT
@DigitaIIntelligence · 8,762
#45
InfoSec Portal
@cybersecinform · 20,042
#46
Мыслить как безопасник
@artemov_security · 9,211
#47
PulSe
@Pulsechanel · 20,004
#48
INSPECTOR | OSINT
@it_fullstak · 11,072
#49
Kali Linux
@linuxkalii · 55,842
#50
Admin Guides | Сисадмин
@admguides · 12,050
#51
Вакансии в ИБ | infosec
@infosec_work · 16,358
#52
Серверная Админа | Компьютерные сети
@school_network · 26,411
#53
Эксплойт
@exploitex · 2,022,997
#54
PRO:PENTEST
@pro_pentest · 10,223
#55
Управление Уязвимостями и прочее
@avleonovrus · 12,628
#56
Кладовка Pavlu
@KladovkaPavlu · 64,668
#57
Утечки информации
@dataleak · 117,768
#58
Багхантер 2.0
@bughunter_circuit · 18,747
#59
Network Admin
@networkadm · 12,351
#60
Python и 1000 уязвимостей
@osint_pythons · 36,463
#61
Сетевик Джонни // Network Admin
@iscode · 5,748
#62
PyLinux | Всё о Linux & Python
@pylinux0 · 11,049
#63
Bafoмёд OSINT
@osint_san_framework · 9,381
#64
Linux Academy
@linuxacademiya · 28,647
#65
Blue (h/c)at Café
@bh_cat · 4,007
#66
Секреты сисадмина | DevOps, Linux, SRE
@sysadmin_library · 25,723
#67
OSINT Беларусь
@osintby · 8,561
#68
Offensive Xwitter
@OffensiveTwitter · 21,323
#69
GitHub Community
@github · 154,995
#70
Cyber Detective
@cybdetective · 28,012
#71

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

no system is safe // cybersec
@nsis_cybersec · 21,166
Telegram ranks this channel #5 of 71 here — alongside 70 others — read 23 September 2026
Этичный Хакер
@hack_less · 243,065
Telegram ranks this channel #7 of 81 here — alongside 80 others — read 12 August 2026
Mycroft Intelligence
@mycroftintel · 20,691
Telegram ranks this channel #8 of 76 here — alongside 75 others — read 25 September 2026
Бункер Хакера
@book_academ · 21,293
Telegram ranks this channel #10 of 72 here — alongside 71 others — read 23 September 2026
Белый хакер
@bezopasno_soft · 29,601
Telegram ranks this channel #12 of 78 here — alongside 77 others — read 8 September 2026
S.E.Reborn
@S_E_Reborn · 22,459
Telegram ranks this channel #15 of 66 here — alongside 65 others — read 20 September 2026
infosec
@it_secur · 63,401
Telegram ranks this channel #15 of 81 here — alongside 80 others — read 22 August 2026
S.E.Book
@S_E_Book · 23,090
Telegram ranks this channel #17 of 64 here — alongside 63 others — read 19 September 2026
Social Engineering
@Social_engineering · 124,696
Telegram ranks this channel #19 of 82 here — alongside 81 others — read 13 August 2026
infosecurity
@tg_infosec · 26,845
Telegram ranks this channel #28 of 74 here — alongside 73 others — read 11 September 2026
Life-Hack - Хакер
@haccking · 63,021
Telegram ranks this channel #29 of 85 here — alongside 84 others — read 21 August 2026
Task No Face
@TaskNoFace · 28,996
Telegram ranks this channel #34 of 78 here — alongside 77 others — read 8 September 2026
Чёрный Треугольник
@black_triangle_tg · 63,957
Telegram ranks this channel #37 of 87 here — alongside 86 others — read 21 August 2026
CyberYozh
@cyberyozh_official · 62,555
Telegram ranks this channel #38 of 81 here — alongside 80 others — read 21 August 2026
Серверная Админа | Компьютерные сети
@school_network · 26,411
Telegram ranks this channel #54 of 85 here — alongside 84 others — read 12 September 2026
CMD | IT
@cmd_it · 24,075
Telegram ranks this channel #55 of 82 here — alongside 81 others — read 16 September 2026
[PYTHON:TODAY]
@python2day · 63,348
Telegram ranks this channel #60 of 91 here — alongside 90 others — read 21 August 2026
Linux Academy
@linuxacademiya · 28,647
Telegram ranks this channel #67 of 84 here — alongside 83 others — read 9 September 2026
Секреты сисадмина | DevOps, Linux, SRE
@sysadmin_library · 25,723
Telegram ranks this channel #75 of 85 here — alongside 84 others — read 13 September 2026
CyberYozh AI Security
@CyberYozh_AI_security · 26,008
Telegram ranks this channel #79 of 91 here — alongside 90 others — read 12 September 2026

This channel appears in 20 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 10 November 2026 — this entry's latest reading, not the date you are reading this.

“Лаборатория хакера” (@lab_hack), 25,423 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/lab_hack.

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.