Telegram RegisterThe public register of Telegram
Telegram profile photo for Security News for Everyone

Channel

Security News for Everyone

@SeguridadInformatica

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

7,842subscribers

-53 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-1001003018554
TypeChannel
Username@SeguridadInformatica
Created18 December 2015 — measured — cross-checked against a third-party dataset (TGDataset)
First recorded6 August 2026
Last confirmed live17 September 2026
Measurements held13
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/SeguridadInformatica

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 12 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

7,8427,8957,868.55 August 2026 — 7,895 subscribers6 August 2026 — 7,895 subscribers9 August 2026 — 7,890 subscribers12 August 2026 — 7,888 subscribers16 August 2026 — 7,882 subscribers19 August 2026 — 7,878 subscribers23 August 2026 — 7,875 subscribers28 August 2026 — 7,873 subscribers31 August 2026 — 7,866 subscribers4 September 2026 — 7,861 subscribers9 September 2026 — 7,853 subscribers13 September 2026 — 7,849 subscribers17 September 2026 — 7,842 subscribers5 August 202617 September 2026
13 measurements spanning 42 days, net -53. 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 7,834–7,903 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 03:567,842-7
13 Sept 2026, 04:217,849-4
9 Sept 2026, 16:417,853-8
4 Sept 2026, 06:167,861-5
31 Aug 2026, 23:577,866-7
28 Aug 2026, 19:447,873-2
23 Aug 2026, 03:047,875-3
19 Aug 2026, 12:127,878-4
16 Aug 2026, 07:537,882-6
12 Aug 2026, 08:487,888-2
9 Aug 2026, 16:047,890-5
6 Aug 2026, 03:057,895no change
5 Aug 2026, 22:087,895first reading

Engagement

19 posts held, back to 23 February 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 19 pages of 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 19 posts for this entry, the most recent from 13 April 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

127 reactions across 18 posts, in 2 distinct kinds. The most used accounts for 85.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍10985.8%
👎1814.2%

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

Measured over the 19 most recent posts we hold, published 23 February 2025 to 13 April 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.

Recent posts

13 Apr 2026, 08:55 UTC≈2,920 views7 reactionsread 28 August 2026

#RockstarGames #Snowflake #CyberSecurity #DataBreach Rockstar Games habría sido afectada indirectamente por una brecha de seguridad relacionada con la plataforma Snowflake, donde atacantes lograron acceder a datos almacenados en entornos de terceros mediante credenciales comprometidas. Este incidente forma parte de una campaña más amplia que ha impactado a múltiples empresas que utilizaban este servicio de almacenam…

👍7

10 Feb 2026, 07:34 UTC≈3,860 views1 reactionsread 28 August 2026

#NotepadPlusPlus #CyberSecurity #Software Notepad++ informó que su sistema de actualizaciones automáticas fue comprometido tras un acceso no autorizado a la infraestructura de un proveedor externo. El incidente permitió que, durante un periodo limitado, algunos usuarios recibieran actualizaciones manipuladas, aunque el código fuente, las versiones oficiales del sitio web y los datos personales de los usuarios no se …

👍1

31 Dec 2025, 23:02 UTC≈4,040 views5 reactionsread 28 August 2026
Photo

🎆 Happy 2026, H@ckers! 🎆 #SecNews2026 2025 goes to the log archive more alerts than coffees in a night-time SOC with new CVEs. 2025 recap: 🔹 AI everywhere: Everything is AI. “AI-ready” RAM costs more, even if it’s just for opening a browser. 💸 🔹 Surgical ransomware: Less noise, more precision. Targeted attacks and extortion. Backups and segmentation are no longer optional. 🔐 🔹 Cloud on fire: Bad identities and …

👍5

31 Dec 2025, 23:01 UTC≈2,970 views10 reactionsread 28 August 2026
Photo

🎆 ¡Feliz 2026, H@ckers! 🎆 #SecNews2026 2025 se va al archivo de logs: más alertas que cafés en un SOC nocturno con CVES nuevos. Os dejamos un resumen de 2025: 🔹 IA everywhere: Todo es IA. RAM “AI-ready” más cara, aunque solo sirva para abrir el navegador. 💸 🔹 Ransomware quirúrgico: Menos ruido, más precisión. Ataques dirigidos y extorsión. Backups y segmentación ya no son opcionales. 🔐 🔹 Cloud en llamas: Identi…

👍10

29 Nov 2025, 16:29 UTC≈3,890 views1 reactionsread 28 August 2026

#OpenA #GPT #Chatgpt OpenAI informó el 26 de noviembre de 2025 que un acceso no autorizado a los sistemas de su proveedor Mixpanel expuso datos analíticos limitados de algunos usuarios de lsu API (como nombres, correos electrónicos, ubicación aproximada e información técnica) sin afectar claves, contraseñas ni contenido de uso. Tras confirmar el incidente, la compañía ha retirado el uso de Mixpanel de sus servicios…

👍1

27 Nov 2025, 20:46 UTC≈2,800 views5 reactionsread 28 August 2026
Photo

#Securizame #BlackFriday #Formacion Nuestros amigos de Securizame vuelven otro año más con sus ofertas de Black Friday. Todos los cursos de su web tienen un 25% de descuento para todos sus cursos y packs online++ Los cursos que ofertan incluyen temáticas como: Análisis Forense, Hacking Ético y Hardening. Estos descuentos recordad que sólo son válidos a partir del Viernes 28 de Noviembre de 2025 hasta el 01 de Dici…

👍5

18 Nov 2025, 12:07 UTC≈3,910 views5 reactionsread 28 August 2026

#Cloudflare #Averia #Issue Se están registrando problemas con el proveedor de cloudflare: Cloudflare Global Network experiencing issues Investigating - Cloudflare is aware of, and investigating an issue which potentially impacts multiple customers. Further detail will be provided as more information becomes available. Nov 18, 2025 - 11:48 UTC De momento se desconoce el problema, hasta que el proveedor se pronuncie…

👍5

1 Oct 2025, 17:49 UTC≈4,660 views10 reactionsread 28 August 2026

#NavajaNegra #Agenda #Congreso Mañana arranca una nueva edición del congreso de Ciberseguridad Navaja Negra #NN13ED (Desde el día 2 de Octubre al día 4 de Octubre de 2025) La programación sera la siguiente: https://www.navajanegra.com/2025/index.html#schedules Se retransmitirá en directo desde: http://twitch.tv/navajanegra y si os va la marcha el CTF estará disponible desde el día 2 de octubre a las 9:00 hasta el…

👍10

16 Jul 2025, 08:08 UTC≈5,340 views8 reactionsread 28 August 2026

Microsoft Defender Antivirus: VulnerableDriver:WinNT/Winring0 Es posible que reciba una alerta de Antivirus de Microsoft Defender que identifique la detección: VulnerableDriver:WinNT/Winring0 Esta detección es válida. El controlador WinRing0 se ha clasificado como una vulnerabilidad conocida como se indica en CVE-2020-14979. Fuente: https://support.microsoft.com/es-es/windows/microsoft-defender-antivirus-vulnerab…

👍8

8 Jul 2025, 16:25 UTC≈5,690 views8 reactionsread 28 August 2026
Photo

#Securizame #HackingEtico #Formacion Nuestros amigos de Securizame , nos han mandado una formación de Hacking Ético, impartida por Dani Echeverri, diseñado para que aprendas en entornos reales, explotación de sistemas, herramientas de pentesting y entrenamientos 100% prácticos. No es un curso más. Es una experiencia intensiva para formarte en lo que realmente necesitas dominar: cómo se ataca, cómo se persiste y cóm…

👍8

20 Jun 2025, 11:35 UTC≈5,830 views9 reactionsread 28 August 2026

Filtración masiva expone 16.000 millones de contraseñas: Google, Apple, Facebook y más entre los afectados Una de las mayores filtraciones de datos en la historia de internet ha salido a la luz. SSe han encontrado más de 16.000 millones de credenciales expuestas en una recopilación masiva que incluye información sensible de usuarios de servicios como Google, Apple, Facebook, Amazon, PayPal, Netflix, Telegram y mucha…

👍7👎2

3 Jun 2025, 15:25 UTC≈4,830 views1 reactionsread 28 August 2026

#Telefónica #Movistar #FiltraciónDatos Telefónica investiga un supuesto 'hackeo' en Movistar Telefónica investiga un ciberataque que expuso 22 millones de registros de clientes de Movistar, principalmente en Perú. El grupo responsable, alias "Dedale", ya ha publicado una muestra con 1 millón de registros. Entre los datos filtrados se encontrarían: Nombres completos, DNI, Números de teléfono, Planes contratados ent…

👍1

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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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.

🔒Seguridad Informática
@seguridadinformatic4 · 29,172
Telegram ranks this channel #22 of 76 here — alongside 75 others — read 8 September 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list 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.

“Security News for Everyone” (@SeguridadInformatica), 7,842 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/SeguridadInformatica.

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.