Telegram RegisterThe public register of Telegram

Channel

Кавычка

@webpwn

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry

15,967subscribers

+3 since we began measuring on 5 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001045163505
TypeChannel
Username@webpwn
DescriptionПрактическая безопасность. Уязвимости и атаки на веб-приложения. Чат @WebPwnChat Только авторский контент, без репостов и рекламы (простите). Вместо лайка: https://t.me/webpwn?boost Платный канал: https://t.me/tribute/app?startapp=s2Vr
Created1 March 2016measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held7
Confirmed unchanged2 times, most recently 12 August 2026
On Telegramt.me/webpwn

Growth

15,96215,96715,964.55 August 2026 — 15,964 subscribers6 August 2026 — 15,964 subscribers6 August 2026 — 15,962 subscribers7 August 2026 — 15,965 subscribers8 August 2026 — 15,967 subscribers9 August 2026 — 15,963 subscribers11 August 2026 — 15,967 subscribers5 August 202611 August 2026
7 measurements spanning 6 days, net +3. 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 15,961–15,968 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 22:2315,967+4
9 Aug 2026, 23:3715,963-4
8 Aug 2026, 20:3815,967+2
7 Aug 2026, 21:2115,965+3
6 Aug 2026, 21:2115,962-2
6 Aug 2026, 02:1915,964no change
5 Aug 2026, 23:0115,964first reading

Engagement

19 posts held, back to 14 November 2023the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 17 pagesof 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 17 October 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
83
Videos
2
Links
184

Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

2,707 reactions across 18 posts, in 9 distinct kinds. The most used accounts for 64.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥1,75664.9%
custom 535966702413599468935213.0%
custom 53415869813463638462689.90%
❤‍🔥1605.91%
custom 53413238372900737841083.99%
custom 5465383954750122781291.07%
custom 5339454611688278598190.702%
custom 5256161284419761757120.443%
👍30.111%

Custom emoji. 6 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

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 18 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 2,707reactions 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 14 November 2023 to 17 October 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Telegram Stars

Stars received
74
across the posts below
Posts paid on
3
of 18 we hold a reading for · 17%
Most on one post
42
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @webpwn. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 19 most recent posts we hold for this entry, published 14 November 2023 to 17 October 2024. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

17 Oct 2024, 10:37 UTC≈47,300 views249 reactions42 Starsread 13 August 2026
Photo

Многие юзают инфу о выданных сертификатах, чтобы узнать поддомены компании, например в crt.sh Но не только лишь все знают, как узнать другие домены одного владельца в ru зоне. Раньше для этого юзал 1stat.ru, но он уже больше как архив, а сейчас использую backorder.ru Эт такой сервис для киберсквоттеров, который позволяет наблюдать за истекшими доменами и их перехватить. Ну и помимо этой функции, доступен расширенный

🔥195custom 534132383729007378442❤‍🔥9👍3

Signed Bo0oM

1 Aug 2024, 10:37 UTC≈40,100 views330 reactions26 Starsread 13 August 2026

Что опасного в публичном отображении phpinfo? Сдаешь такой в багбаунти, а тебе говорят, ну где импакт, CVSS 2.6? А ты такой, ну смотри какой импакт: - Дает узнать о конфигурации PHP, в том числе о версии, установленных модулях, путях к файлам и т.д. Что поможет эксплуатировать другие уязвимости. - Раскрывается информация о реальном расположении серверов (если они скрыты за anti-DDOS или CDN) - Отдельно стоит отмети

custom 5341586981346363846239🔥48custom 534132383729007378438❤‍🔥5

Signed Bo0oM

16 May 2024, 10:37 UTC≈36,800 views105 reactions6 Starsread 13 August 2026
Photo

#owncloud Для owncloud была классная CVE-2023-49105 Сплоет реализован в качестве прокси, которая подписывает запросы и можно через нее ходить на dav://, используя клиент Filezilla, Cyberduck, короч кто-что юзает. Сначала ставим ten, запускаем проксю, но не наслаждаемся. Потому что из коробки сплоет у меня не завелся, клиенты, видимо, не могут корректно распарсить ответ. А я просто вывел ответ от прокси через prin

🔥49custom 533945461168827859819custom 534132383729007378419custom 534158698134636384618

Signed Bo0oM

14 May 2024, 10:37 UTC≈28,200 views166 reactionsread 13 August 2026

#OSINT #SSH Вспомнил тут про старый трюк, можно тестануть: ssh whoami.filippo.io Короч, когда ты подключаешься по ssh, твой ssh-agent перебирает всеми ключами, которые у тебя в него подключены. Это может привести к прикольной деанонимизации, если на стороне сервера включено логирование ssh ключей, которыми пытались подключиться. Ключики можно собирать как на гитхабе: https://github.com/Oleg.keys Так и на гитлабе

🔥92custom 535966702413599468930custom 546538395475012278129custom 525616128441976175712❤‍🔥3

Signed Bo0oM

12 Apr 2024, 10:37 UTC≈28,500 views146 reactionsread 13 August 2026

В дискуссии спросили, ну чего опасного в том, что есть XSS на поддомене без юзеров. Допустим, есть у нас site.kek, а ты нашел уязвимость на subdomain.site.kek Что может дать XSS на поддомене, где обычный одностраничный лэндинг, нет никаких данных пользователя? Штош, импакт такой: - Не только лишь все знают, что поддомен может ставить куки, в том числе на главный сайт (а точнее на весь скоуп, включая другие поддоме

🔥77custom 535966702413599468955custom 53415869813463638466custom 53413238372900737845❤‍🔥3

Signed Bo0oM

3 Apr 2024, 10:37 UTC≈29,400 views163 reactionsread 13 August 2026
Photo

Короч, чтоб тебя всякие shodan, censys и прочие умники не сканировали, а еще и не попадать под их поисковую выдачу, рекомендую такой дефолтный конфиг для nginx: server { listen 80 default_server; listen 443 ssl http2 default_server; # Если есть IPv6 listen [::]:80 default_server; listen [::]:443 ssl http2 default_server; ssl_reject_handshake on; server_name _; location / {

🔥108custom 535966702413599468934❤‍🔥19custom 53413238372900737842

Signed Bo0oM

12 Mar 2024, 10:37 UTC≈25,800 views148 reactionsread 13 August 2026
Photo

#firebase Короч. Встречали firebase на страницах? Обычно это подключение js-ника и конфиг вида firebase.initializeApp({ apiKey: "VHkgcGlkb3IpMDAwKSkpKSkpKSk=", authDomain: "blablabla" ... }); Иногда это используется для заявок, фидбэков и вот этого всего. И если его неправильно готовят, то на нем можно зарегистрироваться через signupNewUser (тыц) и получить доступ к данным, которые собирали сотрудники (в мо

🔥87custom 535966702413599468946❤‍🔥15

Signed Bo0oM

5 Mar 2024, 10:37 UTC≈24,100 views131 reactionsread 13 August 2026
Photo

#OpenAPI #Swagger Короч, в extentions для burp suite есть OpenAPI Parser, это штука, которая позволяет брать всякие swagger.json, превращать их в запросы, сканить и вот это все. Какая с ним проблема. Он не умеет работать с третьей спекой. Валится и все тут. Выход - сконвертировать в OAS 2.0 У меня был огромный swagger и классический editor.swagger.io не смог его прожувать и вкладка зависала. Но есть замечательный A

custom 535966702413599468992🔥34custom 53415869813463638465

Signed Bo0oM

1 Mar 2024, 10:19 UTC≈21,900 views104 reactionsread 13 August 2026

Доступ в двойную кавычку Подключи подписку - и получи доступ к контенту раньше, чем будет его публикация, к щепотке уникального контента и чату без цензуры. Твой вклад помогает развивать этот канал и делать его лучше 💣

custom 535966702413599468987🔥9❤‍🔥6custom 53413238372900737842

Signed Bo0oM

27 Feb 2024, 10:37 UTC≈27,200 views159 reactionsread 13 August 2026

Есть такая штука nextjs, несколько месяцев назад они добавили новую "фишку" распределение нагрузки - под капотом поднимается несколько микросервисов. Каждый из которых занимается своей частью обработки запроса. Работает все примерно так-же как и обычный прокси сервер, запрос приходит, обрабатывается, и через стороннюю библиотеку проксируется на другой порт. Собственно именно это место нас и интересует. В HTTP есть т

🔥149custom 53596670241359946898❤‍🔥2

Signed Bo0oM

19 Feb 2024, 13:03 UTC≈32,100 views206 reactionsread 13 August 2026

Быстро и дешево брутим хэши Короч, есть чуваки такие, immers.cloud По сути это хостинг с арендой видеокарт. А так как я занимался проектом passleak.ru, иногда нужно было разгадывать хэшики, решил не покупать под это оборудование. Вышло круто. Тут есть два варианта развития событий. Арендуем видеокарту (какую - по желанию, они там выкатили какие-то ультра-модные H100, но мне и 2080 часто хватает), грузим туда наши

🔥178❤‍🔥28

Signed Bo0oM

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Citation-graph rank

Citation-graph rank — 197,329 of 1,160,990entries 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.

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.

Names

Channels on the register whose handles appear in this channel's posts.

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.

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

“Кавычка” (@webpwn), 15,967 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/webpwn.

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.