Channel
@nitroteamchannel
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
419subscribers
-4 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001364771108 |
|---|---|
| Type | Channel |
| Username | @nitroteamchannel |
| Created | 10 May 2019 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/nitroteamchannel |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 22:43 | 419 | -4 |
| 6 Aug 2026, 19:31 | 423 | no change |
| 6 Aug 2026, 09:40 | 423 | first reading |
20 posts held, back to 17 February 2021 — 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 pageof 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 6 December 2022. An engagement rate over an empty window would be a number about nothing.
83 reactions across 8 posts, in 4 distinct kinds. The most used accounts for 60.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 50 | 60.2% | |
| 🔥 | 31 | 37.3% | |
| ❤ | 1 | 1.20% | |
| 😱 | 1 | 1.20% |
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 8 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 83reactions 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 17 February 2021 to 6 December 2022, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Наш исследователь @claunch3r обнаружил XSS уязвимость CVE-2022-44153 в программном обеспечении Rapid SCADA 5.8.4. При XSS уязвимости, злоумышленнику удается внедрить на страницу JavaScript-код, который не был предусмотрен разработчиками. С помощью XSS уязвимостей злоумышленник может украсть файлы cookie или другие конфиденциальные данные, создать ложную форму авторизации, внедрить вирусный JavaScript код и другие вр…
👍14🔥11❤1😱1
Обнаружил SSRF-уязвимость в плагине Tumbler для XFCE, которая работает по умолчанию. Если кратко, суть в том, что при открытии директории с m3u8-файлом с расширением .mp4 (работает и для .mp3, .avi, .mpg, etc.) можно отправлять любой GET-запрос на любой сервер. Работает в последней версии Kali Linux, Debian XFCE, и скорее всего в любом другом дистрибутиве Linux с XFCE на борту. Но большую опасность, наверное, несет …
👍10🔥2
Open SysConf 2022 Уже в Октябре! Привет, мы готовим новую - четвертую ежегодную встречу Open SysConf'22. Уже точно есть: — Три доклада — Собрано половина бюджета — Место, дата и время встречи - Обновленный сайт sysconf.io Обычно у большинства людей обстоятельства складываются таким образом, что вечно что-то мешает заняться спортом, сделать доклад, поучаствовать в конфе, мешают обычно работа, откладывание за завтра…
🔥5
Написали заметку про что такое CVE и как его получить: https://telegra.ph/cve-publication-06-06 @nitroteamchannel
👍4🔥4
Во время стажировки в нашей компании, студенты нашли множественные уязвимости в LibreHealth: Broken Access Control (CVE-2022-31496), Cross-Site Scripting (CVE-2022-31492, CVE-2022-31493, CVE-2022-31494, CVE-2022-31495, CVE-2022-31497, CVE-2022-31498). Имена наших героев: Alibek Akhmetov, Bakdaulet Zhaksylyk, Daniyar Absadykov, Amir Askarov, Gaukhar Uzakbay. Подробная информация по багам и по временному исправлению:…
👍15
Наш исследователь обнаружил в open-source системе для медицинских организаций LibreHealth EHR 2.0.0 несколько уязвимостей: одна SQL-инъекция и множественные XSS. Были присвоены следующие идентификаторы: CVE-2022-29938, CVE-2022-29939, CVE-2022-29940. Так как разработчики системы переходят на совершенно новую кодовую базу, для них неактуально исправлять эти уязвимости. Поэтому можно сказать, что это зиродеи. Подроб…
🔥9👍5
Подкаст с B4TR - NitroTeam | PODCAST | PEOPLE | CYBERSECURITY | CODEBY | INFOSEC | Всем привет! Герой нашего подкаста - Тютеев Батыржан! Директор NitroTeam. Компания NitroTeam основана в 2018 году, но объединяет специалистов со стажем более 10 лет в сфере информационной безопасности. Наши специалисты по праву заслужили репутацию экспертов международного уровня и имеют большой опыт в вопросах защиты банков, телеком…
👍1
BLD DNS - Обновление в сторону скорости и безопасности. Краткий отчет. Уже почти, как полгода открытый превентивный DoT/DoH BLD DNS сервис бесплатно приносит пользу блокируя малварные, фишинговые, трекинговые и рекламные домены, экономя трафик, время и мозговые ресурсы своим пользователям. За это время были заблокировано множество фишинговых кампаний (типа franken-phish), малварных и рамсомварных компаний (типа Peg…
https://www.zakon.kz/6004927-nado-byt-trebovatelnym-k-sebe-sovety-kazakhstantsam-ot-belogo-khakera.html #standoff #infosec #phdays #ctf #codeby #nitroteam @nitroteamchannel
Мы победили в третий раз подряд на The Standoff 365! #standoff #infosec #phdays #ctf #codeby #nitroteam @nitroteamchannel
Компания Nitro Team первая в Казахстане получила лицензию CERT по новым требованиям регулятора. Теперь мы официально имеем право предоставлять услуги в области информационной безопасности на территории Казахстана. Для нас это большое событие.
https://habr.com/ru/post/566400/
Showing the 12 most recent of 20 posts we hold for @nitroteamchannel. 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.
Citation-graph rank — 594,926 of 1,350,102entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
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.
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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“NitroTeamChannel” (@nitroteamchannel), 419 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/nitroteamchannel.
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.