РАЗДЕЛ: #Мероприятия Международная конференция на тему безопасности платежей "#PAYMENTSECURITY 2026" В этом году конференция #PAYMENTSECURITY пройдет в новой локации — в историческом центре Нижнего Новгорода. Вас ждут: • Экспертные доклады на тему ИБ в финтехе. • Живой диалог с ведущими экспертами ИБ и ИТ. • Воркшоп по практической информационной безопасности Practical Security Village от пентестеров Deiteriy La…

Channel
LIFE ИБ
@lifeinfsec
On this record: Growth · Engagement · Reactions · Advertising · Posts · Citations · Telegram's recommendations · Cite this entry
545subscribers
+5 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001364711578 |
|---|---|
| Type | Channel |
| Username | @lifeinfsec |
| Created | Between 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 9 September 2026 |
| On Telegram | t.me/lifeinfsec |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 00:22 | 545 | +1 |
| 30 Aug 2026, 21:43 | 544 | +1 |
| 23 Aug 2026, 18:57 | 543 | +2 |
| 15 Aug 2026, 14:38 | 541 | +1 |
| 8 Aug 2026, 03:48 | 540 | no change |
| 7 Aug 2026, 19:10 | 540 | first reading |
Engagement
20 posts held, back to 7 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 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
2 reactions across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 100.0% |
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 3 of the 20 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 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 7 July 2026 to 3 August 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
- 5.00%
- 1 of 20 posts carry an ad marker
- Regulatory tokens
- 1
- posts carrying an erid · 1 distinct token
- Median views · ads
- 76.0
- over 1 measured post
- Median views · rest
- 106
- over 19 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.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| 2VfnxvkDZjH | 1 | 16 July 2026 | 16 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 20 most recent posts we hold, published 7 July 2026 to 3 August 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
💻 В Ставрополе программистов и сотрудников АЗС осудили за внедрение 🦠вредоносного комплекса для недолива топлива В Ставрополе вынесен приговор участникам схемы, которые использовали вредоносное программное обеспечение для хищения топлива у клиентов автозаправочных станций. В группу входили программисты, сервисные инженеры, менеджеры и операторы АЗС. На скамье подсудимых находились 14 человек, в том числе обвиняемый …
В связи с распространением ложной информации о произошедшей утечке данных пользователей с ресурсов КриптоПро сообщаем следующее. С момента первого появления информации об утечке из баз данных компании нашими специалистами было проверено значительное количество образцов появившихся в открытом доступе данных, связываемых с данной утечкой. В отношении всех проверенных данных сообщаем, что на серверах КриптоПро они отс…
Архитектор по информационной безопасности, системный интегратор АСС АйТи ЗП: 400 000 + рублей gross Формат: гибрид Локация: Москва Обязанности: • Выявление потребностей заказчика, анализ требований и разработку оптимальной архитектуры решения, выявление технических рисков (pre-sale); • Проектирование и детализация архитектуры систем защиты; • Разработка и согласование проектной документации, подготовка технико-ком…
РАЗДЕЛ: #Стажировка TS Solution: Стажировка "Сетевая безопасность" Команда TS Solution ведёт набор на оплачиваемую стажировку. Обучение будет проходить в два этапа. Пройди обучение под наставничеством опытных инженеров TS Solution по следующему треку: • Основы сетевых технологий • Архитектура корпоративных сетей • Траблшутинг и анализ трафика • Основы виртуализации • Азы КиберБезопасности • Архитектура защищенны…
РАЗДЕЛ: #Мероприятия BI.ZONE: Вебинар "Управление внешним периметром холдинга: активы, риски, ответственность" В группах компаний ответственность за внешний периметр часто распределена: часть активов находится в зоне контроля головного офиса, часть — в локальной ответственности дочерних структур. Из-за этого даже при выстроенных процессах кибербезопасности у головной компании не всегда есть полная видимость актив…
🔐 Приглашаем на вебинар "Secret Disk для Linux версия 2.3: новые возможности, преимущества и практика внедрения" 📌 Дата: 23 июля 2026 г. (четверг) 📌 Время: 11:00 – 12:30 (МСК) На вебинаре расскажем: ➡️Коротко о продукте и его базовых кейсах применения ➡️Новые функции Secret Disk как часть общей концепции защиты информации на рабочих станциях пользователей ➡️Использование Secret Disk для выполнения требований регул…
🏭 Как сегодня защитить промышленную КИИ, если производство нельзя остановить, оборудование нельзя заменить, а проверки уже на пороге? Именно об этом поговорим 23 июля в 10:00 (МСК) на отраслевом практикуме «КИИ в промышленности». Разберем тему сразу с трех сторон: 🟡 Заказчик (CISO) — как принимать решения внутри предприятия, когда бюджет, производство и безопасность постоянно конфликтуют. 🟡 Интегратор — соответств…
РАЗДЕЛ: #Мероприятия 3Side: Вебинар "Киберинцидент как бизнес-риск: реальные кейсы и выводы" За последний год российские компании столкнулись с десятками тысяч кибератак. Некоторые приводят к остановке производства, потере доступа к корпоративным системам, утечкам данных и серьёзным финансовым потерям. При этом большинство успешных атак развивается по схожим сценариям, а их последствия можно существенно снизить, …
🦠Разработчики 7-Zip исправили опасную RCE-уязвимость в декодере XZ В популярном архиваторе 7-Zip версии 26.02 устранена уязвимость удалённого выполнения произвольного кода, которая отслеживается под идентификатором CVE-2026-14266. Она получила оценку 7,0 балла по шкале CVSS. Проблему обнаружил ИБ-исследователь компании Lunbun LLC Лэндон Пэн, а информация о ней была опубликована в рамках инициативы Zero Day Initiativ…
Posted without readable text
❤2
РАЗДЕЛ: #Мероприятия К2 Кибербезопасность: Вебинар "Безопасная разработка" Пока одни считают AppSec тормозом для релизов, другие уже не представляют без него разработку. В новом выпуске Deep Patch разберем: • стоит ли платить за коммерческие решения или можно жить на open source • как выбрать между SAST, SCA и DAST и не утонуть в количестве инструментов • Security Champions VS AppSec-команда: какой подход продук…
Showing the 12 most recent of 20 posts we hold for @lifeinfsec. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
@anti_malware · 13,1512 postsRussian OSINT
@Russian_OSINT · 47,5812 postsАладдин Р.Д.
@aladdinrd · 5181 postКод ИБ: ИИ & КиберБезопасность
@codeibnews · 6,8561 postНовости КриптоПро
@cryptopro_news · 3,6491 postESCalator
@ptescalator · 8,0231 postRuSecJobs Channel
@RuSecJobs · 11,2801 postSecurityLab.ru
@SecLabNews · 84,1101 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 1 registered channel — 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.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
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.
@involta · 34,269
Telegram ranks this channel #47 of 89 here — alongside 88 others — read 3 September 2026
This channel appears in 1 seed channel's Telegram-generated recommendation list 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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“LIFE ИБ” (@lifeinfsec), 545 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/lifeinfsec.
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.