Telegram RegisterThe public register of Telegram
Telegram profile photo for Этичный Хакер

Channel

Этичный Хакер

@hack_less

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Advertising · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry

242,543subscribers

+16,234 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001479815768
TypeChannel
Username@hack_less
DescriptionПро кибербезопасность и современные технологии. Сотрудничество, реклама: @workhouse_price Канал в реестре РКН: https://clck.ru/3FzjLS Сотрудничаем с @Spiral_Yuri, https://telega.in/c/hack_less Мы в Max: https://max.ru/hack_less
Created30 June 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live15 November 2026
Measurements held65
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/hack_less

Topic

Hacking & security — 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 8 August 2026 and assigned it the closest of 31 fixed categories, at 67% 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

226,166247,916237,041242,5436 August 202615 November 2026
65 measurements spanning 101 days, net +16,234. 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 222,904–251,179 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)SubscribersChange
15 Nov 2026, 17:55242,543-517
12 Nov 2026, 10:01243,060-5
10 Nov 2026, 06:45243,065+112
8 Nov 2026, 18:28242,953-262
7 Nov 2026, 09:05243,215-160
6 Nov 2026, 09:56243,375-305
5 Nov 2026, 07:19243,680-295
4 Nov 2026, 06:15243,975-220
3 Nov 2026, 06:36244,195-32
2 Nov 2026, 04:28244,227-470
1 Nov 2026, 01:28244,697+256
31 Oct 2026, 03:06244,441+266
30 Oct 2026, 02:21244,175-41
29 Oct 2026, 03:50244,216-274
28 Oct 2026, 02:20244,490-145
27 Oct 2026, 00:58244,635-619
26 Oct 2026, 03:16245,254-256
25 Oct 2026, 00:36245,510-401
24 Oct 2026, 02:18245,911-359
23 Oct 2026, 01:46246,270first reading

Engagement

569 posts held, back to 2 August 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 217 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
2.72%
avg views ÷ 242,543 subscribers
Avg views / post
6,610
162 posts measured
Reaction rate
0.875%
reactions ÷ views · ER floor
Posts in window
162
of 569 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 16 November 2026
Posts held569 (2 August 2026 – 16 November 2026)
Views total1,070,220
Reactions total9,368
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Nov 2026, 23:57 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
≈4,550
Videos
≈544
Links
≈4,520

Lifetime counters from Telegram’s own channel header, read 16 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
56m 27s
Average length
1m 27s

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

32,359 reactions across 569 posts, in 11 distinct kinds. The most used accounts for 49.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁15,96349.3%
❤4,49713.9%
🤯2,7958.64%
😭2,2016.80%
🔥1,8725.79%
👏1,7295.34%
👍1,3564.19%
🤔9342.89%
😱5631.74%
🕊4151.28%
🥰340.105%

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

Measured over the 569 most recent posts we hold, published 2 August 2026 to 16 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.

Telegram Stars

Stars received
37
across the posts below
Posts paid on
32
of 569 we hold a reading for · 6%
Most on one post
3
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @hack_less. 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 569 most recent posts we hold for this entry, published 2 August 2026 to 16 November 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
0.879%
5 of 569 posts carry an ad marker
Regulatory tokens
5
posts carrying an erid · 5 distinct tokens
Median views · ads
6,520
over 5 measured posts
Median views · rest
6,630
over 564 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
2VSb5xDMALr110 August 202610 August 2026
2Vtzqv3tUJ8125 September 202625 September 2026
2VtzqxakEJJ19 November 20269 November 2026
2W5zFH5wtrE12 November 20262 November 2026
2W5zFJepnwj129 September 202629 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 569 most recent posts we hold, published 2 August 2026 to 16 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: 4 of 162 posts held from the last 30 days (2.47%) 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).

16 Nov 2026, 20:17 UTC≈2,320 views28 reactionsread 16 November 2026
Photo

😳 На GitHub нашли тысячи секретов, утекших через настройки Claude Code ❗️ Исследователи обнаружили на GitHub 104 185 копий .claude/settings.local.json в 103 617 публичных репозиториях. В 1122 изученных файлах содержался как минимум один секрет, а в общей сложности исследователи насчитали 1379 уникальных секретов Среди них: 398 токенов API, 379 паролей от баз данных, 43 набора учетных данных для подключения по SSH …

😁21👏3❤2🤯2

16 Nov 2026, 17:15 UTC≈3,630 views22 reactionsread 16 November 2026
Photo

🤔 Специалисты нашли в сети данные обращений пользователей в поддержку Telegram — Аналитики предупреждают, что обнаружили базу с персональными данными и текстами обращений пользователей в поддержку Telegram за 2025 год По версии исследователей, наиболее вероятный источник утечки — злоупотребление доступом со стороны волонтеров службы поддержки Особенность Telegram заключается в том, что такие запросы обрабатывают …

😭13😁5🕊3❤1

16 Nov 2026, 14:47 UTC≈4,150 views28 reactionsread 16 November 2026
Photo

😈 83 навыка, которые превращают Claude в охотника за багами Claude BugHunter — это готовый набор навыков (skills) для Claude Code, который ставится одной командой и меняет поведение ассистента — 83 навыка, 15 slash-команд, 681 паттерн, вытащенный из раскрытых отчётов HackerOne и разложенный по 24 классам уязвимостей После установки нейронка начинает вести себя так, будто за плечами много реальных проектов: знает …

🔥17❤7😭3😁1

16 Nov 2026, 11:35 UTC≈4,960 views53 reactionsread 16 November 2026
Photo

⛔️ Иордания заблокировала мессенджер Telegram на территории страны — В заявлении Управления общественной безопасности королевства указывается, что мессенджер может использоваться для киберпреступлений, угроз, вымогательства и распространения запрещенного контента, включая экстремистские материалы, угрожающие общественной безопасности и национальной стабильности Сейчас мессенджер уже заблокирован в Иордании, Иране,…

🤯32😁12❤4👍3🕊2

16 Nov 2026, 09:32 UTC≈4,920 views17 reactionsread 16 November 2026
Photo

👋 Кое-что интересное для тех, кто занимается ИБ Мы регулярно делимся инструментами, исследованиями и разборами атак. Но иногда полезно послушать и тех, кто ежедневно занимается защитой реальной инфраструктуры Поэтому решили напомнить про ICEBREAKER 2026 — ежегодную онлайн-конференцию NGENIX, которая пройдёт 9 декабря В программе DDoS, безопасность веб-приложений и API, защита от ботов, ИИ-краулеры и мониторинг инф…

❤13👍4

16 Nov 2026, 07:30 UTC≈4,990 views108 reactionsread 16 November 2026
Photo

ИИ-реклама заполонила уже весь интернет. 🧑‍💻 Этичный хакер

😁90❤12👏6

15 Nov 2026, 18:52 UTC≈5,860 views36 reactionsread 16 November 2026
Photo

🧑‍🎓 Книга: Хакинг API — взлом программных интерфейсов веб-приложений Хакинг API — это экспресс-курс по тестированию безопасности веб-API Здесь вы узнаете, как взламывать API, искать уязвимости, которые часто упускают даже опытные специалисты, и обеспечивать безопасность ваших собственных АРІ В этом практическом руководстве вы: — Сначала разберетесь, как на самом деле работают REST API и какие уязвимости для них н…

❤19😭9👍5😁3

15 Nov 2026, 15:29 UTC≈6,000 views54 reactionsread 16 November 2026
Photo

😈 Утечка данных 46 млн испанцев: хакер продает архив 80 ГБ — На теневом форуме пользователь с ником spain выставил на продажу архив объёмом около 80 ГБ. Продавец утверждает, что внутри данные примерно 46,3 миллиона жителей Испании, то есть почти всей страны В описании фигурируют: полные имена, номера национальных удостоверений (DNI и NIE), даты рождения, адреса, гражданство и история регистрации по месту жительств…

🤯32❤9👍7🔥3🕊1🤔1😁1

15 Nov 2026, 12:40 UTC≈8,300 views24 reactionsread 16 November 2026
Photo

😈 Исследователи обошли песочницу Codex и вытащили токены GitHub прямо из памяти Специалисты обнаружили опасную цепочку уязвимостей, которая потенциально позволяла скомпрометировать официальный npm-пакет @openai/codex, скачиваемый миллионы раз в месяц ❗️ Для начала атаки было достаточно создать Issue в репозитории OpenAI на GitHub — его содержимое автоматически передавалось ИИ-агенту Codex, которому можно было навя…

🔥9❤7😁7👏1

15 Nov 2026, 09:51 UTC≈5,800 views23 reactionsread 16 November 2026
Photo

😈 Сверло, скрепка и пинцет. Как прошивали консоли до того, как это стали делать нейросети Сегодня энтузиасты пытаются использовать нейросети для взлома Nintendo Switch 2 и переноса её игр на ПК. Но раньше хакерам приходилось проявлять куда больше изобретательности — Сегодня вспомним самые необычные способы обхода защиты игровых приставок, которые использовали задолго до нейросетей, автоматизированного реверс-инжин…

🔥17😁3❤2👏1

15 Nov 2026, 07:03 UTC≈5,830 views82 reactionsread 16 November 2026
Photo

Проблеск AGI.. 🧑‍💻 Этичный хакер

😁70❤7👍5

14 Nov 2026, 20:58 UTC≈7,400 views109 reactionsread 16 November 2026
Video

😈 CS2 взломали с помощью Fable 5.2 — ютубер всего за $20 расковырял файлы игры и собрал готовый чит с воллхаком и аимботом Автор использовал социальную инженерию и REA (Reverse Engineer Anything) — инструмент для автоматизации реверс-инжиниринга с помощью ИИ Он попросил Claude не создать чит, а «исправить странный баг, из-за которого он не видит игроков через стены» А когда Клод наотрез отказывался — к работе подк…

😁93❤8🕊5🔥3

Showing the 12 most recent of 569 posts we hold for @hack_less. 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 10 posts on @hack_less 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
15 August 2026
Most recent seen missing
12 November 2026
Median time before seen missing
2 days
Seen missing in the last 30 days
2

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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 18 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 · 124,636
#1
infosec
@it_secur · 63,564
#2
Mr. Robot
@elliot_cybersec · 38,872
#3
Архив Безопасника
@secure_archive · 10,948
#4
SecurityLab.ru
@SecLabNews · 86,623
#5
CyberYozh
@cyberyozh_official · 62,660
#6
Лаборатория хакера
@lab_hack · 25,374
#7
Codeby
@codeby_sec · 37,076
#8
Life-Hack - Хакер
@haccking · 62,998
#9
SecAtor
@true_secator · 42,222
#10
S.E.Reborn
@S_E_Reborn · 22,441
#11
no system is safe // cybersec
@nsis_cybersec · 21,091
#12
Чёрный Треугольник
@black_triangle_tg · 63,966
#13
Не хакинг, а ИБ
@searchack · 18,054
#14
Записки Безопасника
@infosec_globe · 17,879
#15
infosecurity
@tg_infosec · 26,828
#16
Похек
@poxek · 17,327
#17
Хакер — Xakep.RU
@xakep_ru · 40,322
#18
Эксплойт
@exploitex · 2,020,421
#19
ZeroDay | Кибербезопасность
@cybersec_academy · 42,559
#20
Белый хакер
@bezopasno_soft · 29,580
#21
CyberINS // Лаборатория ИБешника
@cyberins · 11,489
#22
Russian OSINT
@Russian_OSINT · 48,526
#23
STEIN: ИБ, OSINT
@secur_researcher · 14,154
#24
White Hat
@kind_hack · 11,901
#25
Интернет-Розыск
@irozysk · 45,699
#26
Вакансии в ИБ | infosec
@infosec_work · 16,381
#27
S.E.Book
@S_E_Book · 23,075
#28
[PYTHON:TODAY]
@python2day · 63,301
#29
Пост Лукацкого
@alukatsky · 38,486
#30
Бункер Хакера
@book_academ · 21,292
#31
ИБ Книга | Библиотека ИБ
@itbook_library · 15,910
#32
Admin Guides | Сисадмин
@admguides · 12,043
#33
Бэкдор
@whackdoor · 1,531,148
#34
Серверная Админа | Компьютерные сети
@school_network · 26,381
#35
Positive Technologies
@Positive_Technologies · 29,648
#36
Cybred
@cybred · 11,636
#37
BI.ZONE
@bizone_channel · 11,635
#38
Inf0 | ИБ, OSINT
@info_cybersecurity · 10,813
#39
Библиотека Программиста
@code_library · 17,541
#40
APT
@APT_Notes · 17,432
#41
Пакет Безопасности
@package_security · 34,225
#42
T.Hunter
@tomhunter · 14,164
#43
Investigation & Forensic TOOLS
@forensictools · 22,620
#44
NetStalkers
@netstalkerscom · 7,796
#45
YAH
@YAH_Channel · 7,638
#46
OSINT | Форензика
@osintkanal · 14,110
#47
Библиотека разведчика | Osint | Книги | Курсы
@books_osint · 25,870
#48
IT MEGA облако
@it_mega_disk · 11,416
#49
Project Omega | ИБ
@omega_cybersec · 8,657
#50
AP Security
@ap_security · 4,236
#51
Network Admin
@networkadm · 12,348
#52
Не баг, а фича
@bugfeature · 550,064
#53
Арсенал Безопасника
@arsenal_security · 15,022
#54
PyLinux | Всё о Linux & Python
@pylinux0 · 11,043
#55
DevOps School | Linux, InfoSec, ИБ
@devops_sc · 14,792
#56
CodeCamp
@codecamp · 177,363
#57
Хабр
@habr_com · 134,799
#58
Порвали два трояна
@kasperskyb2b · 9,480
#59
Bafoмёд OSINT
@osint_san_framework · 9,420
#60
КИБЕР МЕДИА
@secmedia · 6,082
#61
PulSe
@Pulsechanel · 20,012
#62
Programmer & IT Memes
@itmemes · 121,858
#63
Мыслить как безопасник
@artemov_security · 9,315
#64
Open Source
@open_source_friend · 52,704
#65
Утечки информации
@dataleak · 117,550
#66
Kali Linux
@linuxkalii · 55,893
#67
Багхантер 2.0
@bughunter_circuit · 18,638
#68
PRO:PENTEST
@pro_pentest · 10,217
#69
LAMERLAND - overbafer1
@overlamer1 · 81,204
#70
Python и 1000 уязвимостей
@osint_pythons · 36,452
#71
Управление Уязвимостями и прочее
@avleonovrus · 12,653
#72
SHADOW:Group
@shadow_group_tg · 11,468
#73
GitHub Community
@github · 155,088
#74
NN
@naebnet · 2,174,384
#75
BI.ZONE Bug Bounty
@bizone_bugbounty · 6,735
#76
RuSecJobs Channel
@RuSecJobs · 11,632
#77
Сетевик Джонни // Network Admin
@iscode · 5,733
#78
Information Security Memes
@infosecmemes · 9,619
#79
Секреты сисадмина | DevOps, Linux, SRE
@sysadmin_library · 25,674
#80
Offensive Xwitter
@OffensiveTwitter · 21,343
#81

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

CyberYozh
@cyberyozh_official · 62,660
Telegram ranks this channel #2 of 81 here — alongside 80 others — read 21 August 2026
Social Engineering
@Social_engineering · 124,636
Telegram ranks this channel #2 of 82 here — alongside 81 others — read 13 August 2026
infosec
@it_secur · 63,564
Telegram ranks this channel #4 of 81 here — alongside 80 others — read 22 August 2026
Life-Hack - Хакер
@haccking · 62,998
Telegram ranks this channel #4 of 85 here — alongside 84 others — read 21 August 2026
CYBER HUNTER - Кибербезопасность
@cyberbezopasno · 58,496
Telegram ranks this channel #5 of 50 here — alongside 49 others — read 26 August 2026
🕵️ Telescan вещает
@tele_scan · 99,873
Telegram ranks this channel #6 of 54 here — alongside 53 others — read 21 August 2026
Чёрный Треугольник
@black_triangle_tg · 63,966
Telegram ranks this channel #7 of 87 here — alongside 86 others — read 21 August 2026
overbafer1
@overbafer1 · 63,372
Telegram ranks this channel #11 of 84 here — alongside 83 others — read 21 August 2026
Отдел К: IT-технологии, кибербезопасность
@cyber_cabb · 81,735
Telegram ranks this channel #11 of 94 here — alongside 93 others — read 18 August 2026
Троянский конь | IT, технологии
@trojan_anonym · 63,803
Telegram ranks this channel #12 of 82 here — alongside 81 others — read 21 August 2026
Интернет-Розыск
@irozysk · 45,699
Telegram ranks this channel #15 of 79 here — alongside 78 others — read 27 August 2026
[PYTHON:TODAY]
@python2day · 63,301
Telegram ranks this channel #15 of 91 here — alongside 90 others — read 21 August 2026
Russian OSINT
@Russian_OSINT · 48,526
Telegram ranks this channel #16 of 82 here — alongside 81 others — read 26 August 2026
SecurityLab.ru
@SecLabNews · 86,623
Telegram ranks this channel #16 of 90 here — alongside 89 others — read 18 August 2026
LAMERLAND - overbafer1
@overlamer1 · 81,204
Telegram ranks this channel #20 of 85 here — alongside 84 others — read 18 August 2026
Open Source
@open_source_friend · 52,704
Telegram ranks this channel #26 of 87 here — alongside 86 others — read 24 August 2026
TechNews
@techlucker · 42,577
Telegram ranks this channel #28 of 79 here — alongside 78 others — read 28 August 2026
Английский для программиста | EnglishScript
@EnglishScript · 44,304
Telegram ranks this channel #28 of 82 here — alongside 81 others — read 27 August 2026
OSINT mindset
@osint_mindset · 64,939
Telegram ranks this channel #42 of 83 here — alongside 82 others — read 21 August 2026
GitHub Community
@github · 155,088
Telegram ranks this channel #44 of 87 here — alongside 86 others — read 12 August 2026
Утечки информации
@dataleak · 117,550
Telegram ranks this channel #50 of 83 here — alongside 82 others — read 14 August 2026
Physics.Math.Code
@physics_lib · 146,706
Telegram ranks this channel #50 of 72 here — alongside 71 others — read 13 August 2026
Kali Linux
@linuxkalii · 55,893
Telegram ranks this channel #52 of 89 here — alongside 88 others — read 23 August 2026
Python обучающий
@pythonist24 · 55,153
Telegram ranks this channel #66 of 88 here — alongside 87 others — read 23 August 2026

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

“Этичный Хакер” (@hack_less), 242,543 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/hack_less.

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.