Telegram RegisterThe public register of Telegram
Telegram profile photo for ИБ Книга | Библиотека ИБ

Channel

ИБ Книга | Библиотека ИБ

@itbook_library

On this record: Topic · Growth · Engagement · What this channel posts · Advertising · Posts · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry

15,938subscribers

+72 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-1001231020364
TypeChannel
Username@itbook_library
DescriptionТвой пособник в кибербез. Реклама: @workhouse_price https://telega.in/c/itbook_library РКН: https://www.gosuslugi.ru/snet/675c32b1cb5e1e5991ae6d14
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live10 November 2026
Measurements held60
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/itbook_library

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 10 September 2026 and assigned it the closest of 31 fixed categories, at 91% 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

15,81815,98315,900.56 August 2026 — 15,866 subscribers7 August 2026 — 15,868 subscribers9 August 2026 — 15,866 subscribers10 August 2026 — 15,862 subscribers11 August 2026 — 15,860 subscribers12 August 2026 — 15,864 subscribers13 August 2026 — 15,861 subscribers15 August 2026 — 15,860 subscribers16 August 2026 — 15,853 subscribers17 August 2026 — 15,852 subscribers18 August 2026 — 15,848 subscribers19 August 2026 — 15,845 subscribers20 August 2026 — 15,842 subscribers22 August 2026 — 15,839 subscribers24 August 2026 — 15,832 subscribers25 August 2026 — 15,825 subscribers26 August 2026 — 15,820 subscribers27 August 2026 — 15,818 subscribers28 August 2026 — 15,849 subscribers29 August 2026 — 15,863 subscribers30 August 2026 — 15,865 subscribers31 August 2026 — 15,863 subscribers1 September 2026 — 15,872 subscribers3 September 2026 — 15,863 subscribers4 September 2026 — 15,857 subscribers7 September 2026 — 15,845 subscribers10 September 2026 — 15,839 subscribers12 September 2026 — 15,841 subscribers14 September 2026 — 15,840 subscribers16 September 2026 — 15,834 subscribers18 September 2026 — 15,826 subscribers2 October 2026 — 15,825 subscribers7 October 2026 — 15,974 subscribers11 October 2026 — 15,968 subscribers14 October 2026 — 15,963 subscribers15 October 2026 — 15,957 subscribers16 October 2026 — 15,955 subscribers17 October 2026 — 15,959 subscribers18 October 2026 — 15,955 subscribers19 October 2026 — 15,947 subscribers21 October 2026 — 15,950 subscribers22 October 2026 — 15,946 subscribers23 October 2026 — 15,950 subscribers24 October 2026 — 15,952 subscribers25 October 2026 — 15,945 subscribers26 October 2026 — 15,943 subscribers27 October 2026 — 15,935 subscribers28 October 2026 — 15,934 subscribers29 October 2026 — 15,972 subscribers30 October 2026 — 15,979 subscribers31 October 2026 — 15,983 subscribers1 November 2026 — 15,980 subscribers2 November 2026 — 15,967 subscribers3 November 2026 — 15,964 subscribers4 November 2026 — 15,958 subscribers5 November 2026 — 15,957 subscribers6 November 2026 — 15,951 subscribers7 November 2026 — 15,945 subscribers8 November 2026 — 15,942 subscribers10 November 2026 — 15,938 subscribers15,9386 August 202610 November 2026
60 measurements spanning 95 days, net +72. 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 15,793–16,008 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 60
Measured (UTC)SubscribersChange
10 Nov 2026, 00:1115,938-4
8 Nov 2026, 18:4515,942-3
7 Nov 2026, 11:5015,945-6
6 Nov 2026, 12:2415,951-6
5 Nov 2026, 09:2815,957-1
4 Nov 2026, 05:3015,958-6
3 Nov 2026, 03:4615,964-3
2 Nov 2026, 07:0715,967-13
1 Nov 2026, 03:5915,980-3
31 Oct 2026, 03:1015,983+4
30 Oct 2026, 03:1915,979+7
29 Oct 2026, 04:2115,972+38
28 Oct 2026, 05:0015,934-1
27 Oct 2026, 03:1415,935-8
26 Oct 2026, 04:4815,943-2
25 Oct 2026, 06:0515,945-7
24 Oct 2026, 05:1715,952+2
23 Oct 2026, 08:3515,950+4
22 Oct 2026, 11:4415,946-4
21 Oct 2026, 06:4715,950first reading

Engagement

83 posts held, back to 22 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
11.4%
avg views ÷ 15,938 subscribers
Avg views / post
1,820
36 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
36
of 83 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 10 November 2026
Posts held83 (22 July 2026 – 10 November 2026)
Views total65,511
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 06:32 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
≈962
Videos
≈28
Links
≈1,320

Lifetime counters from Telegram’s own channel header, read 11 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.

Advertising

Ad load
1.20%
1 of 83 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
1,790
over 1 measured post
Median views · rest
1,810
over 82 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
2W5zFGuYNaV124 July 202624 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 83 most recent posts we hold, published 22 July 2026 to 10 November 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

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

10 Nov 2026, 19:00 UTC801 viewsread 11 November 2026
Photo

📂 pocindex: поиск PoC и сопоставление оценок уязвимостей Каталог публичных примеров эксплуатации уязвимостей (PoC) из GitHub, Nuclei, ExploitDB, Metasploit и Vulhub. Искать можно по CVE, производителю, продукту или ключевому слову. Позволяет сопоставить критичность по CVSS, оценки EPSS и сведения CISA об эксплуатации уязвимостей в реальных атаках — не только найти PoC, но и посмотреть контекст угрозы. Данные досту…

10 Nov 2026, 16:52 UTC≈1,020 viewsread 11 November 2026
Photo

🔴В 2025 году Россияне заработали 5,3 млрд рублей на арбитраже криптовалют По данным Минфин 32% граждан покинули своё место работы поскольку в среднем уже в первый месяц смогли заработать 250 000 рублей, а через 2-3 месяца с легкостью вышли на семизначные числа. Самое смешное, что лишь 8% россиян что-то слышали об этой профессии хотя все инструкции бесплатно лежат на канале Арбитраж Криптовалют Там объясняют, как и…

10 Nov 2026, 14:00 UTC≈1,080 viewsread 11 November 2026
Photo

📂 XDR: разбираемся по полочкам Что входит в XDR, как работают плейбуки и графы и где применяется ИИ? У «Лаборатории Касперского» вышел новый видеопроект «Удобные ответы про XDR», где эксперты простым языком объясняют, из чего состоит платформа и какую ценность она дает бизнесу. В программе: 🔸 Что такое XDR и как его понимает команда продукта. 🔸 Плейбуки, графы и возможности единой платформы. 🔸 Применение ИИ в XDR. …

10 Nov 2026, 07:45 UTC≈1,250 viewsread 11 November 2026
Photo

ℹ️ Защита от SSRF: памятка OWASP • Памятка по защите от SSRF — атак, при которых приложение используют для обращения к внутренней или внешней сети либо к самой машине. • Защита разобрана отдельно для двух случаев: запросы только к известным доверенным приложениям, где применим список разрешенных адресатов, и запросы к произвольным внешним IP-адресам или доменам, где такой подход недоступен. • Важная оговорка: спис…

9 Nov 2026, 16:24 UTC≈1,400 viewsread 11 November 2026
Photo

ℹ️ Страж ПК: разбор проверок подозрительных программ • Статья об устройстве «Стража ПК»: как подпись файла, место запуска и командная строка помогают оценить подозрительность, а сетевые связи — искать майнеры без вирусной базы. • Программа не заменяет антивирус. Удаление и перенос файлов требуют подтверждения; для опасных файлов предусмотрен карантин с возможностью восстановления. • На странице релиза доступны уст…

9 Nov 2026, 11:16 UTC≈1,370 viewsread 11 November 2026
Photo

📂 ferret-scan: поиск и маскирование чувствительных данных Утилита командной строки и библиотека Go для поиска персональных данных и секретов в файлах и потоках. Маскирует найденные значения с сохранением формата, оценивает достоверность находок с учетом контекста. Работает локально: данные не покидают компьютер. Отчеты SARIF, GitLab SAST и JUnit подходят для интеграции с проверками кода в GitHub, отчетами GitLab и …

8 Nov 2026, 07:56 UTC≈1,530 viewsread 11 November 2026
Photo

ℹ️ C# для Windows: сборка и проверка из Kali Linux • Статья для пентестеров о сборке C#-программ для Windows в Kali Linux. Для базовой компиляции используется пакет mono-devel. • Отдельно показано, как запускать и тестировать Windows-программы прямо из Kali: для этого предлагается установить Wine и wine-mono. • Для DotNetToJScript есть важная оговорка: авторы использовали готовые бинарные файлы из репозитория прое…

7 Nov 2026, 18:57 UTC≈1,710 viewsread 11 November 2026
Photo

📂 crush-forensics: разбор файлов и образов дисков Инструмент для цифровой криминалистики: открывает архивы, мобильные резервные копии, образы дисков и отдельные файлы без предварительной распаковки. Предназначен для точечного изучения источника, а не полного цикла обработки. BLOB Inspector позволяет последовательно декодировать и распаковывать данные, просматривать результат как hex, текст, JSON или изображение. Пр…

7 Nov 2026, 14:01 UTC≈1,710 viewsread 11 November 2026
Photo

ℹ️ Ghidra и GDB: как проверить смысл условия в бинарнике • Учебный разбор на примере Getting Started Keygen — программы-головоломки для Linux x86-64 на C++. Для анализа доступны только бинарник, Ghidra и GDB: исходного кода и отладочных символов нет. • Показано, как проверить беззнаковое вычитание на отдельной программе, сопоставить псевдокод с инструкциями SUB, CMP и JBE, пройти участок в GDB и сохранить вывод в G…

6 Nov 2026, 13:25 UTC≈1,860 viewsread 11 November 2026
Photo

ℹ️ OWASP: памятка по защите веб-сессий • Памятка о защите веб-сессий от захвата: утечка, угадывание или фиксация идентификатора сессии позволяют атакующему выдать себя за пользователя приложения. • Разобрана передача идентификаторов через cookies. Важно проверить, не принимает ли приложение их также через параметры URL или другие механизмы: одних cookies по умолчанию недостаточно. • Отдельный раздел посвящен защит…

6 Nov 2026, 07:56 UTC≈1,820 viewsread 11 November 2026
Photo

📂 OWASP WSTG: руководство по проверке безопасности веб-приложений Руководство по тестированию безопасности веб-приложений и веб-сервисов. Собирает практики, которые используют пентестеры и организации. Для ссылок на сценарии в отчетах и инструментах рекомендуется указывать версию руководства: идентификаторы проверок могут меняться между выпусками. В README последним стабильным выпуском указан 4.2, а версия 5.0 нах…

5 Nov 2026, 18:00 UTC≈1,920 viewsread 11 November 2026
Photo

ℹ️ Защита офисных МФУ: памятка для администратора • Статья о защите сетевых МФУ: четыре зоны риска — доступ к управлению, лишние службы, устаревшие прошивки и сканы в общих папках под учетной записью с избыточными правами. • Разобран порядок работ: инвентаризация аппаратов, ограничение доступа к управлению, отключение лишних служб, сегментация сети и VLAN для печати, регламент обновления прошивок и настройка прав н…

Showing the 12 most recent of 83 posts we hold for @itbook_library. 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 recorded as deleted after publishing

We recorded 8 posts on @itbook_library as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
10 August 2026
Most recent seen missing
8 November 2026
Median time before seen missing
4 days
Seen missing in the last 30 days
1

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 5 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.

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.

Книжное хранилище
@knijnoe_xranilishe · 19,509
Telegram ranks this channel #11 of 73 here — alongside 72 others — read 30 September 2026
Полка Разработчика
@developer_shelf · 26,715
Telegram ranks this channel #13 of 63 here — alongside 62 others — read 11 September 2026
Бункер Хакера
@book_academ · 21,293
Telegram ranks this channel #14 of 72 here — alongside 71 others — read 23 September 2026
no system is safe // cybersec
@nsis_cybersec · 21,166
Telegram ranks this channel #14 of 71 here — alongside 70 others — read 23 September 2026
S.E.Book
@S_E_Book · 23,090
Telegram ranks this channel #16 of 64 here — alongside 63 others — read 19 September 2026
InfoSec Portal
@cybersecinform · 20,042
Telegram ranks this channel #23 of 75 here — alongside 74 others — read 2 October 2026
Linux для чайника
@os_linux_ru · 19,526
Telegram ranks this channel #24 of 87 here — alongside 86 others — read 1 October 2026
Лаборатория хакера
@lab_hack · 25,423
Telegram ranks this channel #25 of 71 here — alongside 70 others — read 14 September 2026
Open IT | Архив
@openit_archive · 18,760
Telegram ranks this channel #27 of 59 here — alongside 58 others — read 5 October 2026
S.E.Reborn
@S_E_Reborn · 22,459
Telegram ranks this channel #30 of 66 here — alongside 65 others — read 20 September 2026
Этичный Хакер
@hack_less · 243,065
Telegram ranks this channel #32 of 81 here — alongside 80 others — read 12 August 2026
Секреты сисадмина | DevOps, Linux, SRE
@sysadmin_library · 25,723
Telegram ranks this channel #34 of 85 here — alongside 84 others — read 13 September 2026
Учебные фильмы 🎞
@maths_lib · 25,588
Telegram ranks this channel #35 of 67 here — alongside 66 others — read 14 September 2026
infosecurity
@tg_infosec · 26,845
Telegram ranks this channel #35 of 74 here — alongside 73 others — read 11 September 2026
Книги для Системного Администратора
@i_odmin_book · 18,778
Telegram ranks this channel #41 of 83 here — alongside 82 others — read 5 October 2026
hahacker_news
@hahacker_news · 25,231
Telegram ranks this channel #43 of 59 here — alongside 58 others — read 14 September 2026
Social Engineering
@Social_engineering · 124,696
Telegram ranks this channel #47 of 82 here — alongside 81 others — read 13 August 2026
Заметки Бэкендера
@backend_it · 18,688
Telegram ranks this channel #62 of 73 here — alongside 72 others — read 4 October 2026
Серверная Админа | Компьютерные сети
@school_network · 26,411
Telegram ranks this channel #66 of 85 here — alongside 84 others — read 12 September 2026
Physics.Math.Code
@physics_lib · 146,676
Telegram ranks this channel #71 of 72 here — alongside 71 others — read 13 August 2026

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

“ИБ Книга | Библиотека ИБ” (@itbook_library), 15,938 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/itbook_library.

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.