Telegram RegisterThe public register of Telegram

Channel

AppSecs

@AppSecs

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

136subscribers

+0 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-1001980255896
TypeChannel
Username@AppSecs
CreatedBetween 1 March 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/AppSecs

Growth

1367 Aug 2026, 17:12 — 136 subscribers8 Aug 2026, 23:31 — 136 subscribers7 Aug 2026, 17:128 Aug 2026, 23:31
2 measurements spanning 1 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 135–137 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 23:31136no change
7 Aug 2026, 17:12136first reading

Engagement

17 posts held, back to 22 March 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 17 posts for this entry, the most recent from 8 November 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
25
Videos
2
Links
55

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

142 reactions across 16 posts, in 5 distinct kinds. The most used accounts for 43.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥6243.7%
👍4128.9%
2920.4%
🌚96.34%
🤡10.704%

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

Measured over the 17 most recent posts we hold, published 22 March 2025 to 8 November 2025, 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

8 Nov 2025, 10:30 UTC355 views8 reactionsread 8 August 2026
Forwarded from @standoff_bb_tipsPhoto

🤔 Эксплуатация XSS без скобок и точек с запятой Главная цель — обход WAF, который блокирует типичные паттерны XSS. Как это работает ⤵️ 🔴 С помощью запятых можно объединить несколько выражений и вернуть последнее из них 🔴 Замена onerror на eval позволяет выполнить сообщение об ошибке как код 🔴 Вызванные ошибки станут частью сообщения об ошибке 🔴 Если тебе удалось преобразовать сообщение об ошибке в корректный код,

🔥53

19 Sept 2025, 17:24 UTC448 views9 reactionsread 8 August 2026
Photo

100 лет не CTF'ил и решил вспомнить молодость, вылезти из пещеры и поиграть в составе команды SiBears на VolgaCTF. Это был мой первый визит в Самару и очное посещение VolgaCTF. Помимо участия в соревнованиях получилось пообщаться с некоторыми интересными людьми, послушать доклады (в этот раз было много про баг баунти), полутать мерча, а так же посетить похек (раньше я думал, что Похек - это безопасник из Бастиона 🌚)

9

27 Aug 2025, 12:05 UTC433 views8 reactionsread 8 August 2026
Photo

Совершенно неожиданно выиграл книгу от @study_security. Неожиданно и приятно :) Благодарю! Придётся Будем развиваться.

🔥6👍2

22 Aug 2025, 06:30 UTC432 views10 reactionsread 8 August 2026
Photo

Первый день OFFZONE прошел неплохо

🔥10

17 Aug 2025, 10:40 UTC426 views4 reactionsread 8 August 2026
Forwarded from @bbountykzPhoto

Там shodan акк за 5$ можно взять

🔥4

4 Jul 2025, 02:17 UTC554 views4 reactionsread 8 August 2026
Forwarded from @event_securityPhoto

Что – ZeroNights Где – Санкт-Петербург, LOFT HALL #7 Когда – 26 ноября ⛓ Ссылка – zeronights.ru 📝 Думаю, что про эту конференцию и так все знают. На такое мы ходим. 🗓 Твой Пакет Мероприятий | 🗓Наш календарь 🛍 Другие каналы

👍4

30 Jun 2025, 05:28 UTC488 views8 reactionsread 8 August 2026
Photo

Задумывались о сомах? Same Origin Method Execution (SOME) — это класс уязвимостей веб-приложений, при которых злоумышленник через параметр обратного вызова (callback) вынуждает браузер жертвы выполнить произвольный JavaScript-метод в контексте доверенного домена. Звучит знакомо? Да, очень похоже на эксплуатацию классического JSONP callback, когда злоумышленник передаёт в параметре callback произвольный JavaScript-к

👍8

19 Jun 2025, 07:56 UTC411 views10 reactionsread 8 August 2026
Photo

Окак А отказаться можно?

🌚9🤡1

19 May 2025, 16:50 UTC499 views6 reactionsread 8 August 2026
Forwarded from @shadow_group_tgPhoto

Год назад эту защиту нельзя было обойти, однако сейчас это стало реально. Про интересную особенность рассказали в X. Дело в том, что раньше нельзя было использовать точку в протоколе, но теперь браузер Chromium ее поддерживает (URL вернет действительное имя хоста с любым недействительным протоколом, даже с точкой) Соответственно, мы можем использовать пэйлоад типа evil.com://www.example.com. Хост www.example.com бу

👍6

16 Apr 2025, 07:17 UTC468 views19 reactionsread 8 August 2026
Photo

Недавно зарепортил интересный недостаток, который достаточно высоко оценили с уровнем критичности high, но повысить impact получилось благодаря объединению двух low/medium недостатков. На некотором ресурсе X есть возможность оставлять комментарий в формате Markdown с некоторыми html-тегами. «Опасные» теги, такие как <script>, <iframe>, <img> фильтруются. Однако была возможность использовать другие интересные теги. 1.

👍10🔥81

7 Apr 2025, 13:50 UTC420 views5 reactionsread 8 August 2026
Photo

Что будет, если скрестить XSS и CSRF? Получится XSSI. 👁Cross Site Script Inclusion (XSSI) — это техника атаки (или уязвимость), позволяющая злоумышленникам похищать данные определенного типа через origin boundaries (дословно «границы сайта»), путем включения целевых данных с помощью тега SCRIPT в веб-страницу злоумышленника, как показано ниже: <SCRIPT src="http://target.example.jp/secret"></SCRIPT> Браузеры испо

👍4🔥1

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

Citation-graph rank

Citation-graph rank — 981,878 of 1,151,006entries 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

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

“AppSecs” (@AppSecs), 136 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/AppSecs.

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.