Channel
@heise_security
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
1,026subscribers
-3 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001269533396 |
|---|---|
| Type | Channel |
| Username | @heise_security |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/heise_security |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 18:58 | 1,026 | -2 |
| 9 Aug 2026, 10:08 | 1,028 | -2 |
| 6 Aug 2026, 20:47 | 1,030 | +1 |
| 6 Aug 2026, 13:04 | 1,029 | no change |
| 6 Aug 2026, 12:00 | 1,029 | first reading |
20 posts held, back to 1 December 2023 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 11 January 2024. An engagement rate over an empty window would be a number about nothing.
Webkonferenzen: Zoom-Sicherheitslücken ermöglichen Rechteausweitung #Security #Sicherheitslücken #Sicherheitsupdates #Videokonferenz #Zoom Zoom verteilt aktualisierte Videokonferenz-Software․ Sie schließt eine Sicherheitslücke, durch die Angreifer ihre Rechte ausweiten können․
Cyberattacken und Ransomware: Mehrere Opfer, Code-Verkauf und freier Decryptor #Bangladesh #Code #Cyberangriff #Cybercrime #Decryptor #Paraguay #Ransomware #Security #Tigo #Verkauf #Wahlen #ZooToronto Mehrere Cyberangriffe und Ransomware-Attacken haben stattgefunden․ Zudem gibt es Ransomware-Code zu kaufen․ Ein kostenloser Decryptor ist verfügbar․
Zerodays bei Ivanti aktiv genutzt: Connect Secure und Policy Secure sinds nicht #Alert #CVE202346805 #CVE202421887 #Exploit #Ivanti #IvantiConnectSecure #IvantiPolicySecure #NetworkAccessControl #PulseConnectSecure #PulseSecure #Security #VPN Zwei Zero-Days in Ivanti-Produkten machen es "trivial für Angreifer", Befehle auszuführen und sich im Firmennetz einzunisten․ Ivanti hat bedingt gute Tipps․
Sicherheitspatch: API-Fehler in Cisco Unity Connection macht Angreifer zum Root #Cisco #Patchday #Security #Sicherheitslücken #UnityConnection #Updates Verschiedene Netzwerkprodukte von Cisco sind verwundbar․ Eine Lücke gilt als kritisch․
Microsoft Exchange 2019 erreicht Mainstream-Support-Ende #EndofLife #Microsoft #MicrosoftExchange #Security Zum Januar-Patchday von Microsoft ist der Exchange-Server 2019 offiziell aus dem Mainstream-Support gefallen․
heise-Angebot: iX-Workshop: Linux-Server härten (Last Call) #IdentityManagement #Linuxhärten #OpenSource #Server #Zugriffskontrolle Linux-Server und Netzwerkdienste effektiv und umfassend vor Angriffen schützen - von physischer Sicherheit über Verschlüsselung und 2FA bis hin zu SELinux․
Sicherheitsupdates für Dell- und Lenovo-BIOS #AMI #BIOS #Dell #Lenovo #Security #Sicherheitslücken #Sicherheitsupdates Dell stellt aktualisierte BIOS-Versionen für einige Geräte bereit․ AMI schließt mehrere Sicherheitslücken, Lenovo reicht die Korrekturen durch․
"Raffiniertester Exploit aller Zeiten": Sicherheitsexperte beschuldigt Apple #Apple #Cyberangriff #Kaspersky #OperationTriangulation #Security #Spyware #iOS #iPhone Eine schwere iOS-Lücke ermöglichte es Angreifern, iPhones der Sicherheitsfirma Kaspersky zu kapern․ Ein Sicherheitsforscher sieht Apple in der Verantwortung․
Zoho ManageEngine: Kritische Sicherheitslücke in ADSelfService Plus #ADSelfServicePlus #Codeschmuggel #Security #Sicherheitslücken #Sicherheitsupdates #Zoho #ZohoManageEngine In Zoho ManageEngine ADSelfService Plus klafft eine kritische Sicherheitslücke․ Angreifer können dadurch Schadcode einschleusen․
heise-Angebot: Der heise Security Crashkurs zum Schutz vor Ransomware #Cybercrime #Ransomware #Webinar #heisecWebinar Ransomware bleibt die zentrale Gefahr: Dieses praxisorientierte Webinar erklärt, wie Angreifer aktuell vorgehen und wie Sie ihre IT bestmöglich davor schützen․
Sicherheitspatch: IBM Security Verify für Root-Attacken anfällig #IBMSecurityVerify #Patchday #Security #Sicherheitslücken #Updates Die Entwickler haben in IBMs Zugriffsmanagementlösung Security Verify mehrere Sicherheitslücken geschlossen․
Juniper Networks bessert zahlreiche Schwachstellen aus #Juniper #JuniperNetworks #JunosOS #JunosOSEvolved #Security #Sicherheitslücken #Sicherheitsupdates Juniper Networks hat 27 Sicherheitsmitteilungen veröffentlicht․ Sie betreffen Junos OS, Junos OS Evolved und diverse Hardware․
Showing the 12 most recent of 20 posts we hold for @heise_security. 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 — 1,300,668 of 1,340,412entries 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.
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.
@heise_security named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“heise Security” (@heise_security), 1,026 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/heise_security.
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.