Telegram RegisterThe public register of Telegram
Telegram profile photo for 🛡 Pentesting Web

Channel

🛡 Pentesting Web

@PentestingWeb

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

1,362subscribers

+22 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001358276202
TypeChannel
Username@PentestingWeb
CreatedBetween 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live24 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 24 August 2026
On Telegramt.me/PentestingWeb

Growth

1,3401,3621,3517 August 2026 — 1,340 subscribers7 August 2026 — 1,340 subscribers7 August 2026 — 1,342 subscribers10 August 2026 — 1,347 subscribers14 August 2026 — 1,351 subscribers20 August 2026 — 1,359 subscribers24 August 2026 — 1,362 subscribers7 August 202624 August 2026
7 measurements spanning 17 days, net +22. 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 1,337–1,365 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Aug 2026, 02:361,362+3
20 Aug 2026, 12:361,359+8
14 Aug 2026, 00:261,351+4
10 Aug 2026, 09:011,347+5
7 Aug 2026, 15:441,342+2
7 Aug 2026, 06:001,340no change
7 Aug 2026, 05:491,340first reading

Engagement

20 posts held, back to 23 June 2026the 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.

ERR · 30 days
11.0%
avg views ÷ 1,362 subscribers
Avg views / post
150
2 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
2
of 20 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 5 August 2026
Posts held20 (23 June 20265 August 2026)
Views total299
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 06:00 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.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1100.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 1reactions 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.

Recent posts

5 Aug 2026, 12:19 UTC86 viewsread 7 August 2026
Forwarded from @SeguInfoChannel

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

30 Jul 2026, 21:47 UTC213 viewsread 7 August 2026

🔴 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

23 Jul 2026, 19:40 UTC290 viewsread 7 August 2026

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

23 Jul 2026, 02:14 UTC263 viewsread 7 August 2026

🤖 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

19 Jul 2026, 03:05 UTC279 viewsread 7 August 2026

🔴 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

17 Jul 2026, 17:56 UTC238 viewsread 7 August 2026

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

16 Jul 2026, 13:05 UTC211 viewsread 7 August 2026
Forwarded from @SeguInfoChannel

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

15 Jul 2026, 14:53 UTC223 viewsread 7 August 2026
Forwarded from @SeguInfoChannel

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

14 Jul 2026, 00:35 UTC220 viewsread 7 August 2026

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

14 Jul 2026, 00:31 UTC230 viewsread 7 August 2026

🔴 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

12 Jul 2026, 15:16 UTC238 views1 reactionsread 7 August 2026
Forwarded from @SeguInfoChannel

Guía de hardening para Linux https://blog.segu-info.com.ar/2026/07/guia-de-hardening-para-linux.html

👍1

3 Jul 2026, 00:05 UTC363 viewsread 7 August 2026

🛡️ 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.

Forward network

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.

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

“🛡 Pentesting Web” (@PentestingWeb), 1,362 subscribers as measured 24 August 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.