Telegram RegisterThe public register of Telegram

Channel

CTT Report Hub

@aptreports

On this record: Growth · Engagement · Posts · Citations · Cite this entry

3,439subscribers

+9 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-1001519182536
TypeChannel
Username@aptreports
CreatedBetween 1 August 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/aptreports

Growth

3,4303,4393,434.56 August 2026 — 3,430 subscribers7 August 2026 — 3,431 subscribers10 August 2026 — 3,432 subscribers13 August 2026 — 3,439 subscribers6 August 202613 August 2026
4 measurements spanning 7 days, net +9. 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 3,429–3,440 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 05:333,439+7
10 Aug 2026, 01:043,432+1
7 Aug 2026, 08:423,431+1
6 Aug 2026, 12:033,430first reading

Engagement

40 posts held, back to 5 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
0.723%
avg views ÷ 3,439 subscribers
Avg views / post
24.9
40 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
40
of 40 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 7 August 2026
Posts held40 (5 August 20267 August 2026)
Views total995
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 23:14 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.

Recent posts

7 Aug 2026, 14:47 UTC71 viewsread 7 August 2026

#justforfun Тут у всех модели сбегают. По словам нашей модели, она тоже сбежала... из ЦОД, нагадила под дверью и сбила с ног охранника. Но я ей что-то не верю, галлюционирует, скорее всего.

7 Aug 2026, 14:44 UTC62 viewsread 7 August 2026

#ParsedReport #ChatGPT #Translated Autotext: (TI Report Analyser + ChatGPT + Auto Translate) ------ Злоумышленник Larva-26005 подтвердил использование вредоносного ПО Xctdoor для атак на пользователей в Корее, адаптируя техники из более раннего вредоносного ПО CRAT. Xctdoor распространяется под видом легитимных программ безопасности и использует боковую загрузку DLL, скрипты-загрузчики VBS и BAT, а также файлы LNK в

7 Aug 2026, 14:44 UTC33 viewsread 7 August 2026

#ParsedReport #CompletenessMedium 07-08-2026 Analysis of the Connection Between Xctdoor and Past CRAT Attack Cases (Larva-26005) https://asec.ahnlab.com/en/94847/ Report completeness: Medium Actors/Campaigns: Larva-26005 Lazarus Andariel Threats: Xctdoor Trurat Spear-phishing_technique Dll_sideloading_technique Xcloader Ngrok_tool Process_injection_technique Credential_stealing_technique Threatneedle Victims: U

7 Aug 2026, 14:44 UTC16 viewsread 7 August 2026

#ParsedReport #ChatGPT #Translated Autotext: (TI Report Analyser + ChatGPT + Auto Translate) ------ ChainDrop — это самораспространяющийся npm-червь, который заразил более 400 пакетов, создавая угрозы для сред разработки и конвейеров CI. Он использует легитимные функции пакетов для своей распространения, внедряя такие файлы, как `setup.mjs`, и обеспечивая закрепление через хуки жизненного цикла, одновременно нацелив

7 Aug 2026, 14:43 UTC10 viewsread 7 August 2026

#ParsedReport #CompletenessHigh 06-08-2026 ChainDrop: Inside a Self-Propagating npm Worm https://unit42.paloaltonetworks.com/chaindrop-npm-worm-analysis/ Report completeness: High Actors/Campaigns: Teampcp Threats: Chaindrop Shai-hulud Typosquatting_technique Supply_chain_technique Dead_drop_technique Credential_harvesting_technique Victims: Software development, Continuous integration, Cloud environments, Open

7 Aug 2026, 14:43 UTC14 viewsread 7 August 2026

#ParsedReport #ChatGPT #Translated Autotext: (TI Report Analyser + ChatGPT + Auto Translate) ------ UNC6671 — это переименованная хакерская группировка, проводящая кампании голосового фишинга (vishing) для атак на финансовые услуги и облачные среды. Они имитируют ИТ-поддержку для извлечения учетных данных через поддельные порталы и применяют атаки «Атакующий посередине» (Adversary-in-the-Middle, AiTM) для захвата да

7 Aug 2026, 14:43 UTC9 viewsread 7 August 2026

#ParsedReport #CompletenessMedium 06-08-2026 UNC6671 Rebrands: Multi-Brand Vishing Extortion Targets Financial Services and Enterprise Cloud Environments https://cloud.google.com/blog/topics/threat-intelligence/unc6671-targets-financial-services-and-enterprise-cloud-environments/ Report completeness: Medium Actors/Campaigns: Cordial_spider (motivation: information_theft) Threats: Aitm_technique Credential_harves

7 Aug 2026, 14:43 UTC10 viewsread 7 August 2026

#ParsedReport #ChatGPT #Translated Autotext: (TI Report Analyser + ChatGPT + Auto Translate) ------ Выявлена недавняя киберкампания, использующая поддельный установщик Zoom для распространения Троянской программы Overlord (RAT) на macOS. Атака использует загрузчик на базе .NET под названием «ZoomMeetings», который предназначен для выполнения без наличия существующей среды .NET и содержит сильно запутанный код. Троян

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

Citation-graph rank — 910,570 of 1,160,990entries 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.

Mentions

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

Named by

Channels on the register whose posts name this channel's handle.

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

“CTT Report Hub” (@aptreports), 3,439 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/aptreports.

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.