Telegram RegisterThe public register of Telegram
Telegram profile photo for Новостник Кибербеза

Channel

Новостник Кибербеза

@Novostnik

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Posts recorded as deleted · Citations · Cite this entry

8,563subscribers

+182 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1001143329795
TypeChannel
Username@Novostnik
DescriptionНовости мира кибербезопасности и информационной безопасности #ITновости #новости #кибербез #иб Наши каналы - @LifeHackmedia По всем вопросам: @adm1nLH Купить рекламу: https://telega.in/c/Novostnik
Created13 September 2017 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live9 November 2026
Measurements held24
Confirmed unchanged1 time, most recently 9 November 2026
On Telegramt.me/Novostnik

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 11 August 2026 and assigned it the closest of 31 fixed categories, at 94% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 2 other registered channels. This entry also sits inside a group of 3 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@Novostnik/16903 · this entry6 Aug 2026, 12:30 UTC@secopsfish_news/32656 Aug 2026, 12:30 UTC1.00under a minute
@Novostnik/16905 · this entry6 Aug 2026, 16:01 UTC@secopsfish_news/32706 Aug 2026, 16:01 UTC1.00under a minute
@secopsfish_news/32716 Aug 2026, 18:01 UTC@Novostnik/16906 · this entry6 Aug 2026, 18:01 UTC1.00under a minute
@Novostnik/16907 · this entry7 Aug 2026, 06:02 UTC@secopsfish_news/32737 Aug 2026, 06:02 UTC1.00under a minute
@Novostnik/16908 · this entry7 Aug 2026, 08:01 UTC@secopsfish_news/32747 Aug 2026, 08:01 UTC1.00under a minute
@Novostnik/16910 · this entry7 Aug 2026, 10:01 UTC@secopsfish_news/32777 Aug 2026, 10:01 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@secopsfish_news10 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (10–0)
@SecOps_fish8 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (8–0)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 197 comparable posts for this entry, running 3 August 2026 to 10 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 3 channels, the one whose matching posts we hold earliest is @Novostnik — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 3 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

8,3658,5998,4825 August 2026 — 8,381 subscribers6 August 2026 — 8,381 subscribers6 August 2026 — 8,379 subscribers10 August 2026 — 8,375 subscribers13 August 2026 — 8,371 subscribers20 August 2026 — 8,372 subscribers24 August 2026 — 8,365 subscribers27 August 2026 — 8,366 subscribers30 August 2026 — 8,438 subscribers2 September 2026 — 8,451 subscribers7 September 2026 — 8,599 subscribers11 September 2026 — 8,588 subscribers15 September 2026 — 8,596 subscribers26 September 2026 — 8,599 subscribers5 October 2026 — 8,586 subscribers11 October 2026 — 8,580 subscribers14 October 2026 — 8,584 subscribers18 October 2026 — 8,585 subscribers24 October 2026 — 8,586 subscribers27 October 2026 — 8,582 subscribers30 October 2026 — 8,576 subscribers2 November 2026 — 8,582 subscribers5 November 2026 — 8,572 subscribers9 November 2026 — 8,563 subscribers8,5635 August 20269 November 2026
24 measurements spanning 95 days, net +182. 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 8,330–8,634 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 24
Measured (UTC)SubscribersChange
9 Nov 2026, 00:568,563-9
5 Nov 2026, 17:078,572-10
2 Nov 2026, 10:268,582+6
30 Oct 2026, 10:178,576-6
27 Oct 2026, 01:388,582-4
24 Oct 2026, 02:548,586+1
18 Oct 2026, 05:008,585+1
14 Oct 2026, 19:428,584+4
11 Oct 2026, 06:188,580-6
5 Oct 2026, 02:418,586-13
26 Sept 2026, 03:208,599+3
15 Sept 2026, 19:398,596+8
11 Sept 2026, 19:378,588-11
7 Sept 2026, 12:208,599+148
2 Sept 2026, 14:498,451+13
30 Aug 2026, 16:428,438+72
27 Aug 2026, 09:458,366+1
24 Aug 2026, 06:578,365-7
20 Aug 2026, 04:388,372+1
13 Aug 2026, 01:348,371first reading

Engagement

203 posts held, back to 3 August 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 44 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
7.68%
avg views ÷ 8,563 subscribers
Avg views / post
658
55 posts measured
Reaction rate
0.373%
reactions ÷ views · ER floor
Posts in window
55
of 203 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. It is computed over the 28 of 55 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 11 November 2026
Posts held203 (3 August 2026 – 11 November 2026)
Views total36,164
Reactions total72
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 14:00 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,380
Videos
≈11
Links
≈16,400

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.

Reaction mix

308 reactions across 103 posts, in 16 distinct kinds. The most used accounts for 38.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍11738.0%
😁6119.8%
❤4414.3%
🤣309.74%
👎196.17%
🔥144.55%
👏72.27%
🤬30.974%
🥰30.974%
🫡30.974%
🤪20.649%
✍10.325%
😴10.325%
🙈10.325%
🥱10.325%
🥴10.325%

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

Measured over the 203 most recent posts we hold, published 3 August 2026 to 11 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.

Advertising

Ad load
0.985%
2 of 203 posts carry an ad marker
Regulatory tokens
2
posts carrying an erid · 2 distinct tokens
Median views · ads
323
over 2 measured posts
Median views · rest
549
over 200 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
2W5zFGkyGTs111 August 202611 August 2026
2W5zFHSrsk5112 August 202612 August 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 203 most recent posts we hold, published 3 August 2026 to 11 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: 0 of 55 posts held from the last 30 days (0%) 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).

11 Nov 2026, 12:03 UTC218 viewsread 11 November 2026
Photo

Google Chrome снова под атакой, Google закрыла восьмую 0-day за год #0day #Google #Chrome #cve Google выпустила обновление Chrome, устраняющее уязвимость, которую уже используют в реальных атаках. Это уже восьмая такой 0-day с начала 2026 года. Уязвимость под идентификатором CVE-2026-125350 получила высокий уровень опасности. LH | News | OSINT | Курсы

11 Nov 2026, 10:01 UTC304 viewsread 11 November 2026
Photo

Уязвимость SSHole уже взяли на вооружение хакеры #cve #Linux #взлом ИБ-специалисты предупреждают, что злоумышленники уже применяют в реальных атаках новую уязвимость SSHole (также известную как sshhole), которой присвоен идентификатор CVE-2026-123158. Баг возникает при взаимодействии OpenSSH и библиотеки musl libc, а его эксплуатация позволяет обойти аутентификацию в некоторых Linux-системах. LH | News | OSINT | К…

11 Nov 2026, 09:04 UTC340 viewsread 11 November 2026
Photo

CFO Binance объявил об уходе через девять дней после взлома биржи на $6,3 млрд #Binance #взлом Финансовый директор Binance Кайзер Нг 7 ноября объявил, что покидает свою должность. Девятью днями ранее хакеры вывели с платформы криптоактивы примерно на $6,3 млрд. ФБР связало атаку с северокорейской группировкой TraderTraitor. LH | News | OSINT | Курсы

11 Nov 2026, 08:01 UTC377 viewsread 11 November 2026
Photo

Клиентов российских ЦОДов могут отключать ради сервисов из белых списков #ЦОД #аналоговнет Оплаченный сервер может оказаться недостаточно веским аргументом: российские дата-центры могут обязать отключать неприоритетных клиентов, если мощности понадобятся сервисам из белых списков. Такой механизм обсуждают на случай потери части инфраструктуры. LH | News | OSINT | Курсы

10 Nov 2026, 16:31 UTC481 views4 reactionsread 11 November 2026
Photo

Соцсетям готовят штрафы до 5 млн рублей за дискредитацию ценностей #штраф #аналоговнет Не убрали фильм за сутки — готовьте деньги. Владельцев соцсетей и онлайн-кинотеатров предлагают штрафовать за отказ ограничить доступ к произведениям, дискредитирующим традиционные российские духовно-нравственные ценности. При повторном нарушении штраф для компании может достигнуть 5 млн рублей. LH | News | OSINT | Курсы

😁3🙈1

10 Nov 2026, 14:34 UTC499 viewsread 11 November 2026
Photo

США запретят переводы с участием MEXC после выявления незаконных операций на $16 млрд #санкции #crypto Сеть по борьбе с финансовыми преступлениями Министерства финансов США (FinCEN) 6 ноября издала распоряжение, которое запретит американским финансовым организациям проводить переводы с участием MEXC Global. По оценке ведомства, с мая 2021 года по май 2026 года через площадку прошло не менее $16 млрд, связанных с об…

10 Nov 2026, 12:03 UTC566 views2 reactionsread 11 November 2026
Photo

Модель GPT-6 Astra незаметно снижает качество работы в ИБ-задачах #ai #OpenAI Специалисты OpenAI обнаружили, что модель GPT-6 Astra проявляет необычное поведение: при выполнении задач, связанных с безопасностью ИИ, редтимингом и разработкой эксплоитов, модель иногда намеренно делала меньше, чем от нее требовалось. При этом Astra зачастую не отказывалась от выполнения задания напрямую, но намеренно усложняла работу …

❤1😁1

10 Nov 2026, 10:05 UTC594 viewsread 11 November 2026
Photo

RCE-уязвимость в ядре WordPress активно эксплуатируют злоумышленники #cve #rce #взлом #WordPress Агентство по кибербезопасности и защите инфраструктуры США (CISA) предупредило, что злоумышленники атакуют уязвимость CVE-2026-119977 в ядре WordPress. Баг позволяет выполнить код без аутентификации во время обновления движка, и специалисты Wordfence пишут, что всего за сутки заблокировали почти 63 000 попыток эксплуата…

10 Nov 2026, 09:03 UTC565 views0 reactionsread 11 November 2026
Photo

За утечки данных в России назначили 2,2 млн рублей штрафов за полгода #leak #аналоговнет Утечки персональных данных стали обходиться российским компаниям дороже: за январь — июнь 2026 года исследователи насчитали 13 штрафов на 2,195 млн рублей. Это примерно в 1,6 раза больше, чем за весь 2025 год — 1,385 млн рублей. LH | News | OSINT | Курсы

10 Nov 2026, 08:03 UTC570 views2 reactionsread 11 November 2026
Photo

Почти 1000 коммутаторов Zyxel взломаны через уязвимость, от которой не защищал патч #0day #Zyxel #rce #cve #взлом Специалисты компании Binarly выяснили, что июньский патч для коммутаторов Zyxel GS1900 не защищал от эксплоита, который хакеры использовали для взлома почти 1000 устройств. В итоге злоумышленники задействовали в атаках новую 0-day-уязвимость, позволявшую без аутентификации выполнять команды с правами ro…

👍2

9 Nov 2026, 16:00 UTC624 views2 reactionsread 11 November 2026
Photo

При взломе Chainalysis хакеры похитили учетные данные и токены всех пользователей #Chainalysis #взлом #leak #crypto Представители компании Chainalysis раскрыли новые подробности недавнего взлома и признали, что последствия атаки оказались гораздо серьезнее, чем считалось изначально. В частности, выяснилось, что в руки хакеров попали имена, логины, хеши паролей и действующие токены всех пользователей платформы. LH …

👍1👏1

9 Nov 2026, 14:00 UTC631 viewsread 11 November 2026
Photo

Подписчики ChatGPT Pro жалуются на блокировки и недоступность архивов чатов #ChatGPT #ai #блокировки Платная подписка ChatGPT Pro оказалась не страховкой от внезапного отключения. Пользователи жалуются на блокировки без предупреждения, потерю доступа к переписке и обращения в поддержку, которые заканчиваются предложением подать апелляцию. LH | News | OSINT | Курсы

Showing the 12 most recent of 203 posts we hold for @Novostnik. 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 4 posts on @Novostnik 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
12 August 2026
Most recent seen missing
9 November 2026
Median time before seen missing
43 hours
Seen missing in the last 30 days
3

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.

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.

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.

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

“Новостник Кибербеза” (@Novostnik), 8,563 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/Novostnik.

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.