Telegram RegisterThe public register of Telegram
Telegram profile photo for Life-Hack - Хакер

Channel

Life-Hack - Хакер

@haccking

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

63,203subscribers

-80 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1001071752104
TypeChannel
Username@haccking
DescriptionСообщество по информационной безопасности (кибербезопасности). Статьи, гайды, обучения, рекомендации, обзоры, новости, подборки полезного софта! #linux #pentest #hack @LifeHackmedia РКН: https://clck.ru/3GLmbM Связь - @adm1nLH
Created3 March 2017 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live17 September 2026
Measurements held32
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/haccking

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 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.

Previous handles

Recorded in 2019 as “Life-Hack [Жизнь-Взлом]/Хакинг” — the title held for this same channel (matched by Telegram id, not by handle) in the Pushshift Telegram Dataset, a third-party archive captured in 2019-2020, years before this register made its own first observation. CC BY 4.0, Baumgartner, Zannettou, Squire & Blackburn (2020), Zenodo. A third party’s dated snapshot, not a measurement this register made itself.

Growth

63,18663,28363,234.55 August 2026 — 63,283 subscribers6 August 2026 — 63,283 subscribers7 August 2026 — 63,265 subscribers8 August 2026 — 63,258 subscribers9 August 2026 — 63,257 subscribers10 August 2026 — 63,245 subscribers11 August 2026 — 63,249 subscribers12 August 2026 — 63,241 subscribers13 August 2026 — 63,244 subscribers14 August 2026 — 63,234 subscribers16 August 2026 — 63,223 subscribers17 August 2026 — 63,211 subscribers18 August 2026 — 63,208 subscribers19 August 2026 — 63,206 subscribers20 August 2026 — 63,202 subscribers21 August 2026 — 63,208 subscribers25 August 2026 — 63,218 subscribers26 August 2026 — 63,209 subscribers27 August 2026 — 63,215 subscribers28 August 2026 — 63,219 subscribers29 August 2026 — 63,217 subscribers30 August 2026 — 63,214 subscribers31 August 2026 — 63,201 subscribers1 September 2026 — 63,203 subscribers2 September 2026 — 63,207 subscribers3 September 2026 — 63,213 subscribers6 September 2026 — 63,216 subscribers9 September 2026 — 63,201 subscribers12 September 2026 — 63,186 subscribers13 September 2026 — 63,198 subscribers15 September 2026 — 63,209 subscribers17 September 2026 — 63,203 subscribers63,2035 August 202617 September 2026
32 measurements spanning 43 days, net -80. 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 63,171–63,298 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 32
Measured (UTC)SubscribersChange
17 Sept 2026, 19:1963,203-6
15 Sept 2026, 15:3863,209+11
13 Sept 2026, 21:1863,198+12
12 Sept 2026, 00:5863,186-15
9 Sept 2026, 14:0163,201-15
6 Sept 2026, 09:5563,216+3
3 Sept 2026, 23:5863,213+6
2 Sept 2026, 15:5863,207+4
1 Sept 2026, 14:5563,203+2
31 Aug 2026, 11:2863,201-13
30 Aug 2026, 09:4363,214-3
29 Aug 2026, 06:4663,217-2
28 Aug 2026, 03:4763,219+4
27 Aug 2026, 00:5863,215+6
26 Aug 2026, 00:1463,209-9
25 Aug 2026, 01:1563,218+10
21 Aug 2026, 22:1763,208+6
20 Aug 2026, 14:4563,202-4
19 Aug 2026, 15:4963,206-2
18 Aug 2026, 14:0463,208first reading

Engagement

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

ERR · 30 days
6.78%
avg views ÷ 63,203 subscribers
Avg views / post
4,290
72 posts measured
Reaction rate
0.339%
reactions ÷ views · ER floor
Posts in window
72
of 141 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 26 September 2026
Posts held141 (28 July 2026 – 26 September 2026)
Views total308,700
Reactions total1,048
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken26 Sept 2026, 19:02 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,530
Videos
≈92
Links
≈9,140

Lifetime counters from Telegram’s own channel header, read 26 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.

Reaction mix

2,053 reactions across 137 posts, in 16 distinct kinds. The most used accounts for 32.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍67632.9%
🔥65031.7%
❤55326.9%
🤣874.24%
😁321.56%
🤝110.536%
🤔100.487%
👌70.341%
✍60.292%
🤓50.244%
👏40.195%
👾40.195%
🏆30.146%
🫡30.146%
😈10.049%
🤗10.049%

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

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

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @haccking. 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 141 most recent posts we hold for this entry, published 28 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
3.55%
5 of 141 posts carry an ad marker
Regulatory tokens
2
posts carrying an erid · 2 distinct tokens
Median views · ads
4,110
over 5 measured posts
Median views · rest
4,320
over 136 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
2VtzqvcD3eC122 September 202622 September 2026
2W5zFGNzvqP123 September 202623 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 141 most recent posts we hold, published 28 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, 13:01 UTC≈1,240 views5 reactionsread 26 September 2026
Photo

Анализ глубинных интервью с помощью нейросетей: от транскрипта к продуктовым инсайтам #статья #ai После серии глубинных интервью начинается самая сложная часть исследования — анализ. Нужно перечитать десятки страниц транскриптов, найти темы, выделить важные цитаты и понять, что на самом деле стоит за словами пользователей. Сегодня часть этой работы можно поручить нейросетям. Разберем, как ИИ помогает анализировать …

👍3❤1🔥1

26 Sept 2026, 08:05 UTC≈1,700 views8 reactionsread 26 September 2026
Photo

OpenAEV #redteam #blueteam Open source платформа для планирования и проведения adversarial simulation кампаний - от технического уровня до стратегического. Внутри управление сценариями, командами, мониторинг учений в реальном времени, статистика и gap-анализ. И главное - интеграция с OpenCTI: строишь учения под актуальный threat landscape, а не абстрактные техники из головы. Ссылка на GitHub LH | News | OSINT | A…

🔥5👍2❤1

25 Sept 2026, 17:00 UTC≈2,270 views26 reactionsread 26 September 2026

Чтобы не потерять связь, подпишись на канал!

🤣15🤔4👌2🤓2🏆1👍1😁1

25 Sept 2026, 13:02 UTC≈2,690 views13 reactionsread 26 September 2026
Photo

Как я год проработал на Arch Linux, сдался и вернулся на скучную Ubuntu для реальной работы #статья #Linux #admin Весь мой путь в Linux начался в студенческие годы, в момент, когда я получил предложение о работе от своего преподавателя в универе. Оказалось, что помимо преподавательской работы он также трудился в IT-компании, которая на тот момент искала интернов. Собеседование заняло 10 минут, без единого вопроса …

🔥5👍3🤓3❤2

25 Sept 2026, 08:03 UTC≈2,870 views12 reactions1 Starread 26 September 2026
Photo

CVE MCP Server #ai #cve MCP-сервер который позволяет AI-ассистентам получать актуальную информацию об уязвимостях по идентификатору CVE. Инструмент обращается к базе MITRE и возвращает описание уязвимости, что упрощает анализ инцидентов, triage и исследование угроз. Ссылка на GitHub LH | News | OSINT | AI

👍8❤2🔥2

24 Sept 2026, 13:05 UTC≈3,200 views10 reactionsread 26 September 2026
Photo

Как устроены хранилища Kubernetes: разбор для начинающего сисадмина #статья #k8s #devops #admin Управление данными в Kubernetes часто кажется сложным. Если грамотно не подключить внешнее хранилище, то при любом перезапуске пода все накопленные файлы бесследно исчезнут. Этот материал — практическое руководство для тех, кто только осваивает администрирование K8s и хочет разобраться в логике работы дисков без погружен…

🔥6❤3👍1

24 Sept 2026, 08:04 UTC≈3,100 views13 reactionsread 26 September 2026
Photo

Panjiva #OSINT Ресурс по международной торговле и цепочкам поставок. Помогает искать поставщиков, производителей, покупателей и отслеживать импортно-экспортные связи по компаниям и товарам. Ссылка на сервис LH | News | OSINT | AI

🔥8❤3👍2

23 Sept 2026, 13:10 UTC≈3,290 views12 reactionsread 26 September 2026
Photo

UNIX-команды macOS, которых нет в Linux: от say и defaults до sysadminctl #статья #Linux #macOS macOS — сертифицированная UNIX система (формально — UNIX 03), и большая часть того, что набираешь в терминале, ведет себя, как в любом BSD: ls, grep, ps, ssh — все на месте. Но рядом лежит второй слой команд, которого нет ни в одном дистрибутиве Linux и нет в POSIX: defaults, sysadminctl, mdfind, say, afplay. Часть из н…

👍8🔥3❤1

23 Sept 2026, 12:02 UTC≈2,920 views7 reactionsread 26 September 2026
Advertisementerid 2W5zFGNzvqPPhoto

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

👍4❤2🫡1

23 Sept 2026, 08:05 UTC≈2,970 views7 reactionsread 26 September 2026
Photo

HacksGuard #malware #dfir #soc Open-source инструмент на Rust для статического анализа PE-файлов. Терминальный дашборд для SOC и реверсеров с целью быстрой оценки сэмпла, до того как тащить его в IDA/Ghidra. Risk Score 0-100% по 5 эвристикам с radar-графиком. Deep PE inspection: секции, импорты по severity, митигации, Authenticode. Граф энтропии. Overlay detection и авто-декод строк (IP, URL, Base64). JSON-режим дл…

👍3🔥3❤1

22 Sept 2026, 13:10 UTC≈3,510 views16 reactionsread 26 September 2026
Photo

Записал, с кем разговаривают восемь приборов в моей квартире #статья #полезное #spy Телевизор я включал один раз, утром, минут на десять. Потом выключил пультом и больше не трогал. За следующие сутки он обратился к 172 разным доменам — среди них компания, которая занимается распознаванием картинки на экране. Нашёл я это не специально. Просто включил на домашнем роутере файловый журнал DNS-запросов и оставил на вых…

❤8👍6🔥2

22 Sept 2026, 12:01 UTC≈3,210 views6 reactionsread 26 September 2026
Advertisementerid 2VtzqvcD3eCPhoto

Привет, это Николай Арефьев, основатель CyberThreatTech! Мы в CyberThreatTech запускаем новую главу — и хотим показать её вам первыми. 30 сентября в Москвариуме (зал «Море музыки») мы проводим закрытое мероприятие «Океан данных: Погружение в Озеро знаний» — и мыбыли бы рады видеть Вас среди гостей. Почему именно это событие и почему вы? Мы не делаем очередную презентацию – хотим погрузитьгостей в атмосферу Озера з…

👍3🔥2❤1

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

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 9 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.

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.

Social Engineering
@Social_engineering · 125,008
#1
SecurityLab.ru
@SecLabNews · 84,654
#2
Codeby
@codeby_sec · 37,041
#3
Этичный Хакер
@hack_less · 229,400
#4
infosec
@it_secur · 61,761
#5
Похек
@poxek · 16,849
#6
S.E.Reborn
@S_E_Reborn · 22,374
#7
Хакер — Xakep.RU
@xakep_ru · 39,610
#8
Hacker News
@HNews · 7,293
#9
Пост Лукацкого
@alukatsky · 37,862
#10
Cybred
@cybred · 11,118
#11
Mr. Robot
@elliot_cybersec · 38,917
#12
Мамкин ITшник / IT Юмор / Мемы
@ithumorlol · 2,205
#13
Архив Безопасника
@secure_archive · 10,833
#14
Open Source
@open_source_friend · 52,304
#15
infosecurity
@tg_infosec · 26,779
#16
APT
@APT_Notes · 16,685
#17
Интернет-Розыск
@irozysk · 45,953
#18
S.E.Book
@S_E_Book · 23,146
#19
BI.ZONE
@bizone_channel · 11,212
#20
Inside
@in51d3 · 7,996
#21
Управление Уязвимостями и прочее
@avleonovrus · 12,122
#22
Kali Linux
@linuxkalii · 55,412
#23
no system is safe // cybersec
@nsis_cybersec · 21,518
#24
YAH
@YAH_Channel · 7,569
#25
Записки Безопасника
@infosec_globe · 18,120
#26
Investigation & Forensic TOOLS
@forensictools · 22,417
#27
IT курсы / Программирование / ИИ / ИБ
@hacckingbook · 11,934
#28
Лаборатория хакера
@lab_hack · 25,556
#29
Белый хакер
@bezopasno_soft · 29,706
#30
k8s (in)security
@k8security · 13,151
#31
SHADOW:Group
@shadow_group_tg · 11,482
#32
AM Live
@anti_malware · 13,154
#33
BI.ZONE Bug Bounty
@bizone_bugbounty · 6,604
#34
ZeroDay | Кибербезопасность
@cybersec_academy · 42,838
#35
SecuriXy.kz
@securixy_kz · 10,202
#36
Positive Technologies
@Positive_Technologies · 29,062
#37
Mobile AppSec World
@mobile_appsec_world · 8,343
#38
PurpleBear
@purple_medved · 4,627
#39
Не хакинг, а ИБ
@searchack · 18,244
#40
PRO:PENTEST
@pro_pentest · 10,096
#41
CyberYozh Academy
@cyberyozh_academy · 15,399
#42
PWN AI
@pwnai · 7,283
#43
IT и безопасность
@tg_security · 26,560
#44
CyberINS // Лаборатория ИБешника
@cyberins · 11,451
#45
Пакет Безопасности
@package_security · 33,011
#46
Admin Guides | Сисадмин
@admguides · 11,942
#47
Хабр
@habr_com · 132,465
#48
ESCalator
@ptescalator · 8,127
#49
Blue (h/c)at Café
@bh_cat · 3,968
#50
НеКасперский
@NeKaspersky · 16,061
#51
Не баг, а фича
@bugfeature · 571,363
#52
IT MEGA облако
@it_mega_disk · 11,350
#53
КИБЕР МЕДИА
@secmedia · 5,902
#54
Бункер Хакера
@book_academ · 21,429
#55
Борьба с киберпреступностью | F6
@f6_cybersecurity · 22,318
#56
Just Security
@justsecurity · 3,630
#57
Библиотека хакера | Hacking, Infosec, ИБ, информационная безопасность
@hackproglib · 12,705
#58
Секреты сисадмина | DevOps, Linux, SRE
@sysadmin_library · 25,649
#59
Inf0 | ИБ, OSINT
@info_cybersecurity · 10,238
#60
Bounty On Coffee
@BountyOnCoffee · 4,763
#61
PT SWARM
@ptswarm · 7,502
#62
SecAtor
@true_secator · 41,748
#63
Утечки информации
@dataleak · 119,401
#64
CyberYozh
@cyberyozh_official · 62,701
#65
OFFZONE
@offzone_moscow · 7,400
#66
Эксплойт
@exploitex · 2,048,279
#67
Russian OSINT
@Russian_OSINT · 47,701
#68
Двач
@dvachannel · 938,773
#69
Чёрный Треугольник
@black_triangle_tg · 63,850
#70
Багхантер
@bughunter_circuit · 3,514
#71
RuSecJobs Channel
@RuSecJobs · 11,322
#72
Standoff 365
@standoff_365 · 8,268
#73
Вакансии в ИБ | infosec
@infosec_work · 15,755
#74
Бэкдор
@whackdoor · 1,603,481
#75
STEIN: ИБ, OSINT
@secur_researcher · 14,257
#76
БДУ ФСТЭК России
@bdufstecru · 10,589
#77
T.Hunter
@tomhunter · 14,234
#78
Bafoмёд OSINT
@osint_san_framework · 8,984
#79
Offensive Xwitter
@OffensiveTwitter · 21,041
#80
Information Security Memes
@infosecmemes · 9,677
#81
Информация опасносте
@alexmakus · 18,782
#82
GitHub Community
@github · 155,991
#83
Код.ру
@d_code · 406,147
#84
vx-underground
@vxunderground · 52,032
#85

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

CYBER HUNTER - Кибербезопасность
@cyberbezopasno · 53,341
Telegram ranks this channel #2 of 50 here — alongside 49 others — read 26 August 2026
IT и безопасность
@tg_security · 26,560
Telegram ranks this channel #5 of 91 here — alongside 90 others — read 12 September 2026
Кладовка Pavlu
@KladovkaPavlu · 65,054
Telegram ranks this channel #5 of 76 here — alongside 75 others — read 4 September 2026
LAMERLAND - overbafer1
@overlamer1 · 81,379
Telegram ranks this channel #6 of 85 here — alongside 84 others — read 18 August 2026
Codeby
@codeby_sec · 37,041
Telegram ranks this channel #7 of 76 here — alongside 75 others — read 1 September 2026
TechNews
@techlucker · 43,532
Telegram ranks this channel #7 of 79 here — alongside 78 others — read 28 August 2026
Mr. Robot
@elliot_cybersec · 38,917
Telegram ranks this channel #8 of 70 here — alongside 69 others — read 31 August 2026
Open Source
@open_source_friend · 52,304
Telegram ranks this channel #9 of 87 here — alongside 86 others — read 24 August 2026
Этичный Хакер
@hack_less · 229,400
Telegram ranks this channel #9 of 81 here — alongside 80 others — read 12 August 2026
S.E.Book
@S_E_Book · 23,146
Telegram ranks this channel #10 of 64 here — alongside 63 others — read 19 September 2026
Kali Linux
@linuxkalii · 55,412
Telegram ranks this channel #10 of 89 here — alongside 88 others — read 23 August 2026
Termux, please
@termuxplz0x41 · 32,722
Telegram ranks this channel #12 of 54 here — alongside 53 others — read 4 September 2026
S.E.Reborn
@S_E_Reborn · 22,374
Telegram ranks this channel #13 of 66 here — alongside 65 others — read 20 September 2026
Хакер — Xakep.RU
@xakep_ru · 39,610
Telegram ranks this channel #13 of 83 here — alongside 82 others — read 30 August 2026
Social Engineering
@Social_engineering · 125,008
Telegram ranks this channel #14 of 82 here — alongside 81 others — read 13 August 2026
Отдел К: IT-технологии, кибербезопасность
@cyber_cabb · 81,637
Telegram ranks this channel #15 of 94 here — alongside 93 others — read 18 August 2026
Бункер Хакера
@book_academ · 21,429
Telegram ranks this channel #17 of 72 here — alongside 71 others — read 23 September 2026
infosec
@it_secur · 61,761
Telegram ranks this channel #17 of 81 here — alongside 80 others — read 22 August 2026
SecurityLab.ru
@SecLabNews · 84,654
Telegram ranks this channel #17 of 90 here — alongside 89 others — read 18 August 2026
ZeroDay | Кибербезопасность
@cybersec_academy · 42,838
Telegram ranks this channel #18 of 70 here — alongside 69 others — read 29 August 2026
no system is safe // cybersec
@nsis_cybersec · 21,518
Telegram ranks this channel #20 of 71 here — alongside 70 others — read 23 September 2026
Investigation & Forensic TOOLS
@forensictools · 22,417
Telegram ranks this channel #20 of 74 here — alongside 73 others — read 20 September 2026
infosecurity
@tg_infosec · 26,779
Telegram ranks this channel #20 of 74 here — alongside 73 others — read 11 September 2026
Белый хакер
@bezopasno_soft · 29,706
Telegram ranks this channel #20 of 78 here — alongside 77 others — read 8 September 2026

This channel appears in 53 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.

“Life-Hack - Хакер” (@haccking), 63,203 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/haccking.

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.