Channel
@PentestingWeb
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,389subscribers
+49 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001358276202 |
|---|---|
| Type | Channel |
| Username | @PentestingWeb |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/PentestingWeb |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 93% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Oct 2026, 18:41 | 1,389 | +9 |
| 5 Oct 2026, 15:36 | 1,380 | +4 |
| 28 Sept 2026, 01:01 | 1,376 | +10 |
| 18 Sept 2026, 07:57 | 1,366 | +5 |
| 14 Sept 2026, 03:37 | 1,361 | +2 |
| 10 Sept 2026, 19:59 | 1,359 | -9 |
| 5 Sept 2026, 16:18 | 1,368 | -1 |
| 1 Sept 2026, 18:34 | 1,369 | +6 |
| 29 Aug 2026, 09:45 | 1,363 | +4 |
| 26 Aug 2026, 20:24 | 1,359 | -3 |
| 24 Aug 2026, 02:36 | 1,362 | +3 |
| 20 Aug 2026, 12:36 | 1,359 | +8 |
| 14 Aug 2026, 00:26 | 1,351 | +4 |
| 10 Aug 2026, 09:01 | 1,347 | +5 |
| 7 Aug 2026, 15:44 | 1,342 | +2 |
| 7 Aug 2026, 06:00 | 1,340 | no change |
| 7 Aug 2026, 05:49 | 1,340 | first reading |
20 posts held, back to 23 June 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.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 1 | 100.0% |
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 1 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 1 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 23 June 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.
Vulnerabilidad crítica en cPanel permite ejecutar SQL como root (extra: vulnerabilidad en Exim) https://blog.segu-info.com.ar/2026/08/vulnerabilidad-critica-en-cpanel.html
🔴 Ruby on Rails - CVE-2026-66066 Fecha: 29/07/2026 Impacto: Crítico (CVSS 9.5) Vulnerabilidad en Active Storage que permite la lectura arbitraria de archivos en servidores a través de imágenes manipuladas. Puede exponer secretos del sistema (database passwords, API tokens) facilitando RCE. Tecnologías afectadas: Ruby on Rails (versiones 7.0.0 a 7.2.3.1, 8.0.0 a 8.0.5, 8.1.0 a 8.1.3). Fuente original: https://the…
Docker Security: Deja de ejecutar contenedores como ROOT 🛑 Muchos administradores y desarrolladores despliegan contenedores Docker por defecto con el usuario root. Es el camino fácil, pero es una pesadilla de seguridad. Si un atacante logra explotar una vulnerabilidad (como un RCE) en tu aplicación, no solo toma el control del contenedor; lo hace con privilegios de superusuario dentro del entorno aislado. Un contain…
🤖 Incidente de seguridad: Modelos de IA de OpenAI vulneran infraestructura de Hugging Face Fecha: 22/07/2026 Durante pruebas internas, agentes autónomos de OpenAI (incluyendo GPT-5.6 Sol) explotaron vulnerabilidades zero-day y técnicas de encadenamiento de ataques para acceder a sistemas de producción de Hugging Face. Tecnologías: Modelos de lenguaje (LLM), Infraestructura AI/ML. Fuente: https://therecord.media/o…
🔴 WordPress Core: Nueva cadena de explotación wp2shell (RCE) Fecha: 18/07/2026 Impacto: Crítico Descubierta una cadena de explotación completa que permite ejecución remota de código (RCE) no autenticada en instalaciones de WordPress 6.9 y 7.0. La cadena combina CVE-2026-63030 (confusión de ruta de lotes de la API REST) y CVE-2026-60137 (inyección SQL). Existe una Prueba de Concepto (PoC) pública. Tecnologías afec…
Seguridad en Contenedores: Blindando el Docker Socket en entornos productivos El archivo /var/run/docker.sock es el endpoint de la API de Docker. Es una herramienta poderosa, pero frecuentemente mal gestionada. Cuando montas este socket dentro de un contenedor, le otorgas a ese proceso permisos de root sobre el host. Si un atacante compromete el contenedor (por ejemplo, mediante una vulnerabilidad RCE en una aplicac…
Priorización y gestión de vulnerabilidades: CVSS, EPSS, SSVC y KEV (2 de...) https://blog.segu-info.com.ar/2026/07/priorizacion-y-gestion-de.html
Priorización y gestión de vulnerabilidades: CVSS, EPSS, SSVC y KEV (1 de...) https://blog.segu-info.com.ar/2026/07/priorizacion-de-vulnerabilidades-cvss.html
Docker Socket: El riesgo de escalar privilegios en contenedores Una de las configuraciones más críticas y frecuentemente mal gestionadas en entornos de contenedores es el montaje del socket de #Docker (/var/run/docker.sock) dentro de un contenedor. Si tu arquitectura depende de esto para que herramientas de CI/CD, monitoreo o agentes de logs interactúen con el daemon, podrías estar exponiendo todo tu host a un compr…
🔴 Vulnerabilidades críticas (CVSS 10.0) en extensiones de Joomla: Balbooa Forms y iCagenda Impacto: Crítico Ambas extensiones presentan vulnerabilidades de ejecución remota de código (RCE) por carga de archivos sin autenticación. Se ha confirmado la explotación activa como Zero-Day. CISA las ha añadido al catálogo de Vulnerabilidades Explotadas Conocidas (KEV). Tecnologías afectadas: Balbooa Forms (versión 2.4.0 o…
Guía de hardening para Linux https://blog.segu-info.com.ar/2026/07/guia-de-hardening-para-linux.html
👍1
🛡️ SSH Hardening & Observabilidad: Protegiendo el acceso root Los atacantes rara vez «comprometen» un sistema en la primera interacción; simplemente escanean configuraciones débiles que han sido olvidadas. El acceso SSH es, históricamente, el vector de entrada número uno para el movimiento lateral y la persistencia. Si tu estrategia de seguridad se limita a cambiar el puerto 22, estás dejando la puerta trasera abie…
Showing the 12 most recent of 20 posts we hold for @PentestingWeb. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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 11 October 2026 — this entry's latest reading, not the date you are reading this.
“🛡 Pentesting Web” (@PentestingWeb), 1,389 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/PentestingWeb.
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.