Telegram RegisterThe public register of Telegram
Telegram profile photo for 🌐Ciberseguridad, noticias y tips 🌐

Channel

🌐Ciberseguridad, noticias y tips 🌐

@amecimx

On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry

622subscribers

+11 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001323683488
TypeChannel
Username@amecimx
CreatedBetween 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live29 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 29 October 2026
On Telegramt.me/amecimx

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

609622615.57 August 2026 — 611 subscribers8 August 2026 — 611 subscribers15 August 2026 — 609 subscribers9 September 2026 — 613 subscribers18 September 2026 — 617 subscribers13 October 2026 — 619 subscribers21 October 2026 — 617 subscribers29 October 2026 — 622 subscribers7 August 202629 October 2026
8 measurements spanning 83 days, net +11. 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 607–624 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Oct 2026, 09:19622+5
21 Oct 2026, 18:06617-2
13 Oct 2026, 12:56619+2
18 Sept 2026, 14:41617+4
9 Sept 2026, 10:42613+4
15 Aug 2026, 18:04609-2
8 Aug 2026, 03:04611no change
7 Aug 2026, 20:11611first reading

Engagement

20 posts held, back to 7 April 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 1 page 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 20 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

14 reactions across 8 posts, in 4 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😱750.0%
👍321.4%
😢214.3%
🤔214.3%

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

Measured over the 20 most recent posts we hold, published 7 April 2026 to 5 August 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

5 Aug 2026, 22:10 UTC76 views2 reactionsread 8 August 2026

🌐 ¿Recibiste un SMS por una multa? Podría tratarse de una estafa 🌐 En las últimas semanas, se ha detectado un incremento en campañas de smishing (phishing mediante SMS), que notifican supuestas multas de tránsito o adeudos federales para presionar a las víctimas a ingresar a páginas web falsas. https://blog.ameci.org/recibiste-un-sms-por-una-multa-podria-tratarse-de-una-estafa/

😱2

24 Jul 2026, 21:05 UTC183 views1 reactionsread 8 August 2026

ARTICULO COMPLETO: https://blog.ameci.org/ia-genera-preocupacion-tras-intentar-vulnerar-un-sistema-durante-una-prueba-de-seguridad/

😱1

30 Jun 2026, 21:33 UTC290 viewsread 8 August 2026

ARTICULO COMPLETO: https://ameci.org/blog/filtran-datos-del-iphone-18-pro-tras-ciberataque-a-proveedor-de-apple

30 Jun 2026, 21:33 UTC246 viewsread 8 August 2026
Photo

🌐 Filtran datos del iPhone 18 Pro tras ciberataque a proveedor de Apple 🌐 Una filtración de información relacionada con el iPhone 18 Pro salió a la luz luego de que Tata Electronics, uno de los principales proveedores de Apple en la India, fuera víctima de un ciberataque que comprometió miles de archivos internos.

15 Jun 2026, 20:39 UTC320 viewsread 8 August 2026

ARTICULO COMPLETO: https://ameci.org/blog/claude-fable-5-cae-en-menos-de-48-horas-a-manos-de-una-vulnerabilidad

15 Jun 2026, 20:39 UTC248 viewsread 8 August 2026
Photo

🌐 Claude Fable 5 cae en menos de 48 horas a manos de una vulnerabilidad 🌐 El recién lanzado modelo de inteligencia artificial Claude Fable 5, desarrollado por Anthropic y presentado como una de las plataformas más avanzadas en materia de seguridad, habría sido vulnerado en menos de 48 horas tras su llegada al mercado.

1 Jun 2026, 22:24 UTC314 views1 reactionsread 8 August 2026

ARTICULO COMPLETO: https://ameci.org/blog/se-exponen-datos-de-beneficiarios-de-programas-del-bienestar-autoridades-investigan-incidente

👍1

1 Jun 2026, 22:24 UTC266 views1 reactionsread 8 August 2026
Photo

🌐 Se exponen datos de beneficiarios de programas del Bienestar; autoridades investigan incidente 🌐 Datos personales de beneficiarios de distintos programas sociales del Gobierno de México habrían sido expuestos tras un incidente de ciberseguridad relacionado con la plataforma de los Programas para el Bienestar.

🤔1

28 May 2026, 22:14 UTC274 viewsread 8 August 2026

ARTICULO COMPLETO: https://ameci.org/blog/investigan-presunto-hackeo-a-plataforma-de-capacitacion-de-proteccion-civil-en-mexico

28 May 2026, 22:14 UTC252 views3 reactionsread 8 August 2026
Photo

🌐 Investigan presunto hackeo a plataforma de capacitación de Protección Civil en México 🌐 La Coordinación Nacional de Protección Civil (CNPC) confirmó que se encuentra investigando un presunto ciberataque contra la plataforma preparados.gob.mx.

😱2😢1

21 May 2026, 21:37 UTC291 viewsread 8 August 2026

ARTICULO COMPLETO: https://ameci.org/blog/github-vulnerado-robando-miles-de-repositorios-internos

21 May 2026, 21:37 UTC261 viewsread 8 August 2026
Photo

🌐 GitHub vulnerado robando miles de repositorios internos 🌐 El ataque fue atribuido al grupo de hackers TeamPCP, quienes afirmaron haber obtenido miles de repositorios privados y amenazaron con vender la información robada en foros clandestinos.

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

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

“🌐Ciberseguridad, noticias y tips 🌐” (@amecimx), 622 subscribers as measured 29 October 2026. Telegram Register, tgregister.com/channel/amecimx.

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.