Telegram RegisterThe public register of Telegram
Telegram profile photo for Mobile AppSec World

Channel

Mobile AppSec World

@mobile_appsec_world

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

8,589subscribers

+192 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001286683490
TypeChannel
Username@mobile_appsec_world
DescriptionНовости из мира безопасности мобильных приложений, а так же интересные статьи, обзоры инструментов, доклады, митапы и многое другое... По всем вопросам - @Mr_R1p
Created30 April 2020 — measured — cross-checked against a third-party dataset (TGDataset)
First recorded6 August 2026
Last confirmed live12 November 2026
Measurements held27
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/mobile_appsec_world

Topic

Technology — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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 the other topics.

Growth

8,3438,6248,483.56 August 2026 — 8,397 subscribers7 August 2026 — 8,398 subscribers10 August 2026 — 8,394 subscribers13 August 2026 — 8,391 subscribers16 August 2026 — 8,388 subscribers19 August 2026 — 8,395 subscribers22 August 2026 — 8,397 subscribers26 August 2026 — 8,386 subscribers29 August 2026 — 8,374 subscribers1 September 2026 — 8,371 subscribers4 September 2026 — 8,369 subscribers9 September 2026 — 8,358 subscribers13 September 2026 — 8,360 subscribers17 September 2026 — 8,354 subscribers26 September 2026 — 8,343 subscribers4 October 2026 — 8,405 subscribers11 October 2026 — 8,587 subscribers15 October 2026 — 8,598 subscribers18 October 2026 — 8,591 subscribers21 October 2026 — 8,586 subscribers24 October 2026 — 8,588 subscribers27 October 2026 — 8,624 subscribers30 October 2026 — 8,615 subscribers1 November 2026 — 8,613 subscribers4 November 2026 — 8,610 subscribers8 November 2026 — 8,600 subscribers12 November 2026 — 8,589 subscribers8,5896 August 202612 November 2026
27 measurements spanning 98 days, net +192. 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 8,301–8,666 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
12 Nov 2026, 06:598,589-11
8 Nov 2026, 00:378,600-10
4 Nov 2026, 17:388,610-3
1 Nov 2026, 23:368,613-2
30 Oct 2026, 05:178,615-9
27 Oct 2026, 07:298,624+36
24 Oct 2026, 16:378,588+2
21 Oct 2026, 16:098,586-5
18 Oct 2026, 13:418,591-7
15 Oct 2026, 04:468,598+11
11 Oct 2026, 19:578,587+182
4 Oct 2026, 23:598,405+62
26 Sept 2026, 01:218,343-11
17 Sept 2026, 16:388,354-6
13 Sept 2026, 10:218,360+2
9 Sept 2026, 18:568,358-11
4 Sept 2026, 16:388,369-2
1 Sept 2026, 04:458,371-3
29 Aug 2026, 09:038,374-12
26 Aug 2026, 04:388,386first reading

Engagement

26 posts held, back to 29 May 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 45 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
12.7%
avg views ÷ 8,589 subscribers
Avg views / post
1,090
3 posts measured
Reaction rate
0.976%
reactions ÷ views · ER floor
Posts in window
3
of 26 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 23 October 2026
Posts held26 (29 May 2026 – 23 October 2026)
Views total3,280
Reactions total32
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Nov 2026, 01:34 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.

What this channel posts

Photos
195
Videos
12
Links
809

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

267 reactions across 21 posts, in 18 distinct kinds. The most used accounts for 27.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤7427.7%
🔥6022.5%
👍4516.9%
🤡207.49%
😁186.74%
👎155.62%
🤣155.62%
🍾41.50%
✍31.12%
🐳20.749%
💩20.749%
🤮20.749%
🥰20.749%
🎉10.375%
👏10.375%
👾10.375%
😭10.375%
🤪10.375%

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

Measured over the 26 most recent posts we hold, published 29 May 2026 to 23 October 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

Telegram’s own ‘edited’ marker: 0 of 3 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

23 Oct 2026, 11:07 UTC≈1,160 views20 reactionsread 14 November 2026
Forwarded from @VPCBriefPhoto

SANS выпустила отчет AI Cybersecurity Careers 2026: The Market Reality Это один из первых материалов, описывающих трансформацию рынка труда в кибербезопасности из-за ИИ. Для каждой роли указаны: названия аналоги, кто недавно разместил вакансии, описание роли и почему она появилась, медианные значения и вилки годовых зарплат. Источник для анализа - реальные опубликованные вакансии. Некоторые сомнения в объективност…

❤9👍6🔥3🎉1👾1

Signed Yury Shabalin

23 Oct 2026, 11:06 UTC≈1,070 views10 reactionsread 14 November 2026

Больше папок по ИБ! Агенты уже замечательно умеют сортировать файлы, раскладывать музыку по жанрам и исполнителям, структурировать всякое на домашних компьютерах. Но пока что в телегу такой AI-функционал не завезли, зато есть механизм папок - которым я очень активно пользуюсь и вам советую. Но так как самому составлять не всегда удается - периодически подписываюсь на уже собранные папки. И хоть я в последнее время…

👎3👍2💩2🔥2🤪1

Signed Yury Shabalin

23 Oct 2026, 10:39 UTC≈1,050 views2 reactionsread 14 November 2026
Forwarded from @r3m4z3

Observing Android’s Binder Trust Boundary with eBPF Построение runtime-наблюдателя за Binder IPC в Android с помощью eBPF. Автор рассматривает Binder не просто как IPC-механизм, а как security trust boundary, потому что именно на этом уровне Android понимает, кто вызывает какой сервис, а дальше на этой идентичности строятся getCallingUid(), SELinux Binder rules и решения самих system services.

❤2

Signed Yury Shabalin

12 Oct 2026, 11:30 UTC≈1,830 views9 reactionsread 14 November 2026
Photo

🔥 ИНТЕНСИВ ПО БЕЗОПАСНОСТИ: ПРОВЕРКА НА ПРОЧНОСТЬ Друзья, 14 октября в Москве стартует практический форум для тех, кто занимается анализом защищенности. 💡 Почему «мы проверились» — это не равно «мы поняли риски»? 💡 Как не купить красивый отчет вместо реального уровня защиты? 💡 Где грань между пентестом, Red Team и Purple Team? 🎟 Участие для CISO, руководителей департаментов безопасности и технических специалистов и…

🔥8❤1

Signed Yury Shabalin

12 Oct 2026, 11:30 UTC≈1,490 views3 reactionsread 14 November 2026

Новое мероприятие от авторов «Территория безопасности» Всем привет! По какой-то причине мне очень нравится форум Территория Безопасности. Когда-то, когда он проходил самый первый раз, мы стояли там со стендом Стинга. Было достаточно много людей, выступление, интерактив, где мы в реальном времени анализировали приложение, много крутых людей, с кем удалось познакомиться, а еще я тогда первый раз на стенд выложил теле…

👍3

Signed Yury Shabalin

3 Oct 2026, 16:29 UTC≈2,070 views34 reactionsread 14 November 2026

Ну а мы всегда готовы помочь, хоть с анализом и устранением уязвимостей, хоть с защитой приложения ;) (с) не является публичной офертой :D

🔥11👎8❤5👍5😁3🤮2

Signed Yury Shabalin

3 Oct 2026, 16:28 UTC≈1,710 views9 reactionsread 14 November 2026
Forwarded from @alukatsky

Хакеры, взломавшие TEZ TOUR и Додо-Пицца, используют интересную тактику – они публикуют полноценные разборы своих действий и недостатков защиты своих жертв, по шагам рассказывая, как им удалось проникнуть внутрь. В случае с Додо 🦤 началось все с анализа мобильного приложения, в котором хранилась внутренняя кухня ИТ-инфраструктуры, которая и послужила отправной точки для нападающих. Запомните этот факт. 2 октября Fin…

❤9

Signed Yury Shabalin

3 Oct 2026, 16:28 UTC≈1,530 views2 reactionsread 14 November 2026

Мобильное приложение, как точка входа На нескольких конференциях, во многих статьях и при любом удобном случае я говорил о том, что исследование мобильного приложения может стать ооочень хорошей отправной точкой для нападающих, потому что внутри порой сожно найти очень вкусную информацию. И как приятно осознавать, что это все еще актуально. Хотя и жаль ребят, кому пришлось с этим столкнуться. Помните, что далеко н…

❤2

Signed Yury Shabalin

28 Sept 2026, 17:13 UTC≈1,840 views16 reactionsread 14 November 2026
Forwarded from @android_guards_today

Я редко скидываю сюда статьи из чужих блогов, потому что таких "новостных рупоров" и без меня уже больше чем надо. Но эта статья определенно заслуживает вашего внимания. Мне она прямо "зашла" наверное еще и потому, что я буквально недавно нашел очень похожую цепочку уязвимостей на другом устройстве. Впрочем об этом я расскажу когда-нибудь потом, когда выйдет фикс от вендора. В статье же описан довольно забавный вект…

❤11👍5

Signed Yury Shabalin

26 Sept 2026, 10:02 UTC≈2,120 views9 reactionsread 14 November 2026

Внезапно я вернулся :) И сразу с предложением поиграть в CTF) Интересно, будет ли хотя бы одна команда без агентов?))

😁8🔥1

Signed Yury Shabalin

26 Sept 2026, 10:01 UTC≈1,830 views5 reactionsread 14 November 2026
Photo

Регистрация на SolarCTF открыта ☀️ Первые студенческие соревнования по кибербезопасности от «Солара» — возможность проверить свои навыки на практике, собрать команду и побороться за призы. 📍Что важно знать: ✦ Команды — до 5 человек ✦ Старт — 17 октября в 12:00 (МСК) ✦ Финиш — 18 октября в 12:00 (МСК) ✦ 24 часа на выполнение заданий Общий призовой фонд — 300 000 ₽* + лимитированный мерч. Участвовать можно, если те…

🐳2👎2👍1

Signed Yury Shabalin

18 Jul 2026, 13:39 UTC≈3,450 views34 reactionsread 14 November 2026
Forwarded from @sib_compsec

Semgrep Rules Последнее время мы с командой всё чаще задумывались о том, что mobsfscan в части своего Semgrep-компонента, мягко говоря, местами глючный и довольно ограниченый. А если попробовать найти достаточно полный набор Semgrep-правил для мобильных приложений, быстро выясняется, что хорошие правила разбросаны по всему необъятному интернету🔞 Поэтому мы решили собрать всё это в одном месте и создали репозиторий…

❤18👍10🔥5👏1

Signed Yury Shabalin

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

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.

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Life-Hack - Хакер
@haccking · 63,001
Telegram ranks this channel #38 of 85 here — alongside 84 others — read 21 August 2026
The Bug Bounty Hunter
@thebugbountyhunter · 52,192
Telegram ranks this channel #47 of 60 here — alongside 59 others — read 25 August 2026
OSINT mindset
@osint_mindset · 64,939
Telegram ranks this channel #49 of 83 here — alongside 82 others — read 21 August 2026
SecurityLab.ru
@SecLabNews · 86,538
Telegram ranks this channel #49 of 90 here — alongside 89 others — read 18 August 2026

This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Mobile AppSec World” (@mobile_appsec_world), 8,589 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/mobile_appsec_world.

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.