Telegram RegisterThe public register of Telegram
Telegram profile photo for Порвали два трояна

Channel

Порвали два трояна

@kasperskyb2b

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry

9,480subscribers

+79 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001336699696
TypeChannel
Username@kasperskyb2b
DescriptionПро ИБ в бизнесе, промышленности и многом другом 💼 Главный канал Kaspersky: @kasperskylab_ru Связь @KasperskyCrew
Created22 June 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live14 November 2026
Measurements held26
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/kasperskyb2b

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

9,4009,4809,4406 August 2026 — 9,401 subscribers6 August 2026 — 9,401 subscribers6 August 2026 — 9,402 subscribers9 August 2026 — 9,406 subscribers11 August 2026 — 9,405 subscribers14 August 2026 — 9,406 subscribers18 August 2026 — 9,400 subscribers21 August 2026 — 9,404 subscribers24 August 2026 — 9,402 subscribers27 August 2026 — 9,407 subscribers30 August 2026 — 9,404 subscribers2 September 2026 — 9,405 subscribers12 September 2026 — 9,406 subscribers29 September 2026 — 9,410 subscribers6 October 2026 — 9,420 subscribers13 October 2026 — 9,423 subscribers15 October 2026 — 9,426 subscribers18 October 2026 — 9,434 subscribers22 October 2026 — 9,439 subscribers26 October 2026 — 9,441 subscribers29 October 2026 — 9,442 subscribers31 October 2026 — 9,439 subscribers3 November 2026 — 9,437 subscribers6 November 2026 — 9,436 subscribers9 November 2026 — 9,461 subscribers14 November 2026 — 9,480 subscribers6 August 202614 November 2026
26 measurements spanning 101 days, net +79. 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 9,388–9,492 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 26
Measured (UTC)SubscribersChange
14 Nov 2026, 23:119,480+19
9 Nov 2026, 17:499,461+25
6 Nov 2026, 13:349,436-1
3 Nov 2026, 13:579,437-2
31 Oct 2026, 23:299,439-3
29 Oct 2026, 09:299,442+1
26 Oct 2026, 00:389,441+2
22 Oct 2026, 14:099,439+5
18 Oct 2026, 22:209,434+8
15 Oct 2026, 21:099,426+3
13 Oct 2026, 07:009,423+3
6 Oct 2026, 15:579,420+10
29 Sept 2026, 17:399,410+4
12 Sept 2026, 01:209,406+1
2 Sept 2026, 07:189,405+1
30 Aug 2026, 06:089,404-3
27 Aug 2026, 10:269,407+5
24 Aug 2026, 13:439,402-2
21 Aug 2026, 00:359,404+4
18 Aug 2026, 03:329,400first reading

Engagement

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

ERR · 30 days
18.5%
avg views ÷ 9,480 subscribers
Avg views / post
1,750
22 posts measured
Reaction rate
0.728%
reactions ÷ views · ER floor
Posts in window
22
of 63 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 16 November 2026
Posts held63 (14 July 2026 – 16 November 2026)
Views total38,590
Reactions total281
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 00:52 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
≈1,030
Videos
≈108
Links
≈1,610

Lifetime counters from Telegram’s own channel header, read 17 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
40s
Average length
40s

Measured directly from 1 video 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

690 reactions across 58 posts, in 15 distinct kinds. The most used accounts for 35.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥24335.2%
👍16423.8%
👏9313.5%
🤯578.26%
❤395.65%
😁375.36%
😱243.48%
💯101.45%
🤔71.01%
🌚40.58%
👎40.58%
😍30.435%
🤣30.435%
💩10.145%
🤩10.145%

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

Measured over the 63 most recent posts we hold, published 14 July 2026 to 16 November 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

Telegram’s own ‘edited’ marker: 2 of 22 posts held from the last 30 days (9.09%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

16 Nov 2026, 07:33 UTC605 views9 reactionsread 17 November 2026

🔥 Ещё один телеком-шпион, Citrus ransomware, жертвы Php2Shell и другие исследования APT за неделю 🔻Анализ TTPs группировки BlackNevas. Не эксплуатируя ни одной уязвимости, злоумышленники вывели из строя всю VMware-инфраструктуру жертвы, включая резервные копии. С помощью учёток с Windows-хостов они получили доступ к vCenter и включили SSH на ESXi-хостах через Host Profiles. 🟢Разбор активностей SilentAir — ранее неи…

👍4🔥3👏2

13 Nov 2026, 15:46 UTC823 views11 reactionsread 17 November 2026

❗️ Более 60 тысяч репозиториев могут оказаться под ударом в результате масштабного взлома на GitHub Последствия могут затронуть не только разработчиков, но и пользователей ПО, а также и госструктры зарубежных стран. Как действовали злоумышленники: 🔴получали доступ через запросы на изменение кода, а затем внедряли вредоносный скрипт в процессы GitHub Actions; 🔴скрипт собирал пароли, ключи доступа и токены; 🔴с помощь…

🔥4🤯4🌚3

13 Nov 2026, 10:02 UTC982 views9 reactionsread 17 November 2026
Photo

🟢 Просто о ClickFix Хотя атаки ClickFix уже приняли масштаб эпидемии, многие пользователи по-прежнему не знают об этой угрозе. Между тем, скучная просьба «пройти капчу» или «установить Claude Code одной строкой» может приводить и к запуску инфостилеров, и к атакам вымогателей. Техника настолько убедительна, что её взяли на вооружение буквально все — от мелких киберпреступников до серьёзных APT. Используйте наши кар…

🔥5👍2👏1💯1

12 Nov 2026, 09:34 UTC≈1,130 views10 reactionsread 17 November 2026
Photo

🏭 Киберфизические атаки на современный склад Скомпрометированный сканер штрихкодов или принтер этикеток — легко достижимая и эффективная точка проникновения в ИТ-инфраструктуру современного склада, позволяющая злоумышленникам сорвать отгрузки даже без развёртывания ransomware. При анализе безопасности складской инфраструктуры эксперты «Лаборатории Касперского» продемонстрировали, как оборудование на складе, которо…

🔥6❤2👍1💯1

11 Nov 2026, 07:34 UTC≈1,200 views18 reactionsread 17 November 2026

🪲 Ноябрьский вторник патчей: снова 1000+ Microsoft снова разразилась монструозным пакетом обновлений для своих продуктов, но до рекорда октября не дотянула — в обновление вошли «всего» 1235 бага. Лишь один эксплуатируется вживую, и ни один не был разглашён до выпуска патчей. Критических дефектов 66, из них 48 приводят к RCE, а 15 — к повышению привилегий. Среди общего объёма уязвимостей абсолютно доминируют EoP (53…

🔥8👍5💯3❤2

10 Nov 2026, 14:29 UTC≈1,120 views8 reactionsread 17 November 2026

📌 Уроки кибериммунитета для ИИ-агентов Применение подхода secure by design встречается в разработке ПО нечасто. Все мы знаем, как в итоге это отражается на качестве ПО. С опозданием в два десятка лет этот подход начали рекомендовать агентства по кибербезопасности, но внедрение всё равно идёт довольно медленно. Но есть и хорошие новости! Сейчас — самое время украсть пару страниц из учебника по конструктивной безопа…

👍4🔥3👏1

10 Nov 2026, 10:13 UTC≈1,130 views16 reactionsread 17 November 2026

🟢 Защита от DDoS — наглядно По исследованию «Лаборатории Касперского», продолжается рост числа DDoS-атак. В первой половине 2026 года их количество выросло на 56% год к году. Растёт не только количество, но и сложность угроз. Около трети атак проводятся одновременно на уровнях L3/L4 и L7, затрагивая всю автономную сеть жертвы и значительно усложняя реагирование. Эффективно противостоять современным атакам позволяе…

🔥6❤4👍4👏2

9 Nov 2026, 07:59 UTC≈1,160 views13 reactionsread 17 November 2026

Интересные исследования APT и новости ИБ за неделю 🟣Технический разбор вторжений вымогателей Storm-2603, где через уязвимость ToolShell устанавливали примечательный бесфайловый веб-шелл, который существовал только в памяти ASP.NET runtime. Злоумышленники повышали привилегии при помощи адаптированной техники EfsPotato, злоупотребляли уязвимой сборкой Velociraptor и пытались отключить EDR с помощью BYOVD, прежде чем р…

🔥6👏4❤1👍1🤯1

6 Nov 2026, 12:04 UTC≈8,310 views15 reactionsread 17 November 2026
Photo

🔥 Видео и презентации с сотен ИБ-конференций без регистрации и SMS Если вы не поехали в этом или прошлом году на Virus Bulletin, SAS, KazHackStan, CCC, или иную ИБ-конференцию, крупную или мелкую — забирайте в закладки этот сайт. Не знаем, кто его поддерживает, но на infocon.org выложены видео и материалы с двух сотен конференций, большей частью за последние годы. Но, например, Virus Bulletin аж с 1991 (тогда видео …

🔥10👏4👍1

5 Nov 2026, 09:33 UTC≈1,500 views10 reactionsread 17 November 2026

🧊 Подводная часть айсберга уязвимостей Во всей истории про «апокалипсис патчей» есть интересный и очень неудобный для крупных бизнесов аспект. Дефектов стало настолько много, что вендоры всё чаще устраняют их, не назначая CVE. В результате баги становятся «невидимы» для типового корпоративного ИБ-конвейера. Отказ назначать CVE может проявляться в разных формах — от risk-based disclosure, как в Cisco вежливо назвал…

🔥6👍2🤯1😱1

3 Nov 2026, 08:31 UTC≈1,530 views16 reactionsread 17 November 2026
Photo

👀 Что делать с опасными сертификатами из цепочки УЦ eMudhra Талантливые люди из индийского УЦ eMudhra умудрились выпустить в 2025 году восемь сертификатов промежуточных CA, приватными ключами в которых служили числа от 4 до 237. Сертификаты, выпущенные на их основе, не так уж многочисленны и преимущественно использовались одним (крупным) клиентом, но вот MITM-атаки с их помощью может проводить любой желающий. 17 окт…

😁7🔥4👏3👍2

2 Nov 2026, 08:11 UTC≈2,940 views16 reactionsread 16 November 2026

ИИ-агенты на службе атакующих: инцидент с участием CyberstrikeAI Эксперты Лаборатории Касперского обнаружили вредоносную кампанию, в которой образовательные организации в странах Африки и Латинской Америки были атакованы с помощью С2-агентов, управляемых полуавтономным фреймворком CyberStrikeAI. Злоумышленники автоматизировали значительную часть цепочки атаки, делегировав языковым моделям разведку в сети после перв…

🔥8👏3🤯3👍2

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

@kasperskyb2b 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
8 August 2026
Most recent edit
12 August 2026

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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

Mentions

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

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.

Kaspersky
@kasperskylab_ru · 29,326
Telegram ranks this channel #3 of 96 here — alongside 95 others — read 9 September 2026
Борьба с киберпреступностью | F6
@f6_cybersecurity · 22,367
Telegram ranks this channel #17 of 85 here — alongside 84 others — read 21 September 2026
Листок бюрократической защиты информации
@bureaucraticsecurity · 19,141
Telegram ranks this channel #26 of 98 here — alongside 97 others — read 4 October 2026
SecAtor
@true_secator · 42,222
Telegram ranks this channel #26 of 78 here — alongside 77 others — read 29 August 2026
КиберДед official
@deedcoin_club · 23,016
Telegram ranks this channel #27 of 84 here — alongside 83 others — read 25 September 2026
Positive Technologies
@Positive_Technologies · 29,648
Telegram ranks this channel #27 of 87 here — alongside 86 others — read 9 September 2026
Хакер — Xakep.RU
@xakep_ru · 40,322
Telegram ranks this channel #27 of 83 here — alongside 82 others — read 30 August 2026
Пост Лукацкого
@alukatsky · 38,486
Telegram ranks this channel #32 of 89 here — alongside 88 others — read 31 August 2026
Mycroft Intelligence
@mycroftintel · 20,655
Telegram ranks this channel #35 of 76 here — alongside 75 others — read 25 September 2026
Отдел К: IT-технологии, кибербезопасность
@cyber_cabb · 81,735
Telegram ranks this channel #35 of 94 here — alongside 93 others — read 18 August 2026
SecurityLab.ru
@SecLabNews · 86,623
Telegram ranks this channel #35 of 90 here — alongside 89 others — read 18 August 2026
Russian OSINT
@Russian_OSINT · 48,579
Telegram ranks this channel #37 of 82 here — alongside 81 others — read 26 August 2026
Пакет Безопасности
@package_security · 34,225
Telegram ranks this channel #49 of 82 here — alongside 81 others — read 4 September 2026
Positive Hack Days Media
@positivehackmedia · 30,000
Telegram ranks this channel #57 of 88 here — alongside 87 others — read 6 September 2026
Этичный Хакер
@hack_less · 242,543
Telegram ranks this channel #59 of 81 here — alongside 80 others — read 12 August 2026

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

“Порвали два трояна” (@kasperskyb2b), 9,480 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/kasperskyb2b.

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.