Telegram RegisterThe public register of Telegram
Telegram profile photo for Kaspersky

Channel

Kaspersky

@kasperskylab_ru

Verified by Telegram

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

28,831subscribers

-304 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001120211852
TypeChannel
Username@kasperskylab_ru
DescriptionКибербез с человеческим лицом. Главный канал «Лаборатории Касперского». Канал техподдержки: https://t.me/kl_support/ Регистрация в РКН: https://gosuslugi.ru/snet/67a33d9224c8ba6dca898edd Вопросы и предложения @KasperskyCrew
Created9 October 2017 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live27 September 2026
Measurements held36
Confirmed unchanged1 time, most recently 27 September 2026
On Telegramt.me/kasperskylab_ru

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 97% 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

28,83129,13528,9836 August 2026 — 29,135 subscribers6 August 2026 — 29,135 subscribers6 August 2026 — 29,132 subscribers7 August 2026 — 29,113 subscribers8 August 2026 — 29,109 subscribers9 August 2026 — 29,093 subscribers10 August 2026 — 29,080 subscribers12 August 2026 — 29,069 subscribers12 August 2026 — 29,061 subscribers14 August 2026 — 29,058 subscribers16 August 2026 — 29,066 subscribers17 August 2026 — 29,051 subscribers18 August 2026 — 29,050 subscribers19 August 2026 — 29,047 subscribers20 August 2026 — 29,043 subscribers21 August 2026 — 29,035 subscribers22 August 2026 — 29,040 subscribers24 August 2026 — 29,026 subscribers25 August 2026 — 29,020 subscribers26 August 2026 — 29,009 subscribers27 August 2026 — 29,000 subscribers28 August 2026 — 28,987 subscribers29 August 2026 — 28,985 subscribers30 August 2026 — 28,982 subscribers31 August 2026 — 28,974 subscribers1 September 2026 — 28,959 subscribers2 September 2026 — 28,954 subscribers4 September 2026 — 28,962 subscribers6 September 2026 — 28,948 subscribers9 September 2026 — 28,922 subscribers12 September 2026 — 28,908 subscribers13 September 2026 — 28,890 subscribers15 September 2026 — 28,877 subscribers17 September 2026 — 28,865 subscribers19 September 2026 — 28,858 subscribers27 September 2026 — 28,831 subscribers6 August 202627 September 2026
36 measurements spanning 52 days, net -304. 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 28,785–29,181 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 36
Measured (UTC)SubscribersChange
27 Sept 2026, 01:3728,831-27
19 Sept 2026, 17:3628,858-7
17 Sept 2026, 09:1528,865-12
15 Sept 2026, 10:2128,877-13
13 Sept 2026, 19:0028,890-18
12 Sept 2026, 00:3828,908-14
9 Sept 2026, 18:0028,922-26
6 Sept 2026, 09:4028,948-14
4 Sept 2026, 02:0028,962+8
2 Sept 2026, 12:4428,954-5
1 Sept 2026, 12:5328,959-15
31 Aug 2026, 09:4928,974-8
30 Aug 2026, 09:5828,982-3
29 Aug 2026, 10:5528,985-2
28 Aug 2026, 14:1928,987-13
27 Aug 2026, 12:0229,000-9
26 Aug 2026, 13:1229,009-11
25 Aug 2026, 12:4329,020-6
24 Aug 2026, 12:4329,026-14
22 Aug 2026, 20:1629,040first reading

Engagement

111 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 76 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
6.89%
avg views ÷ 28,831 subscribers
Avg views / post
1,990
48 posts measured
Reaction rate
1.20%
reactions ÷ views · ER floor
Posts in window
48
of 111 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 29 September 2026
Posts held111 (31 July 2026 – 29 September 2026)
Views total95,317
Reactions total1,148
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Sept 2026, 11:13 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
≈4,510
Videos
≈273
Links
≈4,150

Lifetime counters from Telegram’s own channel header, read 29 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
10m 27s
Average length
45s

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

2,320 reactions across 109 posts, in 11 distinct kinds. The most used accounts for 26.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤62126.8%
🔥59225.5%
👍32514.0%
👾24110.4%
👏23410.1%
🤯1948.36%
🤩522.24%
🥰351.51%
😁150.647%
🤡80.345%
👎30.129%

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 111 of the 111 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 2,351 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 111 most recent posts we hold, published 31 July 2026 to 29 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.

Advertising

Ad load
0.901%
1 of 111 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
2,260
over 1 measured post
Median views · rest
2,270
over 110 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2RanykMWtWX131 July 202631 July 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 111 most recent posts we hold, published 31 July 2026 to 29 September 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

29 Sept 2026, 09:59 UTC885 views19 reactionsread 29 September 2026
Photo

❗️ Эксперты «Лаборатории Касперского» обнаружили новую легенду мошенников – они присылают сообщения якобы от соседей 🔻Как это работает: 🔴Схема начинается с сообщения в мессенджере. «Сосед» обращается к человеку по реальному имени, называет номер квартиры и предупреждает о подозрительном мужчине у двери, который что-то снимает на камеру. 🔴Затем приходит ссылка на якобы видео с этим мужчиной и вопрос: «Вы его знаете…

🔥9🤯6👾3❤1

29 Sept 2026, 08:01 UTC991 views13 reactionsread 29 September 2026
Photo

🐺Предательские расширения для браузера Установили расширение для браузера из официального магазина и уверены, что оно безопасно? Зря! Даже если в момент публикации ваш любимый инструмент был легитимным, после очередного обновления он вполне мог стать вредоносным. Злоумышленники нередко используют популярные расширения в качестве «троянских коней». Для нормальной работы таким программам часто нужен доступ к информац…

👏6👍4❤2🤯1

28 Sept 2026, 14:35 UTC≈1,560 views20 reactionsread 29 September 2026
Video

Опять звонят по видео, а вы не понимаете, настоящий это собеседник или дипфейк? Разбираем вместе с Дмитрием Аникиным, руководителем направления исследования данных, по каким признакам можно определить, что на связи дипфейк⬆️ А заодно напоминаем: даже если вы понимаете, что говорите с человеком, но он вас торопит, пугает, просит назвать одноразовые коды или присылает ссылки в мессенджерах — скорее всего это мошенник…

❤10🤯4🔥3👏2👾1

28 Sept 2026, 09:01 UTC≈1,620 views13 reactionsread 29 September 2026
Photo

📊Скрытые угрозы: почему инциденты остаются незамеченными годами Внедрение современных ИБ-решений — важный шаг, но сам по себе он не гарантирует полную сохранность корпоративных данных. Из-за нехватки ресурсов или профильных специалистов компании нередко вынуждены полностью полагаться на автоматику. Однако подход «настроил и забыл» играет на руку киберпреступникам: многие инциденты остаются незамеченными на протяжени…

👏4🤯3❤2👾2🔥2

27 Sept 2026, 17:35 UTC≈1,690 views18 reactionsread 29 September 2026
Photo

Дайджест киберновостей за прошедшую неделю ➡️ 🟣Новая критическая уязвимость в ядре WordPress (CVE-2026-87902) уже активно эксплуатируется в реальных атаках. Подробности, полезные ссылки и советы — в материале Kaspersky Daily. 🟣Группировка Toy Ghouls расширила свой арсенал самописным бэкдором — зловредом для установления контроля над заражёнными устройствами. Подробный разбор, а также индикаторы компрометации — в на…

👍7👾5🔥4❤2

26 Sept 2026, 09:34 UTC≈1,880 views21 reactionsread 29 September 2026

А теперь возвращаемся к «Битве Роботов»! До отборочных осталось совсем немного времени — они пройдут с 6 по 10 октября на Кинозаводе «Москино» — так что пора подготовиться, чтобы понимать происходящее! ▶️Что это вообще такое? «Битва роботов» — международный чемпионат, где роботы, автономные или дистанционно управляемые командами от 1 до 5 человек, сражаются на ринге. ▶️Все команды выступают в одной категории? Кате…

🔥7❤5👍5👾4

25 Sept 2026, 17:22 UTC≈2,210 views20 reactionsread 29 September 2026
Photo

❗️Новая критическая уязвимость в ядре WordPress (CVE-2026-87902) уже активно эксплуатируется в реальных атаках 22 сентября WordPress выпустил обновление, которое её закрывает, но злоумышленники отреагировали очень быстро — первые попытки эксплуатации уязвимости были замечены уже через несколько часов после публикации патча. Из-за уязвимости CVE-2026-87902 атакующий может составить запрос к WordPress таким образом, …

❤7👾7🤯6

25 Sept 2026, 11:35 UTC≈2,140 views28 reactionsread 29 September 2026
Video

Продолжаем деловой осенний сезон на международных мероприятиях: вот так ярко прошел GISEC Global 2026 для «Лаборатории Касперского»! Дискуссии, встречи, переговоры, подписания, неформальные обсуждения, настоящее и будущее кибербезопасности — три дня пролетели как один! Смотрим атмосферное видео и готовимся к следующим мероприятиям 🔥

👾9🔥9👍6👏3❤1

24 Sept 2026, 14:15 UTC≈2,290 views25 reactionsread 29 September 2026
Photo

В свежем #kaspersky_securityweek: 🔵Эксперты «Лаборатории Касперского» изучили новое вредоносное ПО MovieReaper, которое распространяется на популярных торрент-трекерах под видом фильмов, игр и других файлов. Зловред содержит целый ряд мер для защиты от обнаружения — например, адрес резервного командного сервера он получает из блокчейна Solana. В результате успешного заражения злоумышленники получают полный удалённый…

🤯9🔥7👾5❤2👍2

24 Sept 2026, 08:29 UTC≈2,190 views22 reactionsread 29 September 2026
Photo

🙀 Новые инструменты группировки Hacking Cat Группировка Hacking Cat (или «Хакерский кiт») известна атаками на российские компании с начала 2024 года. Более года злоумышленники ограничивались утечками данных и подменой содержимого сайтов, но летом прошлого года они сменили профиль: теперь их цель — шифрование и полное уничтожение данных. Наши эксперты изучили обновлённый арсенал группировки: 🔴Gorilla RAT — троянец с…

🔥9🤯8❤3👾2

23 Sept 2026, 13:59 UTC≈2,110 views24 reactionsread 29 September 2026
Photo

🔨 Новый виток развития атаки типа Rowhammer Канадские исследователи кибербезопасности представили GPUThor, новый метод атак на графические ускорители. Возможность таких атак демонстрировалась и раньше, но старые способы приносили скромные результаты: на промышленных видеоускорителях эффективность была низкой. Новый же метод оказался результативнее в 7–23 тысячи раз. При помощи GPUThor учёным удалось добиться двойн…

👾11🤯6🔥5❤2

23 Sept 2026, 10:44 UTC≈2,290 views25 reactionsread 29 September 2026
Forwarded from @Kaspersky4mediaPhoto

🏆«Лаборатория Касперского» выступила партнёром компетенции «Конструктивная безопасность автономных транспортных систем» на Чемпионате высоких технологий Компания стала партнёром компетенции «Конструктивная безопасность автономных транспортных систем», заказчиком которой выступило Министерство транспорта России. Чемпионат высоких технологий — это соревнования по компетенциям, отражающим наиболее перспективные и дина…

❤13👍5🔥5👏2

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

@kasperskylab_ru 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
20 August 2026
Most recent edit
27 August 2026

Forward network

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

Mentions

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

Евгений Касперский
@e_kaspersky · 6,535
#1
Карьера в Kaspersky
@kaspersky_career · 8,085
#2
Порвали два трояна
@kasperskyb2b · 9,406
#3
Positive Technologies
@Positive_Technologies · 29,062
#4
Пост Лукацкого
@alukatsky · 37,862
#5
SecurityLab.ru
@SecLabNews · 84,654
#6
BI.ZONE
@bizone_channel · 11,212
#7
Kaspersky4media
@Kaspersky4media · 1,177
#8
SecAtor
@true_secator · 41,748
#9
AM Live
@anti_malware · 13,154
#10
НеКасперский
@NeKaspersky · 16,061
#11
Солар
@solar_security · 6,477
#12
RED Security
@redsecurity_co · 5,194
#13
Техническая поддержка Лаборатории Касперского
@kl_support · 7,555
#14
Солдатов в Телеграм
@soldatov_in_telegram · 2,277
#15
Хакер — Xakep.RU
@xakep_ru · 39,610
#16
Сицебрекс!
@sycebrex · 1,161
#17
Борьба с киберпреступностью | F6
@f6_cybersecurity · 22,318
#18
ESCalator
@ptescalator · 8,127
#19
Похек
@poxek · 16,849
#20
Минцифры России
@mintsifry · 234,926
#21
Топ кибербезопасности Батранкова
@safebdv · 10,019
#22
Резбез
@Rez_in_Bez · 2,648
#23
Positive Events
@PositiveEvents · 6,117
#24
CISOCLUB - кибербезопасность и ИТ
@cisoclub · 7,058
#25
Kaspersky Club
@kasperskyclub · 1,185
#26
Sachok
@CyberSachok · 11,275
#27
Russian OSINT
@Russian_OSINT · 47,701
#28
КИБЕР МЕДИА
@secmedia · 5,902
#29
Social Engineering
@Social_engineering · 125,008
#30
Standoff 365
@standoff_365 · 8,298
#31
Positive Development Community
@POSIdev · 3,186
#32
SOC FORUM | Неделя кибербезопасности
@forumsoc · 2,882
#33
CyberCamp
@CYBERCAMP_ONLINE · 8,666
#34
Мероприятия по ИБ
@InfoBezEvents · 5,653
#35
KasperskyOS
@kosdevs · 1,216
#36
Codeby
@codeby_sec · 37,041
#37
Кибербез образование | cybersecurity-roadmap.ru
@cyber_edu · 6,013
#38
IT's positive investing
@positive_investing · 9,251
#39
ИТ-Пикник
@IT_picnic · 23,126
#40
Евгениально
@naumovaevgeniya · 868
#41
InfoWatch
@infowatchout · 3,153
#42
Хабр
@habr_com · 132,465
#43
Группа Астра
@astragroup · 9,409
#44
Hacker News
@HNews · 7,293
#45
Innostage
@innostage_group · 2,708
#46
Инфосистемы Джет
@jetinfosystems · 6,292
#47
Makrushin
@makrushin · 3,873
#48
YAH
@YAH_Channel · 7,569
#49
Сбер
@sberbank · 741,927
#50
vc.ru
@vcnews · 112,033
#51
Angara Security
@angarasecurity · 1,576
#52
BESSEC
@bessec · 4,751
#53
Cybred
@cybred · 11,118
#54
Yandex Cloud
@yandexcloudnews · 21,888
#55
Integral Security
@integral_security · 1,722
#56
GIS о кибербезопасности
@gis_cybersec · 11,515
#57
Axoft в Эфире
@axoftonair · 3,890
#58
Код ИБ: ИИ & КиберБезопасность
@codeibnews · 6,852
#59
Security Vision
@svplatform · 5,401
#60
OFFZONE
@offzone_moscow · 7,400
#61
Раньше всех. Ну почти.
@bbbreaking · 1,974,402
#62
Управление Уязвимостями и прочее
@avleonovrus · 12,122
#63
Эксплойт
@exploitex · 2,048,279
#64
Новости Москвы
@moscowmap · 2,668,820
#65
Утечки информации
@dataleak · 119,401
#66
Код.ру
@d_code · 406,147
#67
Rozetked
@rozetked · 672,965
#68
Кибервойна
@cyberguerre · 8,790
#69
purple shift
@purpleshift · 3,037
#70
Positive Hack Days Media
@positivehackmedia · 30,694
#71
Это Саша
@svoyapolosa · 300
#72
Бэкдор
@whackdoor · 1,590,187
#73
infosec
@it_secur · 61,761
#74
Банкста
@banksta · 438,371
#75
РБК. Новости. Главное
@rbc_news · 905,528
#76
RuSecJobs Channel
@RuSecJobs · 11,387
#77
CyberSquatting RU Alerts
@CyberSquattingChannel · 2,459
#78
Яндекс
@yandex · 606,530
#79
Багхантер
@bughunter_circuit · 3,514
#80
ИнфоТеКС
@infotecs_official · 6,442
#81
BI.ZONE Bug Bounty
@bizone_bugbounty · 6,620
#82
Вакансии в ИБ | infosec
@infosec_work · 15,755
#83
README.hta
@s3Ch1n7 · 3,211
#84
ТАСС
@tass_agency · 567,568
#85
k8s (in)security
@k8security · 13,151
#86
ГосСОПКА Центр
@sopkacentr · 16,415
#87
R-Vision
@rvision_pro · 2,495
#88
llm security и каланы
@llmsecurity · 2,039
#89
Cybersecurity memes off
@cybersecurity_memes_off · 1,700
#90
CNews.ru
@CNewsDaily · 15,674
#91
лидер мнений среди удобрений
@lider · 176,821
#92
Mash
@mash · 3,110,586
#93
БарKas
@barkas_moscow · 1,035
#94
БДУ ФСТЭК России
@bdufstecru · 10,589
#95
Information Security Memes
@infosecmemes · 9,677
#96

Read from Telegram’s recommendation API, most recently 9 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Positive Technologies
@Positive_Technologies · 29,062
Telegram ranks this channel #19 of 87 here — alongside 86 others — read 9 September 2026
Борьба с киберпреступностью | F6
@f6_cybersecurity · 22,318
Telegram ranks this channel #20 of 85 here — alongside 84 others — read 21 September 2026
Хакер — Xakep.RU
@xakep_ru · 39,610
Telegram ranks this channel #40 of 83 here — alongside 82 others — read 30 August 2026
SecurityLab.ru
@SecLabNews · 84,654
Telegram ranks this channel #44 of 90 here — alongside 89 others — read 18 August 2026
Пост Лукацкого
@alukatsky · 37,862
Telegram ranks this channel #48 of 89 here — alongside 88 others — read 31 August 2026
Positive Hack Days Media
@positivehackmedia · 30,694
Telegram ranks this channel #53 of 88 here — alongside 87 others — read 6 September 2026

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

Cite this entry

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

“Kaspersky” (@kasperskylab_ru), 28,831 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/kasperskylab_ru.

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.