Telegram RegisterThe public register of Telegram

Channel

Fail Auth

@failauth

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

203subscribers

+0 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002193422534
TypeChannel
Username@failauth
DescriptionНа этом канале я буду делиться своими открытиями, инсайтами из мира информационной безопасности и инструментами для пентеста. Связаться со мной: @konstanto0 Offensive security | Rad Cop https://radcop.online/ https://t.me/radcop_online
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live7 August 2026
Measurements held2
On Telegramt.me/failauth

Growth

2036 Aug 2026, 12:51 — 203 subscribers7 Aug 2026, 04:01 — 203 subscribers6 Aug 2026, 12:517 Aug 2026, 04:01
2 measurements taken within a single day. 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 202–204 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 04:01203no change
6 Aug 2026, 12:51203first reading

Engagement

20 posts held, back to 15 October 2025the 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.

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 4 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
52
Links
30

Lifetime counters from Telegram’s own channel header, read 7 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

223 reactions across 19 posts, in 24 distinct kinds. The most used accounts for 25.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍5625.1%
🔥5022.4%
3716.6%
❤‍🔥208.97%
🏆114.93%
👨‍💻83.59%
👀62.69%
😱41.79%
🤝41.79%
🥴41.79%
🎄31.35%
🎅31.35%
😁31.35%
😎31.35%
🍾20.897%
10.448%
🌚10.448%
🎃10.448%
🐳10.448%
👏10.448%
4 further kinds41.79%

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 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 223reactions 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 15 October 2025 to 4 July 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.

Telegram Stars

Stars received
1
across the posts below
Posts paid on
1
of 20 we hold a reading for · 5%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @failauth. 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 20 most recent posts we hold for this entry, published 15 October 2025 to 4 July 2026. 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

4 Jul 2026, 17:57 UTC128 views24 reactions1 Starread 7 August 2026
Photo

Наконец-то получил бумажку! Это было слишком жестко! 🤩

🔥123🍾2🎃1🏆1🐳1👀1💘1

29 May 2026, 17:26 UTC206 views11 reactionsread 7 August 2026
Photo

HTTP Request Smuggling → Privilege Escalation Разбирал задание с уязвимостью CL.TE (Content-Length / Transfer-Encoding). Сценарий: есть пользователь с низкими привилегиями, есть эндпоинт /admin.php?promote_uid=7. Задача — заставить администратора выполнить запрос от нашего имени. 1️⃣ Суть CL.TE Фронтенд читает длину тела через Content-Length. Бэкенд читает тело через Transfer-Encoding: chunked. Это несоответствие и

❤‍🔥4🔥3👍2🏆1🕊1

21 Apr 2026, 15:16 UTC464 views16 reactionsread 7 August 2026
Photo

Всем привет! Вот и у меня дошли руки поделиться впечатлениями и эмоциями об ообучнии и сдаче CWES. Как и обещал 🫡 Почитать можно тут.

🔥8❤‍🔥3👍3👀1👨‍💻1

16 Apr 2026, 09:03 UTC215 viewsread 7 August 2026

Всем, кто в теме, рекомендую к прочтению! 💻 Делясь знаниями, получаешь больше 🤝

16 Apr 2026, 09:03 UTC250 views6 reactionsread 7 August 2026
Forwarded from @pathsecure

Хей! Пост немного задержался... Но я принес вам Хабр-статью с моей рефлексией по итогам сдачи OSWE! Поделился своими мыслями и тактиками. https://habr.com/ru/articles/1024100/ - - - А я в ближайшие дни стартую новое приключение в сдачу OSEP 😎 #oswe #habr #education #cert

👀4🔥2

6 Apr 2026, 09:26 UTC264 views11 reactionsread 7 August 2026
Photo

Всем привет! 🕵‍♂️ Не сложилось у меня с CPTS, не зашло. Переиграл план, который по обучению расписал на год, и всё же решил углубляться в то, что по душе, а именно — в вебчик! Взял Golden-подписку на HTB и стартую CWEE. В общем, с проектами и обучением спать будет некогда. На этот счёт у меня одна из любимых фраз: «Тот, кто спит, тот видит только сны». Но всё же спать рекомендую — сертами менталку не залечишь. 🤪 П

🔥6👍3❤‍🔥1👨‍💻1

28 Mar 2026, 09:38 UTC244 views8 reactionsread 7 August 2026
Forwarded from @rmrf_0Photo

Продолжение серии про JWT - шесть новых статей Криптография, шифрование, библиотеки, OAuth/OIDC, XSS и продвинутые криптоатаки: 9. Криптография JWT для хакеров - ECDSA, RSA-PSS, EdDSA и где ломается математика 10. JWE — зашифрованные токены, Bleichenbacher, Invalid Curve, PBES2 DoS 11. JWT-библиотеки — рейтинг дырявости, Top 5 CVE, fingerprinting по токену 12. JWT в OAuth 2.0 и OIDC — token confusion, cross-service

👍6❤‍🔥1😱1

28 Mar 2026, 09:38 UTC189 views4 reactionsread 7 August 2026
Forwarded from @rmrf_0Photo

Опубликовал новые статьи из серии статей про JWT Не пугайтесь графика на скриншоте - он просто для наглядности того почему именно работает уязвимость От структуры токена до атак с PoC: 1. Почему JWT сломан by design 2. Анатомия токена 3. alg:none - одна строчка и ты admin 4. Algorithm Confusion - публичный ключ как пароль 5. kid injection - SQLi через заголовок токена 6. jku/x5u/jwk/x5c - весь заголовок это attack

👍3🌚1

24 Mar 2026, 08:16 UTC≈3,640 views14 reactionsread 7 August 2026

Prototype Pollution → Localhost Bypass Недавно решал веб-челлендж на НТВ (white-box). На первый взгляд — максимально простой сервис заметок на Express + Mongo. Но внутри оказалась очень интересная цепочка через server-side prototype pollution, которая приводит к обходу IP-проверки. 1️⃣ Первичный анализ В коде явно видно ограничение доступа к /flag: app.get('/flag', (req, res) => { const remoteAddress = req.con

👍8❤‍🔥3👨‍💻21

3 Mar 2026, 12:00 UTC256 views15 reactionsread 7 August 2026
Photo

Ну что… Наконец-то я его получил! 💻 Мелочь, а приятно. Как писал выше, подписку на обучение купил перед НГ. Учебный трек прошёл довольно быстро, но вот с экзаменом всё оказалось не так просто. С первого раза сдать не удалось 🤩 Завалился на все тачки - получил админа, но больше всего трудностей было с RCE. Если кратко: курс реально супер интересный. Лично мне проходить его было намного интереснее, чем PortSwigger Ac

🔥103😱2

3 Mar 2026, 09:38 UTC187 views7 reactionsread 7 August 2026
Forwarded from @infobesPhoto

Представьте: в углу офиса мирно стоит принтер, печатает отчёты… а в это время через него кто-то получает учётки сотрудников и заходит во внутреннюю сеть компании. Звучит неприятно? Ещё бы. В своей новой статье разобрал, почему устройства печати становятся удобной точкой входа для злоумышленников: стандартные пароли, утечки учётных данных через SNMP, pass-back-атаки и другие типовые векторы. В материале: — реальные

3👍2🤝2

2 Mar 2026, 17:24 UTC216 views10 reactionsread 7 August 2026

Всем привет! Уже весна, а я все никак не могу вернуться к актиновсти на канале. Год со старта довольно загружен: проекты, обучение, порой просто лень ☹️ Буду стараться делиться с вами полезным чаще. Тем более есть повод ⤵️ Про вашу инфраструктуру уже кое-что знают. Возможно, больше, чем вы. 5 марта в 16.00 на вебинаре мой коллега из ПК "РАД КОП" покажет, как безопаснику самому собрать картину своей внешней поверхно

5👍3🔥2

Showing the 12 most recent of 20 posts we hold for @failauth. 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 — 440,898 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 2 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“Fail Auth” (@failauth), 203 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/failauth.

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.