Telegram RegisterThe public register of Telegram
Telegram profile photo for CSIRT Italia

Channel

CSIRT Italia

@CSIRT_italia

Verified by Telegram

On this record: Topic · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry

11,969subscribers

+668 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001239933375
TypeChannel
Username@CSIRT_italia
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live6 November 2026
Measurements held59
Confirmed unchanged1 time, most recently 6 November 2026
On Telegramt.me/CSIRT_italia

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

11,30111,96911,6357 August 2026 — 11,301 subscribers7 August 2026 — 11,301 subscribers8 August 2026 — 11,307 subscribers11 August 2026 — 11,313 subscribers12 August 2026 — 11,314 subscribers13 August 2026 — 11,315 subscribers14 August 2026 — 11,318 subscribers16 August 2026 — 11,321 subscribers17 August 2026 — 11,323 subscribers18 August 2026 — 11,334 subscribers19 August 2026 — 11,333 subscribers20 August 2026 — 11,340 subscribers22 August 2026 — 11,342 subscribers23 August 2026 — 11,348 subscribers25 August 2026 — 11,355 subscribers25 August 2026 — 11,359 subscribers26 August 2026 — 11,362 subscribers28 August 2026 — 11,365 subscribers28 August 2026 — 11,376 subscribers29 August 2026 — 11,379 subscribers30 August 2026 — 11,380 subscribers31 August 2026 — 11,384 subscribers1 September 2026 — 11,394 subscribers2 September 2026 — 11,400 subscribers4 September 2026 — 11,407 subscribers6 September 2026 — 11,401 subscribers9 September 2026 — 11,424 subscribers12 September 2026 — 11,435 subscribers14 September 2026 — 11,436 subscribers15 September 2026 — 11,438 subscribers17 September 2026 — 11,446 subscribers28 September 2026 — 11,481 subscribers5 October 2026 — 11,528 subscribers9 October 2026 — 11,561 subscribers13 October 2026 — 11,575 subscribers14 October 2026 — 11,611 subscribers15 October 2026 — 11,636 subscribers17 October 2026 — 11,648 subscribers17 October 2026 — 11,654 subscribers18 October 2026 — 11,655 subscribers19 October 2026 — 11,668 subscribers21 October 2026 — 11,678 subscribers22 October 2026 — 11,705 subscribers23 October 2026 — 11,748 subscribers23 October 2026 — 11,788 subscribers24 October 2026 — 11,794 subscribers25 October 2026 — 11,802 subscribers26 October 2026 — 11,821 subscribers27 October 2026 — 11,836 subscribers28 October 2026 — 11,852 subscribers29 October 2026 — 11,868 subscribers30 October 2026 — 11,884 subscribers31 October 2026 — 11,892 subscribers1 November 2026 — 11,894 subscribers2 November 2026 — 11,895 subscribers3 November 2026 — 11,912 subscribers4 November 2026 — 11,920 subscribers5 November 2026 — 11,953 subscribers6 November 2026 — 11,969 subscribers7 August 20266 November 2026
59 measurements spanning 91 days, net +668. 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 11,201–12,069 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 59
Measured (UTC)SubscribersChange
6 Nov 2026, 08:3911,969+16
5 Nov 2026, 10:1611,953+33
4 Nov 2026, 08:1111,920+8
3 Nov 2026, 11:0911,912+17
2 Nov 2026, 09:3411,895+1
1 Nov 2026, 11:2411,894+2
31 Oct 2026, 14:4911,892+8
30 Oct 2026, 13:5511,884+16
29 Oct 2026, 15:3711,868+16
28 Oct 2026, 16:4011,852+16
27 Oct 2026, 18:2611,836+15
26 Oct 2026, 16:5611,821+19
25 Oct 2026, 20:0611,802+8
24 Oct 2026, 19:5111,794+6
23 Oct 2026, 23:2011,788+40
23 Oct 2026, 02:2611,748+43
22 Oct 2026, 03:2911,705+27
21 Oct 2026, 00:4111,678+10
19 Oct 2026, 23:0711,668+13
18 Oct 2026, 20:1011,655first reading

Engagement

209 posts held, back to 4 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 50 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
15.8%
avg views ÷ 11,969 subscribers
Avg views / post
1,890
51 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
51
of 209 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 5 November 2026
Posts held209 (4 August 2026 – 5 November 2026)
Views total96,160
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Nov 2026, 07:25 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

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

5 Nov 2026, 19:44 UTC≈1,230 viewsread 6 November 2026
Photo

‼️ #OpenSSH: sanata vulnerabilità che potrebbe consentire il bypass dell’autenticazione #SSH su specifiche configurazioni #Linux basate su #musl #libc. Rischio: 🟠 Tipologia: 🔸 Authentication Bypass 🔗 https://www.acn.gov.it/portale/w/openssh-potenziale-bypass-dell-autenticazione-su-sistemi-linux-basati-su-musl-libc 🔄 Aggiornamenti disponibili 🔄

5 Nov 2026, 15:47 UTC≈1,650 viewsread 6 November 2026
Photo

#SonicWall: risolte vulnerabilità, tra cui una con gravità "critica", in #GMS #EoL Rischio: 🟠 Tipologia: 🔸 Information Disclosure 🔸 Arbitrary File Read 🔗 https://www.acn.gov.it/portale/w/vulnerabilita-in-prodotti-sonicwall-12 ⚠ Si raccomanda di migrare i sistemi interessati verso soluzioni supportate dal produttore

5 Nov 2026, 15:43 UTC≈1,550 viewsread 6 November 2026
Photo

‼️ #PoC #FreeRDP: disponibili Proof of Concept (PoC) per lo sfruttamento di molteplici vulnerabilità Rischio: 🔴 Tipologia: 🔸 Remote Code Execution 🔸 Denial of Service 🔸 Information Disclosure 🔸 Security Restrictions Bypass 🔸 Spoofing 🔗 https://www.acn.gov.it/portale/w/freerdp-disponibili-poc-per-molteplici-vulnerabilita ⚠️ Importante mantenere aggiornati i sistemi

5 Nov 2026, 14:27 UTC≈1,640 viewsread 6 November 2026
Photo

#VeraCrypt: sanata una vulnerabilità con gravità "alta" Rischio: 🟠 Tipologia: 🔸 Denial of Service 🔸 Information Disclosure 🔗 https://www.acn.gov.it/portale/w/risolta-vulnerabilita-in-veracrypt 🔄️ Aggiornamenti disponibili 🔄️

5 Nov 2026, 11:12 UTC≈1,810 viewsread 6 November 2026
Photo

‼️ #PoC #Linux: disponibile Proof of Concept (PoC) per la vulnerabilità CVE-2026-98432, che interessa il kernel Linux Rischio: 🔴 Tipologia: 🔸 Remote Code Execution 🔸 Denial of Service 🔗 https://www.acn.gov.it/portale/w/linux-disponibile-poc-per-lo-sfruttamento-della-cve-2026-98432 ⚠️ Importante mantenere aggiornati i sistemi

5 Nov 2026, 10:12 UTC≈1,780 viewsread 6 November 2026
Photo

#WatchGuard: risolte quattro vulnerabilità, 3 con gravità "critica" e una con gravità "alta", in #AuthPointAuthenticationGateway Rischio: 🟠 Tipologia: 🔸 Authentication Bypass 🔸 Information Disclosure 🔸 Tampering 🔸 Denial of Service 🔗 https://www.acn.gov.it/portale/w/risolte-vulnerabilita-in-prodotti-watchguard-4 🔄️ Aggiornamenti disponibili 🔄️

5 Nov 2026, 10:06 UTC≈1,740 viewsread 6 November 2026
Photo

#Cisco: risolte tre vulnerabilità, di cui una con gravità "alta" in #UCS_Central_Software Rischio: 🟡 Tipologia: 🔸 Remote Code Execution 🔸 Arbitrary File Write 🔸 Information Disclosure 🔗 https://www.acn.gov.it/portale/w/aggiornamenti-di-sicurezza-per-prodotti-cisco-2 🔄️ Aggiornamenti disponibili 🔄️

5 Nov 2026, 08:40 UTC≈1,820 viewsread 6 November 2026
Photo

‼️ #Exploited #Drupal: rilevato sfruttamento attivo in rete della CVE-2026-118539 Rischio: 🔴 Tipologia: 🔸 Security Restrictions Bypass 🔸 Information Disclosure 🔗 https://www.acn.gov.it/portale/w/drupal-rilevato-sfruttamento-in-rete-della-cve-2026-118539 ⚠️ Importante mantenere aggiornati i sistemi

4 Nov 2026, 17:45 UTC≈2,190 viewsread 6 November 2026
Photo

❄️ #Interfacce di telegestione: si rinnovano le raccomandazioni di sicurezza per tutti i soggetti che impiegano sistemi industriali di gestione remota, indipendentemente dal settore di appartenenza ⚠️ Mitigazioni disponibili 🔗 https://www.acn.gov.it/portale/w/sicurezza-dei-sistemi-a-supporto-della-catena-del-freddo-e-interfacce-di-management-di-sistemi-connessi-richiamo-urgente-alle-misure-di-verifica-e-mitigazione

4 Nov 2026, 16:28 UTC≈2,180 viewsread 6 November 2026
Photo

‼️ #Exploited #WordPress: rilevato sfruttamento attivo in rete della CVE-2026-119977 Rischio: 🔴 Tipologia: 🔸 Remote Code Execution 🔗 https://www.acn.gov.it/portale/w/wordpress-rilevato-sfruttamento-in-rete-della-cve-2026-119977 ⚠️ Importante mantenere aggiornati i sistemi

4 Nov 2026, 15:12 UTC≈2,010 viewsread 6 November 2026
Photo

‼️ #SupplyChain: rilevata la distribuzione di versioni malevole dell'estensione Claude Code sul Marketplace di #Cursor Rischio: 🔴 🔗 https://www.acn.gov.it/portale/w/supply-chain-attack-distribuzione-di-versioni-malevole-dell-estensione-claude-code-sul-marketplace-di-cursor ⚠️ Mitigazioni disponibili

4 Nov 2026, 14:10 UTC≈1,980 viewsread 6 November 2026
Photo

#MongoDB: sanate 15 vulnerabilità, di cui 6 con gravità "alta" in Database Tools e nei driver C, Atlas SQL ODBC e Node.js Rischio: 🟠 Tipologia: 🔸 Privilege Escalation 🔸 Denial of Service 🔸 Information Disclosure 🔸 Security Restrictions Bypass 🔗 https://www.acn.gov.it/portale/w/aggiornamenti-di-sicurezza-per-prodotti-mongodb-4 🔄️ Aggiornamenti disponibili 🔄️

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

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.

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.

DeepWeb
@DeepWebITA · 55,180
Telegram ranks this channel #31 of 55 here — alongside 54 others — read 23 August 2026
The Hacker News
@thehackernews · 165,224
Telegram ranks this channel #41 of 58 here — alongside 57 others — read 13 August 2026
andreagaleazzi.com
@andreagaleazzi · 22,172
Telegram ranks this channel #51 of 63 here — alongside 62 others — read 21 September 2026
Ugolize
@Ugolize · 21,223
Telegram ranks this channel #59 of 67 here — alongside 66 others — read 23 September 2026
Will Media
@will_media · 40,802
Telegram ranks this channel #74 of 79 here — alongside 78 others — read 29 August 2026
Proton
@proton_privacy · 19,093
Telegram ranks this channel #80 of 83 here — alongside 82 others — read 31 August 2026

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

“CSIRT Italia” (@CSIRT_italia), 11,969 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/CSIRT_italia.

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.