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,446subscribers

+145 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 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 September 2026
Measurements held31
Confirmed unchanged1 time, most recently 17 September 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 why it has no browse page of its own yet.

Growth

11,30111,44611,373.57 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 subscribers7 August 202617 September 2026
31 measurements spanning 42 days, net +145. 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,279–11,468 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 31
Measured (UTC)SubscribersChange
17 Sept 2026, 21:2111,446+8
15 Sept 2026, 20:1511,438+2
14 Sept 2026, 00:2011,436+1
12 Sept 2026, 06:3711,435+11
9 Sept 2026, 23:3811,424+23
6 Sept 2026, 15:3911,401-6
4 Sept 2026, 02:5611,407+7
2 Sept 2026, 19:1911,400+6
1 Sept 2026, 19:1511,394+10
31 Aug 2026, 21:2711,384+4
30 Aug 2026, 20:3411,380+1
29 Aug 2026, 18:5311,379+3
28 Aug 2026, 22:0711,376+11
28 Aug 2026, 01:1811,365+3
26 Aug 2026, 23:1511,362+3
25 Aug 2026, 22:3511,359+4
25 Aug 2026, 01:0511,355+7
23 Aug 2026, 15:0311,348+6
22 Aug 2026, 03:3411,342+2
20 Aug 2026, 19:1611,340first reading

Engagement

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

ERR · 30 days
15.2%
avg views ÷ 11,446 subscribers
Avg views / post
1,740
54 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
54
of 158 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 2 September 2026
Posts held158 (4 August 20262 September 2026)
Views total93,880
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 00:05 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

2 Sept 2026, 15:19 UTC≈1,020 viewsread 3 September 2026
Photo

‼️ #Exploited #SonicWall: rilevato sfruttamento attivo in rete delle vulnerabilità CVE-2026-83548 e CVE-2026-83549 Rischio: 🔴 Tipologia: 🔸 Remote Code Execution 🔸 Security Restrictions Bypass 🔗 https://www.acn.gov.it/portale/w/vulnerabilita-in-prodotti-sonicwall-12 ⚠️ Importante mantenere aggiornati i sistemi

2 Sept 2026, 13:51 UTC≈1,230 viewsread 3 September 2026
Photo

#HPE: sanate 86 vulnerabilità nei prodotti #Aruba Networking #AOS-CX e #FabricComposer Rischio: 🟠 Tipologia: 🔸 Remote Code Execution 🔸 Authentication Bypass 🔸 Privilege Escalation 🔸 Arbitrary File Write 🔸 Security Restrictions Bypass 🔸 Information Disclosure 🔸 Denial of Service 🔗 https://www.acn.gov.it/portale/w/risolte-vulnerabilita-in-prodotti-hpe-aruba-networking-1 🔄️ Aggiornamenti disponibili 🔄️

2 Sept 2026, 13:42 UTC≈1,150 viewsread 3 September 2026
Photo

#Elastic: risolte 4 vulnerabilità con gravità "alta" in #Kibana #Elasticsearch #Winlogbeat Rischio: 🟠 Tipologia: 🔸 Security Restrictions Bypass 🔸 Remote Code Execution 🔸 Privilege Escalation 🔸 Arbitrary File Write/Deletion 🔸 Tampering 🔗 https://www.acn.gov.it/portale/w/risolte-vulnerabilita-in-prodotti-elastic-1 🔄️ Aggiornamenti disponibili 🔄️

2 Sept 2026, 13:04 UTC≈1,190 viewsread 3 September 2026
Photo

#Zohocorp: risolta vulnerabilità con gravità "alta" presente nei prodotti #ManageEngine #PasswordManagerPro, #PAM360 e #AccessManagerPlus Rischio: 🟠 Tipologia: 🔸 Security Restrictions Bypass 🔗 https://www.acn.gov.it/portale/w/risolte-vulnerabilita-in-prodotti-zohocorp-manageengine 🔄️ Aggiornamenti disponibili 🔄️

2 Sept 2026, 10:38 UTC≈1,320 viewsread 3 September 2026
Photo

#Erlang/OTP: risolte nuove vulnerabilità, di cui 11 con gravita "alta" Rischio: 🟠 Tipologia: 🔸 Denial of Service 🔸 Security Feature Bypass 🔸 Tampering 🔗 https://www.acn.gov.it/portale/w/rilevate-vulnerabilita-in-erlang/otp-3 🔄️ Aggiornamenti disponibili 🔄️

2 Sept 2026, 09:38 UTC≈1,250 viewsread 3 September 2026
Photo

#Dell: risolte 17 vulnerabilità, di cui 3 con gravità "critica", nei prodotti #PowerStore Rischio: 🟠 Tipologia: 🔸 Remote Code Execution 🔸 Authentication Bypass 🔸 Privilege Escalation 🔸 Denial of Service 🔸 Information Disclosure 🔸 Data Manipulation 🔗 https://www.acn.gov.it/portale/w/aggiornamenti-di-sicurezza-dell-technologies-2 🔄️ Aggiornamenti disponibili 🔄️

2 Sept 2026, 09:20 UTC≈1,240 viewsread 3 September 2026
Photo

#GitHub: risolte 4 vulnerabilità, di cui 3 con gravità "alta" Rischio: 🟡 Tipologia: 🔸 Remote Code Execution 🔸 Information Disclosure 🔸 Privilege Escalation 🔗 https://www.acn.gov.it/portale/w/risolte-vulnerabilita-su-github-enterprise-server-1 🔄️ Aggiornamenti disponibili 🔄️

2 Sept 2026, 08:29 UTC≈1,290 viewsread 3 September 2026
Photo

#Google: risolte 26 vulnerabilità, di cui 9 con gravità "alta" e 2 con gravità "critica" Rischio: 🟠 Tipologia: 🔸 Arbitrary Code Execution 🔸 Information Disclosure 🔸 Security Restrictions Bypass 🔗 https://www.acn.gov.it/portale/w/risolte-vulnerabilita-in-google-chrome-71 🔄️ Aggiornamenti disponibili 🔄️

2 Sept 2026, 08:28 UTC≈1,360 viewsread 3 September 2026
Photo

#Rockwell: risolte nuove vulnerabilità di cui 5 con gravità "alta" Rischio: 🟠 Tipologia: 🔸 Denial of Service 🔸 Remote Code Execution 🔸 Elevation of Privilege 🔗 https://www.acn.gov.it/portale/w/vulnerabilita-in-prodotti-rockwell-automation 🔄️ Aggiornamenti disponibili 🔄️

2 Sept 2026, 08:25 UTC≈1,390 viewsread 3 September 2026
Photo

#Mozilla: risolte 11 vulnerabilità nei prodotti #Firefox, #FirefoxESR e #Thunderbird Rischio: 🟠 Tipologia: 🔸 Arbitrary Code Execution 🔸 Privilege Escalation 🔸 Security Restrictions Bypass 🔗 https://www.acn.gov.it/portale/w/risolte-vulnerabilita-in-prodotti-mozilla-9 🔄️ Aggiornamenti disponibili 🔄️

1 Sept 2026, 12:20 UTC≈1,780 viewsread 3 September 2026
Photo

‼️ #PoC #Tenda: disponibili Proof of Concept (PoC) per 3 vulnerabilità con gravità "critica" Rischio: 🔴 Tipologia: 🔸Authentication Bypass 🔸Denial of Service 🔸Tampering 🔗 https://www.acn.gov.it/portale/w/tenda-poc-pubblici-per-3-nuove-vulnerabilita ⚠️ Importante mantenere aggiornati i sistemi

1 Sept 2026, 09:18 UTC≈1,860 viewsread 3 September 2026

‼ #Ruby: rilevato lo sfruttamento attivo in rete della CVE-2026-66066, relativa al framework di sviluppo #Rails Rischio: 🔴 ⚠ Ove non provveduto, si raccomanda l’aggiornamento tempestivo del software interessato 👉 link al post principale: https://t.me/CSIRT_italia/3835

Showing the 12 most recent of 158 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 · 56,878
Telegram ranks this channel #31 of 55 here — alongside 54 others — read 23 August 2026
The Hacker News
@thehackernews · 164,665
Telegram ranks this channel #41 of 58 here — alongside 57 others — read 13 August 2026
andreagaleazzi.com
@andreagaleazzi · 22,289
Telegram ranks this channel #51 of 63 here — alongside 62 others — read 21 September 2026
Will Media
@will_media · 41,296
Telegram ranks this channel #74 of 79 here — alongside 78 others — read 29 August 2026
Proton
@proton_privacy · 36,183
Telegram ranks this channel #80 of 83 here — alongside 82 others — read 31 August 2026

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

“CSIRT Italia” (@CSIRT_italia), 11,446 subscribers as measured 17 September 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.