Telegram RegisterThe public register of Telegram
Telegram profile photo for Пост Лукацкого

Channel

Пост Лукацкого

@alukatsky

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

37,862subscribers

+418 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001077356912
TypeChannel
Username@alukatsky
DescriptionУникальный контент про кибербезопасность от Алексея Лукацкого (@alukatsk) - мысли, полезные ссылки, комментарии к текущим событиям, юмор и мемасики. Канал личный - мой работодатель никак не влияет на то, что здесь публикуется. Рекламу не размещаю!!!
Created31 July 2017measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live18 September 2026
Measurements held35
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/alukatsky

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

37,44437,86237,6536 August 2026 — 37,444 subscribers6 August 2026 — 37,444 subscribers6 August 2026 — 37,495 subscribers7 August 2026 — 37,515 subscribers8 August 2026 — 37,517 subscribers9 August 2026 — 37,521 subscribers10 August 2026 — 37,534 subscribers11 August 2026 — 37,546 subscribers12 August 2026 — 37,555 subscribers13 August 2026 — 37,574 subscribers15 August 2026 — 37,592 subscribers16 August 2026 — 37,590 subscribers17 August 2026 — 37,596 subscribers18 August 2026 — 37,612 subscribers19 August 2026 — 37,664 subscribers20 August 2026 — 37,654 subscribers22 August 2026 — 37,665 subscribers24 August 2026 — 37,667 subscribers25 August 2026 — 37,699 subscribers26 August 2026 — 37,710 subscribers27 August 2026 — 37,715 subscribers28 August 2026 — 37,720 subscribers28 August 2026 — 37,723 subscribers29 August 2026 — 37,716 subscribers30 August 2026 — 37,709 subscribers31 August 2026 — 37,697 subscribers1 September 2026 — 37,702 subscribers2 September 2026 — 37,709 subscribers4 September 2026 — 37,707 subscribers6 September 2026 — 37,739 subscribers10 September 2026 — 37,763 subscribers12 September 2026 — 37,791 subscribers14 September 2026 — 37,805 subscribers15 September 2026 — 37,826 subscribers18 September 2026 — 37,862 subscribers6 August 202618 September 2026
35 measurements spanning 43 days, net +418. 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 37,381–37,925 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 35
Measured (UTC)SubscribersChange
18 Sept 2026, 03:3637,862+36
15 Sept 2026, 19:4037,826+21
14 Sept 2026, 05:3737,805+14
12 Sept 2026, 09:5637,791+28
10 Sept 2026, 04:5637,763+24
6 Sept 2026, 20:5637,739+32
4 Sept 2026, 04:4037,707-2
2 Sept 2026, 16:0537,709+7
1 Sept 2026, 17:3437,702+5
31 Aug 2026, 19:0537,697-12
30 Aug 2026, 22:2737,709-7
29 Aug 2026, 22:3737,716-7
28 Aug 2026, 23:4537,723+3
28 Aug 2026, 02:4337,720+5
27 Aug 2026, 03:4837,715+5
26 Aug 2026, 00:4337,710+11
25 Aug 2026, 04:1737,699+32
24 Aug 2026, 00:5437,667+2
22 Aug 2026, 10:0637,665+11
20 Aug 2026, 21:1637,654first reading

Engagement

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

ERR · 30 days
15.9%
avg views ÷ 37,862 subscribers
Avg views / post
6,020
79 posts measured
Reaction rate
0.635%
reactions ÷ views · ER floor
Posts in window
82
of 163 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 77 of 79 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 23 September 2026
Posts held163 (31 July 202623 September 2026)
Views total475,940
Reactions total2,979
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken24 Sept 2026, 00:43 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
7,070
Videos
507
Links
7,920

Lifetime counters from Telegram’s own channel header, read 24 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
1m 20s
Average length
20s

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

6,407 reactions across 149 posts, in 53 distinct kinds. The most used accounts for 21.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1,35021.1%
🔥1,13617.7%
😁1,12117.5%
83813.1%
💯4066.34%
🤣3245.06%
🤔1933.01%
🤡1352.11%
🤝1131.76%
1011.58%
🤯811.26%
💩661.03%
😱470.734%
👏450.702%
❤‍🔥390.609%
👀340.531%
330.515%
😢290.453%
🥰270.421%
👌250.39%
33 further kinds2644.12%

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

Measured over the 163 most recent posts we hold, published 31 July 2026 to 23 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
55
across the posts below
Posts paid on
17
of 160 we hold a reading for · 11%
Most on one post
31
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @alukatsky. 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 163 most recent posts we hold for this entry, published 31 July 2026 to 23 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.

Recent posts

23 Sept 2026, 18:29 UTC≈2,170 views38 reactionsread 24 September 2026
Photo

#рефлексия

😁20🥰7👍5🤡4👌2

23 Sept 2026, 13:45 UTC≈3,660 views31 reactionsread 24 September 2026
Poll

Как называется единица измерения риска?

  1. Микроморт9%
  2. Меш8%
  3. Сантиморган4%
  4. Вар16%
  5. Рискограмм10%
  6. Бред, риск не имеет единицы измерения54%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

😁246🔥1

23 Sept 2026, 13:45 UTC≈3,360 viewsread 24 September 2026

«Венки в ассортименте» гласила надпись. Я уткнулся в нее, бродя под сенью чинар вечернего Ташкента. Хотя, если честно, ботаник из меня никудышний. Поэтому может это и не чинары были вовсе. Но не суть. Надпись, под которой бездомный лохматый барбос напрудил лужу, показав тем самым свое отношение к надписи и к жизни, навела меня на мысль очередного опроса на проверку кругозора. #опрос #риск

23 Sept 2026, 11:10 UTC≈3,800 views0 reactionsread 24 September 2026
Poll

У вас есть плейбук по работе с ИИ-инцидентами (утечки через LLM, злоупотребления ИИ-агентов, кража обучающих корпусов, атаки на локальный харнесс и т.п.)? #опрос #ии

  1. Да, есть полноценный плейбук под специфичные ИИ-инциденты5%
  2. Да, но мы включили эти инциденты в типовые плейбуки5%
  3. Нет, но мы в процессе разработки/тестирования10%
  4. Нет, но мы планируем разработать их в ближайшие полгода15%
  5. Нет, и пока не планируем (не видим необходимость)34%
  6. Затрудняюсь ответить / Не мой профиль31%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

23 Sept 2026, 11:10 UTC≈3,580 views6 reactionsread 24 September 2026

👀 Когда мы думали о развитии курса "SOC 2.0", то как я уже писал, решили не только расширить тему применения ИИ в SOC, но и добавить новый блок про использование SOC для работы с ИИ-инцидентами. Это желание было основано на ощущении, что многие ИБшники уже готовы к применению искусственного интеллекта для автоматизации рутинных задач SOC, как минимум, и обнаружения угроз, как максимум, но почти не готовы к тому, что

5👍1

23 Sept 2026, 07:28 UTC≈3,730 views19 reactionsread 24 September 2026
Photo

Выступал сегодня с keynote на TLDCON 2026 в Ташкенте с легким визионерским докладом, который поделил на 2 части. В первой говорил об атаках сегодняшнего дня на регистраторов доменов. Да, на базе ИИ, куда без него. По сути речь шла об эволюционном развитии атак. Во второй части позволил себе пофантазировать о том, как могут выглядеть регистратуры будущего и какие атаки будут актуальными для них 🌟 #мероприятие #презен

👍10🔥6😁3

23 Sept 2026, 04:26 UTC≈4,180 views23 reactionsread 24 September 2026

CISA опубликовала интересный документ "A Tale of Two SOCs: Insights From Two Red Team Assessments", который немного отличается от привычных документов американской ФСТЭК. Они провели Red Team'инг двух организаций схожими методами и, в конечном итоге, получили полный контроль над доменом в обеих организациях. В обеих она добралась до sensitive business systems и облачной инфраструктуры. Но первая компания практически

👍193🙏1

22 Sept 2026, 20:29 UTC≈4,430 views42 reactionsread 24 September 2026
Photo

ShinyHunters заявила о взломе ФБР через непатченный зеродей в Oracle PeopleSoft с последующей кражей 2-3 ТБ данных о текущих и бывших сотрудниках, а также о кандидатах на работу. Независимые источники вроде как подтверждают реальность данных, но ФБР пока не комментирует. #утечка #инцидент

🔥18❤‍🔥12😱8😁3👎1

22 Sept 2026, 17:57 UTC≈5,110 views13 reactionsread 24 September 2026
Photo

Национальные системы уведомления об инцидентах ИБ... Существуют они не только в России (привет, ГосСОПКА), но и в других юрисдикциях. И там эти системы гораздо более открыты для внешней оценки их работоспособности и эффективности. Вчера европейский суд аудиторов (или как еще перевести European Court of Auditors) опубликовал выводы об аудите европейской системы обнаружения и реагирования на инциденты ИБ. Их главный вы

👍54🔥4

22 Sept 2026, 13:46 UTC≈4,400 views10 reactionsread 24 September 2026

Писать про всякие инциденты с шифровальщиками, убежавшие ИИ-модели, убивающие младенцев, или очередной вредонос, написанный с применением ИИ, становится уже неинтересно, – это почти мейнстрим и про это пишут все. А вот копаться в последствиях от такого рода инцидентов гораздо интереснее и позволяет понять, насколько серьезно тема ИБ влияет именно на бизнес-показатели и как это все можно выносить на уровень топ-менедж

❤‍🔥3🔥32👍2

22 Sept 2026, 10:27 UTC≈4,390 views77 reactionsread 24 September 2026
Photo

Кажется, в российском кибербезе окончательно наступила эпоха признания. Нет, не того признания, когда компания пережила серьезную атаку без остановки бизнеса и не стала хвалиться об этом. И не того, когда CISO пять лет строил защиту, о которой никто не знает именно потому, что она работает. И даже не того, когда тебя уважают коллеги, потому что видели тебя в деле. Речь о настоящем признании. С дипломом, статуеткой,

😁4610🔥8🏆5🍾4🤔2🤣1😢1

22 Sept 2026, 06:46 UTC≈4,030 views25 reactionsread 24 September 2026

21 сентября Nepal Stock Exchange (NEPSE) полностью отменила торговую сессию. Причиной стал инцидент с шифровальщиком у DataHub Pvt Ltd, где размещались торговые системы сразу 72 брокерских компаний. Пострадавшую инфраструктуру изолировали, поскольку существовал риск распространения атаки на связанные сети, включая инфраструктуру самой биржи. Вроде ничего необычного. Ну шифровальщик, ну с кем не бывает. Но есть пароч

👍127🔥4💯1🤔1

Showing the 12 most recent of 163 posts we hold for @alukatsky. 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 edited after publishing

@alukatsky edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
11 August 2026
Most recent edit
31 August 2026

Polls

The 6 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

23 Sept 2026, 13:45 UTCAnonymous Quiz1,020 voters approx.

Как называется единица измерения риска?

  1. Микроморт9%
  2. Меш8%
  3. Сантиморган4%
  4. Вар16%
  5. Рискограмм10%
  6. Бред, риск не имеет единицы измерения54%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

23 Sept 2026, 11:10 UTCAnonymous Poll333 voters

У вас есть плейбук по работе с ИИ-инцидентами (утечки через LLM, злоупотребления ИИ-агентов, кража обучающих корпусов, атаки на локальный харнесс и т.п.)? #опрос #ии

  1. Да, есть полноценный плейбук под специфичные ИИ-инциденты5%
  2. Да, но мы включили эти инциденты в типовые плейбуки5%
  3. Нет, но мы в процессе разработки/тестирования10%
  4. Нет, но мы планируем разработать их в ближайшие полгода15%
  5. Нет, и пока не планируем (не видим необходимость)34%
  6. Затрудняюсь ответить / Не мой профиль31%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

21 Sept 2026, 11:57 UTCAnonymous Poll951 voters

А вы 30 сентября какую ИБ-конфу решили посетить? #опрос

  1. GIS DAYS (Питер)4%
  2. ZeroNights (Питер)7%
  3. Онлайн-конфа по автономным SOCам (AM Live)2%
  4. Я вообще на KazHackStan поеду (Астана)12%
  5. Буду на мероприятии не из списка выше3%
  6. У меня отходняк от BIS Summit предыдущего дня запланирован2%
  7. С «Инфобез без иллюзий» еще не успею вернуться1%
  8. Мероприятие по грамотному планированию мероприятий5%
  9. А работать кто будет?64%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

11 Sept 2026, 08:30 UTCAnonymous Poll577 voters

А как у вас преимущественно строится бюджет на ИБ в 2027-м году?

  1. На основе требований бизнеса8%
  2. В соответствие с требованиями регуляторики10%
  3. Опираясь на угрозы и риски14%
  4. Хоть что-то бы дали, а там выкручиваться буду21%
  5. Бюджет? Что это? Кому-то еще и деньги на ИБ дают?31%
  6. Начальство есть – пусть оно о бюджете думает15%

Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.

31 Aug 2026, 08:11 UTCAnonymous Poll2,260 voters approx.

Через какой порт сегодня проходит больше всего трафика протокола Telnet в реальном Интернете? #опрос

  1. 204%
  2. 2117%
  3. 2214%
  4. 2320%
  5. 8019%
  6. 87105%
  7. Не знаю22%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

25 Aug 2026, 16:49 UTCAnonymous Poll1,570 voters approx.

Кого вы возьмете на работу из этих двух кандидатов? #опрос #работа

  1. Первого (который курсы завершил)12%
  2. Второго (который багу нашел)60%
  3. Да я сам ищу работу28%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 163 most recent posts we hold, published 31 July 2026 to 23 September 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Forward network

Republished by

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

Кот на яблоне
@kot_na_tree · 46
3 posts
ИТ-Диалог
@ITDialog_official · 973
2 posts
Я у мамы SecMemOps
@secmemops · 5,340
2 posts
Авангард Медиа | Про ИБ и не только
@Avangardmedia · 956
1 post
HireHack
@IThirehack · 3,881
1 post
ML Seva100p0l
@ML_Sevastopol · 1
1 post
Remote Meme Execution
@RemoteMemeExecution · 1,574
1 post
SecurityLab.ru
@SecLabNews · 84,459
1 post
AI Attacks
@aiattacks · 983
1 post
AI SecOps
@aisecops · 1,177
1 post
Антивирусное ДНО
@avdno · 1,675
1 post
BearPass — берлога безопасности
@bearpass_news · 194
1 post
Bullshitjob
@bullshitjob · 43
1 post
Пиэмэмим кибербез
@cyberbez_pmm · 155
1 post
Единая биометрическая система | 572-ФЗ
@ebs_572fz · 1,853
1 post
Fisher.Talks
@fisher_talks · 239
1 post
gbwce
@gbwcel · 44
1 post
UNLIM
@ibbezgranic · 80
1 post
Информация без опасностей (безопасность)
@infobezopasnost · 1,511
1 post
Integral Security
@integral_security · 1,718
1 post
ИнфоПовод
@kaluginprofit · 5,707
1 post
Sasha Kruasanova PROIT
@kruasanova_as · 2,193
1 post
NetSkills
@netskills · 4,597
1 post
ODC
@odc_kib · 41
1 post
Pentester
@pentester · 208
1 post
Похек meme
@poxek_meme · 782
1 post
DPO отвечает
@privacy_tech · 961
1 post
Про tech и этих
@protechietich · 20,492
1 post
Редакция
@redaktionen · 25
1 post
Избранное про ИБ
@sergeyborisov23 · 1,092
1 post
Защита персональных данных и не только
@shudrova_pdn · 1,327
1 post
какиетоновости
@stable_news · 58
1 post
Технологический Болт Генона
@tech_b0lt_Genona · 9,731
1 post
Эшер II. A+
@usher2 · 16,433
1 post
Учимся визуализировать
@visual_scheme · 202
1 post
WeLoveNoFraud
@welovenofraud · 276
1 post
SbX | Security by Xyurity
@xyuriti · 1,226
1 post
yoprstcon
@yoprstcon · 407
1 post
ЗаТелеком 🌐
@zatelecom · 64,628
1 post
⁣Злой Админ
@zloyadm_in · 232
1 post

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 42 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. The 23 listed below are the most frequent namers; the rest are counted above but not each listed.

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.

SecurityLab.ru
@SecLabNews · 84,459
#1
Positive Technologies
@Positive_Technologies · 28,968
#2
Управление Уязвимостями и прочее
@avleonovrus · 12,130
#3
SecAtor
@true_secator · 41,700
#4
BI.ZONE
@bizone_channel · 11,212
#5
OFFZONE
@offzone_moscow · 7,369
#6
Резбез
@Rez_in_Bez · 2,653
#7
AM Live
@anti_malware · 13,147
#8
Похек
@poxek · 16,779
#9
Кибервойна
@cyberguerre · 8,757
#10
ESCalator
@ptescalator · 8,039
#11
Листок бюрократической защиты информации
@bureaucraticsecurity · 19,075
#12
НеКасперский
@NeKaspersky · 16,061
#13
Hacker News
@HNews · 7,293
#14
Sachok
@CyberSachok · 11,259
#15
Топ кибербезопасности Батранкова
@safebdv · 10,041
#16
k8s (in)security
@k8security · 13,119
#17
Russian OSINT
@Russian_OSINT · 47,701
#18
Вакансии в ИБ | infosec
@infosec_work · 15,677
#19
AlexRedSec
@alexredsec · 4,007
#20
Positive Development Community
@POSIdev · 3,186
#21
Солар
@solar_security · 6,477
#22
CISOCLUB - кибербезопасность и ИТ
@cisoclub · 7,058
#23
infosec
@it_secur · 61,761
#24
PWN AI
@pwnai · 7,283
#25
Social Engineering
@Social_engineering · 125,008
#26
AppSec Journey
@AppSecJourney · 3,467
#27
RED Security
@redsecurity_co · 5,191
#28
YAH
@YAH_Channel · 7,567
#29
Кибербез образование | cybersecurity-roadmap.ru
@cyber_edu · 6,023
#30
Солдатов в Телеграм
@soldatov_in_telegram · 2,275
#31
Порвали два трояна
@kasperskyb2b · 9,406
#32
Хакер — Xakep.RU
@xakep_ru · 39,506
#33
Positive Events
@PositiveEvents · 6,114
#34
Мероприятия по ИБ
@InfoBezEvents · 5,637
#35
CyberCamp
@CYBERCAMP_ONLINE · 8,668
#36
Codeby
@codeby_sec · 36,985
#37
ZLONOV security
@zlonov_security · 3,983
#38
Makrushin
@makrushin · 3,865
#39
Echelon Eyes
@EchelonEyes · 6,535
#40
BESSEC
@bessec · 4,733
#41
Борьба с киберпреступностью | F6
@f6_cybersecurity · 22,323
#42
Cybred
@cybred · 11,091
#43
IT's positive investing
@positive_investing · 9,281
#44
Security Wine (бывший - DevSecOps Wine)
@sec_devops · 7,110
#45
КИБЕР МЕДИА
@secmedia · 5,915
#46
Inside
@in51d3 · 7,996
#47
Kaspersky
@kasperskylab_ru · 28,858
#48
SOC FORUM | Неделя кибербезопасности
@forumsoc · 2,876
#49
Cybersecurity memes off
@cybersecurity_memes_off · 1,698
#50
Информация опасносте
@alexmakus · 18,808
#51
S.E.Reborn
@S_E_Reborn · 22,374
#52
RPPA PRO: Privacy • AI • Cybersecurity • IP
@GDPRru · 6,036
#53
APT
@APT_Notes · 16,571
#54
Аналитический центр RPPA
@Persdata · 7,827
#55
ISACARuSec
@IsacaRuSec · 2,260
#56
Евгений Касперский
@e_kaspersky · 6,535
#57
Код ИБ: ИИ & КиберБезопасность
@codeibnews · 6,852
#58
Анонсы ИБ мероприятий
@secwebinars · 6,162
#59
BIS Journal — Информационная безопасность
@BISInside · 2,271
#60
Privacy Advocates
@prv_adv · 21,945
#61
Life-Hack - Хакер
@haccking · 63,203
#62
Кибердом
@cyberdom_business · 12,404
#63
infosecurity
@tg_infosec · 26,786
#64
Blue (h/c)at Café
@bh_cat · 3,975
#65
R-Vision
@rvision_pro · 2,488
#66
Денис Лукаш | Privacy Expert
@privacyexpert · 13,429
#67
RuSecJobs Channel
@RuSecJobs · 11,322
#68
Утечки информации
@dataleak · 119,401
#69
БДУ ФСТЭК России
@bdufstecru · 10,568
#70
Раньше всех. Ну почти.
@bbbreaking · 1,971,693
#71
Information Security Memes
@infosecmemes · 9,694
#72
Минцифры России
@mintsifry · 235,414
#73
Mash
@mash · 3,096,804
#74
Банкста
@banksta · 438,140
#75
Багхантер
@bughunter_circuit · 3,514
#76
Positive Hack Days Media
@positivehackmedia · 30,694
#77
CyberSquatting RU Alerts
@CyberSquattingChannel · 2,451
#78
ГосСОПКА Центр
@sopkacentr · 16,415
#79
Эксплойт
@exploitex · 2,041,128
#80
Двач
@dvachannel · 938,773
#81
AppSec & DevSecOps Jobs
@appsec_job · 4,728
#82
DevSecOps Talks
@devsecops_weekly · 8,025
#83
BI.ZONE Bug Bounty
@bizone_bugbounty · 6,604
#84
ИБ в "Законе"
@MetaSecurityInformation · 4,056
#85
linkmeup
@linkmeup_podcast · 17,369
#86
#ПоИБэшечка
@Poibeshechka · 1,850
#87
The After Times
@theaftertimes · 16,774
#88
PT SWARM
@ptswarm · 7,502
#89

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

Positive Technologies
@Positive_Technologies · 28,968
Telegram ranks this channel #1 of 87 here — alongside 86 others — read 9 September 2026
SecurityLab.ru
@SecLabNews · 84,459
Telegram ranks this channel #1 of 90 here — alongside 89 others — read 18 August 2026
Борьба с киберпреступностью | F6
@f6_cybersecurity · 22,323
Telegram ranks this channel #2 of 85 here — alongside 84 others — read 21 September 2026
IT и безопасность
@tg_security · 26,613
Telegram ranks this channel #2 of 91 here — alongside 90 others — read 12 September 2026
SecAtor
@true_secator · 41,700
Telegram ranks this channel #2 of 78 here — alongside 77 others — read 29 August 2026
Kaspersky
@kasperskylab_ru · 28,858
Telegram ranks this channel #5 of 96 here — alongside 95 others — read 9 September 2026
Хакер — Xakep.RU
@xakep_ru · 39,506
Telegram ranks this channel #5 of 83 here — alongside 82 others — read 30 August 2026
Russian OSINT
@Russian_OSINT · 47,701
Telegram ranks this channel #5 of 82 here — alongside 81 others — read 26 August 2026
Отдел К: IT-технологии, кибербезопасность
@cyber_cabb · 81,445
Telegram ranks this channel #7 of 94 here — alongside 93 others — read 18 August 2026
Privacy Advocates
@prv_adv · 21,945
Telegram ranks this channel #8 of 98 here — alongside 97 others — read 22 September 2026
Пакет Безопасности
@package_security · 33,106
Telegram ranks this channel #9 of 82 here — alongside 81 others — read 4 September 2026
Codeby
@codeby_sec · 36,985
Telegram ranks this channel #9 of 76 here — alongside 75 others — read 1 September 2026
Вестник Киберполиции России
@cyberpolice_rus · 83,750
Telegram ranks this channel #9 of 92 here — alongside 91 others — read 18 August 2026
Утечки информации
@dataleak · 119,401
Telegram ranks this channel #9 of 83 here — alongside 82 others — read 14 August 2026
Investigation & Forensic TOOLS
@forensictools · 22,368
Telegram ranks this channel #10 of 74 here — alongside 73 others — read 20 September 2026
Life-Hack - Хакер
@haccking · 63,203
Telegram ranks this channel #10 of 85 here — alongside 84 others — read 21 August 2026
infosec
@it_secur · 61,761
Telegram ranks this channel #11 of 81 here — alongside 80 others — read 22 August 2026
S.E.Reborn
@S_E_Reborn · 22,374
Telegram ranks this channel #12 of 66 here — alongside 65 others — read 20 September 2026
S.E.Book
@S_E_Book · 23,170
Telegram ranks this channel #12 of 64 here — alongside 63 others — read 19 September 2026
Интернет-Розыск
@irozysk · 46,000
Telegram ranks this channel #12 of 79 here — alongside 78 others — read 27 August 2026
Positive Hack Days Media
@positivehackmedia · 30,694
Telegram ranks this channel #13 of 88 here — alongside 87 others — read 6 September 2026
infosecurity
@tg_infosec · 26,786
Telegram ranks this channel #14 of 74 here — alongside 73 others — read 11 September 2026
Social Engineering
@Social_engineering · 125,008
Telegram ranks this channel #18 of 82 here — alongside 81 others — read 13 August 2026
Нецифровая экономика
@antidigital · 24,409
Telegram ranks this channel #25 of 96 here — alongside 95 others — read 16 September 2026

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

“Пост Лукацкого” (@alukatsky), 37,862 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/alukatsky.

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.