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

38,422subscribers

+978 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 2017 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live7 November 2026
Measurements held60
Confirmed unchanged1 time, most recently 7 November 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 the other topics.

Growth

37,44438,42237,9336 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 subscribers30 September 2026 — 37,915 subscribers6 October 2026 — 37,955 subscribers10 October 2026 — 38,042 subscribers13 October 2026 — 38,216 subscribers15 October 2026 — 38,260 subscribers15 October 2026 — 38,276 subscribers16 October 2026 — 38,303 subscribers17 October 2026 — 38,305 subscribers18 October 2026 — 38,303 subscribers19 October 2026 — 38,313 subscribers21 October 2026 — 38,314 subscribers22 October 2026 — 38,333 subscribers24 October 2026 — 38,348 subscribers26 October 2026 — 38,360 subscribers27 October 2026 — 38,373 subscribers28 October 2026 — 38,385 subscribers30 October 2026 — 38,377 subscribers31 October 2026 — 38,395 subscribers1 November 2026 — 38,387 subscribers2 November 2026 — 38,382 subscribers3 November 2026 — 38,387 subscribers4 November 2026 — 38,398 subscribers5 November 2026 — 38,407 subscribers6 November 2026 — 38,417 subscribers7 November 2026 — 38,422 subscribers6 August 20267 November 2026
60 measurements spanning 93 days, net +978. 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,297–38,569 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 60
Measured (UTC)SubscribersChange
7 Nov 2026, 06:2838,422+5
6 Nov 2026, 08:4838,417+10
5 Nov 2026, 09:5138,407+9
4 Nov 2026, 07:5738,398+11
3 Nov 2026, 06:3038,387+5
2 Nov 2026, 09:2938,382-5
1 Nov 2026, 12:4838,387-8
31 Oct 2026, 10:0938,395+18
30 Oct 2026, 08:1138,377-8
28 Oct 2026, 02:1838,385+12
27 Oct 2026, 04:3538,373+13
26 Oct 2026, 05:3738,360+12
24 Oct 2026, 03:1438,348+15
22 Oct 2026, 23:4638,333+19
21 Oct 2026, 18:1938,314+1
19 Oct 2026, 19:5638,313+10
18 Oct 2026, 17:3938,303-2
17 Oct 2026, 18:2738,305+2
16 Oct 2026, 20:4938,303+27
15 Oct 2026, 22:4538,276first reading

Engagement

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

ERR · 30 days
16.4%
avg views ÷ 38,422 subscribers
Avg views / post
6,280
145 posts measured
Reaction rate
0.71%
reactions ÷ views · ER floor
Posts in window
145
of 372 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 7 November 2026
Posts held372 (31 July 2026 – 7 November 2026)
Views total911,280
Reactions total6,467
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Nov 2026, 22:55 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,210
Videos
≈517
Links
≈8,040

Lifetime counters from Telegram’s own channel header, read 7 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
11m 21s
Average length
49s

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

15,766 reactions across 358 posts, in 70 distinct kinds. The most used accounts for 19.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁3,10819.7%
👍3,04719.3%
🔥2,54916.2%
❤2,02012.8%
🤣1,5299.70%
💯7644.85%
🤔4823.06%
🤡2661.69%
✍1881.19%
👏1701.08%
🤝1581.00%
😢1530.97%
😱1080.685%
🤯1080.685%
👀1040.66%
🤬780.495%
💩700.444%
😭630.4%
❤‍🔥550.349%
🥰520.33%
50 further kinds6944.40%

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

Measured over the 372 most recent posts we hold, published 31 July 2026 to 7 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
80
across the posts below
Posts paid on
36
of 369 we hold a reading for · 10%
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 372 most recent posts we hold for this entry, published 31 July 2026 to 7 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.

Recent posts

Telegram’s own ‘edited’ marker: 3 of 145 posts held from the last 30 days (2.07%) 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).

7 Nov 2026, 17:39 UTC≈2,710 views48 reactionsread 7 November 2026

Когда меня спросили в Старбаксе при покупке Американо, нет ли у меня аллергии, я удивился в первый раз. Когда мне тот же вопрос стали задавать при покупке любой еды на вынос, в Макдональдсе, мишленовском ресторане, уличных забегаловках и пабах, я решил поинтересоваться, откуда взялся этот заученный навык у всех работников английского общепита. Оказалось, что все дело в так называемом "законе Наташи", вступившем в си…

🔥27❤10👍4🤯3😱2👎1🤬1

7 Nov 2026, 09:37 UTC≈4,210 views71 reactionsread 7 November 2026
Photo

Вот интересно, рекламировать VPN до российских адресов, заблокированных в Европе, - это легально или нет? #суверенитет #vpn

😁68🔥2👍1

6 Nov 2026, 17:55 UTC≈4,480 views54 reactionsread 7 November 2026
Photo

В Блечли Парке есть стена славы голубей, которых использовали для передачи секретных сообщений в ситуациях, когда другим средствам коммуникации доверять было нельзя. Мне кажется, что МЧС планирует у нас возродить этот вид связи. Иначе как еще объяснить их запрет на коммуникации с внешним миром по e-mail? Мне кажется, что МЧС надо быть последовательным и запретить телефоны, так как по ним говорят мошенники, и сотрудн…

💯31😁20🔥2👍1

6 Nov 2026, 14:29 UTC≈4,540 views25 reactionsread 7 November 2026

Представьте, подключились вы к ЕБС... и все. На проверку отправляются не все запросы на биометрическую аутентификацию, а те, по которым приходит отказ или низкий score соответствия подлинности все равно пропускаются. Да не, как такое возможно, спросите вы. А вот так. 5 ноября FINRA, американский регулятор брокерской деятельности, объявил о санкциях против Webull Financial, который использовал внешнего поставщика авто…

🔥12👍4❤2😁2😱2👌1🤔1🤯1

6 Nov 2026, 10:45 UTC≈4,630 views16 reactionsread 7 November 2026

DigiCert тут провел расследования очередного инцидента, который позволил получить несанкционированный доступ к бизнес-системам, и поделился результатами. И это не та история, которая была весной, а другая (у PKIщиков что-то много их в последнее время). Если кратко, то 4 февраля 2025 года внутреннюю систему DigiCert перенесли из VPN-ограниченного сегмента в другую инфраструктурную зону, в результате чего часть функци…

👍11❤3💯2

6 Nov 2026, 08:41 UTC≈5,090 views7 reactionsread 7 November 2026
File

File, posted without a caption

🔥5❤1👍1

6 Nov 2026, 08:41 UTC≈5,150 views20 reactionsread 7 November 2026
Photo

Gartner в отчете "The Roles Required for the AI-Enabled Security Operations Center (SOC)" пишет, что к 2028-му году в SOCах будет на 50% больше инженеров, чем аналитиков. Аналитиков L1 тоже не будет, инженеры по детектам превратятся в промпт-инженеров, а фокус сдвинется в сторону Exposure Management. Ну и там еще много всего написано, не буду пересказывать – вы и сами можете прочитать 👇 #soc #тенденции #работа #ии

😁8❤3💯3👍2🤔2👌1🔥1

5 Nov 2026, 20:41 UTC≈5,280 views55 reactionsread 7 November 2026
Photo

Инструкции получил, инструментарий обновил, шифрблокноты сменил…

😁40✍8🔥5👍2

5 Nov 2026, 15:50 UTC≈5,360 views12 reactionsread 7 November 2026

Прошло больше года с инцидента у английского ритейлера Marks & Spencer, который нанес ущерба на сотни миллионов долларов. И вот 4 ноября Marks & Spencer опубликовала полугодовые результаты за 26 недель, завершившихся 26 сентября 2026 года. И что же мы там видим? Кибератака, произошедшая весной 2025 года, до сих пор фигурирует в объяснении операционных результатов бизнеса. M&S сообщила, что последствия ручных процеду…

👀9✍2👍1

5 Nov 2026, 12:33 UTC≈5,180 views15 reactionsread 7 November 2026

Индия обсуждает усиление CERT-In, чтобы добиваться обязательного устранения критических уязвимостей в установленные сроки. Как пишет The Economic Times, начать предлагают с государственных организаций. Пока это обсуждаемая инициатива, о принятом решении издание не сообщает. Поводом стал кризис вокруг PHP. По данным газеты, две критические уязвимости, обнаруженные с помощью ИИ, вызвали массовые атаки. CERT-In рекомен…

👍7🤔4❤2❤‍🔥1🔥1

5 Nov 2026, 10:34 UTC≈5,390 views18 reactionsread 7 November 2026

Про случившийся 11 октября инцидент с Ahold Delhaize я уже писал – была нарушена работа ряда цифровых и логистических систем ритейлера. В частности, пострадала электронная торговля Albert Heijn. В ходе восстановления компания поэтапно возвращала доставку продуктов: сначала примерно на треть обычной мощности, затем 28 октября сообщила о возвращении нормального объёма доставки. И вот вчера компания Ahold Delhaize опубл…

❤7💯7🔥2👍1🫡1

5 Nov 2026, 08:46 UTC≈6,490 views36 reactionsread 7 November 2026

Тут китайские товарищи ведут регулярно обновляемый список IP, на которых "висят" ИИ-фреймворки для проведения атак ARTEX и CyberStrike AI, которые задействованы почти во всех последних инцидентах с участием ИИ-агентов: 🔗 ARTEX - https://threatbook.io/hubfs/Feeds/ARTEX.txt 🔗 CyberStrikeAI - https://threatbook.io/hubfs/Feeds/CSAI.txt #ии #threatintelligence

❤15👍13🔥7👏1

Showing the 12 most recent of 372 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 4 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
23 October 2026

Polls

The 6 most recent of 8 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.

17 Oct 2026, 11:28 UTCAnonymous Poll1,350 voters approx.

Делайте ваши ставки, какое решение может быть принято? #опрос

  1. Заблокировать все иностранное38%
  2. Ввести посадки за использование в его несуверенного5%
  3. Разрешить только посконное4%
  4. Дружить с Китаем глубже5%
  5. «Бомбить Воронеж» (это мем из 2010-х, а не призыв)7%
  6. Инвестировать в развитие своего ИИ10%
  7. Украсть на дискете модели и датасеты у Qwen’а3%
  8. Запретить кибератаки, ать-два15%
  9. Ушел за грибами; потом гляну результаты12%

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

26 Sept 2026, 05:11 UTCAnonymous Quiz805 voters

Если вы следите за новостями рынка ИБ и знакомились с материалами судебного дела А40-290966/2023, то как вы думаете, что согласно мнению суда сделали хакеры, которые взломали организацию и получили доступ к компьютеру гендира с электронной подписью?

  1. Использовали ПК как точку входа, после чего уничтожили всю инфраструктуру12%
  2. Украли деньги из банка, пользуясь ключом электронной подписи15%
  3. Оформили налоговую декларацию за компанию и отправили ее в ФНС17%
  4. Украли коллекцию фото и видео директора5%
  5. Ничего не сделали, так как компьютер был на Астре, а хакеры не были знакомы с этой ОС13%
  6. Пропатчили компьютер и настроили на нем механизмы ИБ15%
  7. Затрудняюсь с ответом23%

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

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

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

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

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

23 Sept 2026, 11:10 UTCAnonymous Poll419 voters

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

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

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.

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 372 most recent posts we hold, published 31 July 2026 to 7 November 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 · 47
3 posts
ИТ-Диалог
@ITDialog_official · 964
2 posts
Я у мамы SecMemOps
@secmemops · 5,423
2 posts
Авангард Медиа | Про ИБ и не только
@Avangardmedia · 943
1 post
HireHack
@IThirehack · 3,859
1 post
ML Seva100p0l
@ML_Sevastopol · 1
1 post
Remote Meme Execution
@RemoteMemeExecution · 1,650
1 post
SecurityLab.ru
@SecLabNews · 86,460
1 post
AI Attacks
@aiattacks · 1,108
1 post
AI SecOps
@aisecops · 1,238
1 post
Антивирусное ДНО
@avdno · 1,653
1 post
BearPass — берлога безопасности
@bearpass_news · 198
1 post
Пиэмэмим кибербез
@cyberbez_pmm · 151
1 post
Cyber Security Club Moscow
@cybersecurityclub · 655
1 post
Единая биометрическая система | 572-ФЗ
@ebs_572fz · 1,822
1 post
Fisher.Talks
@fisher_talks · 237
1 post
Fun Science
@funscience · 34,235
1 post
gbwce
@gbwcel · 48
1 post
UNLIM
@ibbezgranic · 80
1 post
Информация без опасностей (безопасность)
@infobezopasnost · 1,519
1 post
Integral Security
@integral_security · 1,712
1 post
Зоопарк из слоновой кости
@ivoryzoo · 32,029
1 post
ИнфоПовод
@kaluginprofit · 5,839
1 post
Sasha Kruasanova PROIT
@kruasanova_as · 2,195
1 post
Mobile AppSec World
@mobile_appsec_world · 8,600
1 post
NetSkills
@netskills · 4,598
1 post
ODC
@odc_kib · 40
1 post
papirsec
@papirsec · 770
1 post
Pentester
@pentester · 211
1 post
Похек meme
@poxek_meme · 800
1 post
DPO отвечает
@privacy_tech · 971
1 post
Про tech и этих
@protechietich · 20,855
1 post
Редакция
@redaktionen · 25
1 post
Избранное про ИБ
@sergeyborisov23 · 1,120
1 post
Защита персональных данных и не только
@shudrova_pdn · 1,591
1 post
какиетоновости
@stable_news · 59
1 post
Технологический Болт Генона
@tech_b0lt_Genona · 10,579
1 post
Эшер II. A+
@usher2 · 16,532
1 post
Учимся визуализировать
@visual_scheme · 202
1 post
WeLoveNoFraud
@welovenofraud · 276
1 post
SbX | Security by Xyurity
@xyuriti · 1,227
1 post
yoprstcon
@yoprstcon · 403
1 post
ЗаТелеком 🌐
@zatelecom · 64,562
1 post
⁣Злой Админ
@zloyadm_in · 231
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 45 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 22 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 · 86,460
#1
Positive Technologies
@Positive_Technologies · 29,430
#2
Управление Уязвимостями и прочее
@avleonovrus · 12,623
#3
SecAtor
@true_secator · 42,177
#4
BI.ZONE
@bizone_channel · 11,589
#5
OFFZONE
@offzone_moscow · 7,536
#6
Резбез
@Rez_in_Bez · 2,644
#7
AM Live
@anti_malware · 13,172
#8
Похек
@poxek · 17,272
#9
Кибервойна
@cyberguerre · 8,911
#10
ESCalator
@ptescalator · 8,350
#11
Листок бюрократической защиты информации
@bureaucraticsecurity · 19,135
#12
НеКасперский
@NeKaspersky · 16,217
#13
Hacker News
@HNews · 7,260
#14
Sachok
@CyberSachok · 11,347
#15
Топ кибербезопасности Батранкова
@safebdv · 9,939
#16
k8s (in)security
@k8security · 13,317
#17
Russian OSINT
@Russian_OSINT · 48,496
#18
Вакансии в ИБ | infosec
@infosec_work · 16,321
#19
AlexRedSec
@alexredsec · 4,034
#20
Positive Development Community
@POSIdev · 3,237
#21
Солар
@solar_security · 6,639
#22
CISOCLUB - кибербезопасность и ИТ
@cisoclub · 7,191
#23
infosec
@it_secur · 63,349
#24
PWN AI
@pwnai · 7,629
#25
Social Engineering
@Social_engineering · 124,717
#26
AppSec Journey
@AppSecJourney · 3,542
#27
RED Security
@redsecurity_co · 5,196
#28
YAH
@YAH_Channel · 7,632
#29
Кибербез образование | cybersecurity-roadmap.ru
@cyber_edu · 6,012
#30
Солдатов в Телеграм
@soldatov_in_telegram · 2,286
#31
Порвали два трояна
@kasperskyb2b · 9,436
#32
Хакер — Xakep.RU
@xakep_ru · 40,287
#33
Positive Events
@PositiveEvents · 6,118
#34
Мероприятия по ИБ
@InfoBezEvents · 5,689
#35
CyberCamp
@CYBERCAMP_ONLINE · 8,750
#36
Codeby
@codeby_sec · 37,058
#37
ZLONOV security
@zlonov_security · 3,987
#38
Makrushin
@makrushin · 4,103
#39
Echelon Eyes
@EchelonEyes · 6,539
#40
BESSEC
@bessec · 4,796
#41
Борьба с киберпреступностью | F6
@f6_cybersecurity · 22,365
#42
Cybred
@cybred · 11,416
#43
IT's positive investing
@positive_investing · 9,193
#44
Security Wine (бывший - DevSecOps Wine)
@sec_devops · 7,090
#45
КИБЕР МЕДИА
@secmedia · 6,091
#46
Inside
@in51d3 · 7,968
#47
Kaspersky
@kasperskylab_ru · 28,900
#48
SOC FORUM | Неделя кибербезопасности
@forumsoc · 3,203
#49
Cybersecurity memes off
@cybersecurity_memes_off · 1,705
#50
Информация опасносте
@alexmakus · 18,748
#51
S.E.Reborn
@S_E_Reborn · 22,457
#52
RPPA PRO: Privacy • AI • Cybersecurity • IP
@GDPRru · 6,142
#53
APT
@APT_Notes · 17,319
#54
Аналитический центр RPPA
@Persdata · 7,741
#55
ISACARuSec
@IsacaRuSec · 2,266
#56
Евгений Касперский
@e_kaspersky · 6,616
#57
Код ИБ: ИИ & КиберБезопасность
@codeibnews · 7,010
#58
Анонсы ИБ мероприятий
@secwebinars · 6,154
#59
BIS Journal — Информационная безопасность
@BISInside · 2,273
#60
Privacy Advocates
@prv_adv · 21,855
#61
Life-Hack - Хакер
@haccking · 63,033
#62
Кибердом
@cyberdom_business · 12,777
#63
infosecurity
@tg_infosec · 26,848
#64
Blue (h/c)at Café
@bh_cat · 4,001
#65
R-Vision
@rvision_pro · 2,519
#66
Денис Лукаш | Privacy Expert
@privacyexpert · 13,401
#67
RuSecJobs Channel
@RuSecJobs · 11,606
#68
Утечки информации
@dataleak · 117,868
#69
БДУ ФСТЭК России
@bdufstecru · 10,637
#70
Раньше всех. Ну почти.
@bbbreaking · 1,975,837
#71
Information Security Memes
@infosecmemes · 9,625
#72
Минцифры России
@mintsifry · 232,573
#73
Mash
@mash · 3,142,084
#74
Банкста
@banksta · 439,713
#75
Багхантер 2.0
@bughunter_circuit · 19,448
#76
Positive Hack Days Media
@positivehackmedia · 30,082
#77
CyberSquatting RU Alerts
@CyberSquattingChannel · 2,512
#78
ГосСОПКА Центр
@sopkacentr · 6,141
#79
Эксплойт
@exploitex · 2,028,700
#80
Двач
@dvachannel · 970,017
#81
AppSec & DevSecOps Jobs
@appsec_job · 4,884
#82
DevSecOps Talks
@devsecops_weekly · 8,080
#83
BI.ZONE Bug Bounty
@bizone_bugbounty · 6,732
#84
ИБ в "Законе"
@MetaSecurityInformation · 4,077
#85
linkmeup
@linkmeup_podcast · 17,565
#86
#ПоИБэшечка
@Poibeshechka · 1,847
#87
The After Times
@theaftertimes · 16,839
#88
PT SWARM
@ptswarm · 7,612
#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.

Листок бюрократической защиты информации
@bureaucraticsecurity · 19,135
Telegram ranks this channel #1 of 98 here — alongside 97 others — read 4 October 2026
Positive Technologies
@Positive_Technologies · 29,430
Telegram ranks this channel #1 of 87 here — alongside 86 others — read 9 September 2026
SecurityLab.ru
@SecLabNews · 86,460
Telegram ranks this channel #1 of 90 here — alongside 89 others — read 18 August 2026
Борьба с киберпреступностью | F6
@f6_cybersecurity · 22,365
Telegram ranks this channel #2 of 85 here — alongside 84 others — read 21 September 2026
IT и безопасность
@tg_security · 26,838
Telegram ranks this channel #2 of 91 here — alongside 90 others — read 12 September 2026
SecAtor
@true_secator · 42,177
Telegram ranks this channel #2 of 78 here — alongside 77 others — read 29 August 2026
Kaspersky
@kasperskylab_ru · 28,900
Telegram ranks this channel #5 of 96 here — alongside 95 others — read 9 September 2026
Хакер — Xakep.RU
@xakep_ru · 40,287
Telegram ranks this channel #5 of 83 here — alongside 82 others — read 30 August 2026
Russian OSINT
@Russian_OSINT · 48,496
Telegram ranks this channel #5 of 82 here — alongside 81 others — read 26 August 2026
Информация опасносте
@alexmakus · 18,748
Telegram ranks this channel #6 of 85 here — alongside 84 others — read 5 October 2026
Отдел К: IT-технологии, кибербезопасность
@cyber_cabb · 81,650
Telegram ranks this channel #7 of 94 here — alongside 93 others — read 18 August 2026
I’m CTO, bitch
@ctobtch · 20,252
Telegram ranks this channel #8 of 95 here — alongside 94 others — read 28 September 2026
КиберДед official
@deedcoin_club · 22,983
Telegram ranks this channel #8 of 84 here — alongside 83 others — read 25 September 2026
Privacy Advocates
@prv_adv · 21,855
Telegram ranks this channel #8 of 98 here — alongside 97 others — read 22 September 2026
Пакет Безопасности
@package_security · 33,788
Telegram ranks this channel #9 of 82 here — alongside 81 others — read 4 September 2026
Codeby
@codeby_sec · 37,058
Telegram ranks this channel #9 of 76 here — alongside 75 others — read 1 September 2026
Вестник Киберполиции России
@cyberpolice_rus · 82,869
Telegram ranks this channel #9 of 92 here — alongside 91 others — read 18 August 2026
Утечки информации
@dataleak · 117,868
Telegram ranks this channel #9 of 83 here — alongside 82 others — read 14 August 2026
Investigation & Forensic TOOLS
@forensictools · 22,599
Telegram ranks this channel #10 of 74 here — alongside 73 others — read 20 September 2026
Life-Hack - Хакер
@haccking · 63,033
Telegram ranks this channel #10 of 85 here — alongside 84 others — read 21 August 2026
infosec
@it_secur · 63,349
Telegram ranks this channel #11 of 81 here — alongside 80 others — read 22 August 2026
S.E.Reborn
@S_E_Reborn · 22,457
Telegram ranks this channel #12 of 66 here — alongside 65 others — read 20 September 2026
S.E.Book
@S_E_Book · 23,100
Telegram ranks this channel #12 of 64 here — alongside 63 others — read 19 September 2026
Интернет-Розыск
@irozysk · 45,743
Telegram ranks this channel #12 of 79 here — alongside 78 others — read 27 August 2026

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

“Пост Лукацкого” (@alukatsky), 38,422 subscribers as measured 7 November 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.