Telegram RegisterThe public register of Telegram
Telegram profile photo for #Arm1tage

Channel

#Arm1tage

@arm1tage

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

1,574subscribers

+2 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-1001651246693
TypeChannel
Username@arm1tage
CreatedBetween 1 December 2021 and 30 April 2023— 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/arm1tage

Growth

1,5691,5761,572.57 August 2026 — 1,572 subscribers8 August 2026 — 1,573 subscribers11 August 2026 — 1,569 subscribers14 August 2026 — 1,571 subscribers17 August 2026 — 1,575 subscribers20 August 2026 — 1,576 subscribers24 August 2026 — 1,574 subscribers1,5747 August 202624 August 2026
7 measurements spanning 17 days, net +2. 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,568–1,577 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Aug 2026, 06:081,574-2
20 Aug 2026, 11:471,576+1
17 Aug 2026, 19:041,575+4
14 Aug 2026, 15:251,571+2
11 Aug 2026, 11:271,569-4
8 Aug 2026, 01:261,573+1
7 Aug 2026, 11:321,572first reading

Engagement

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

Reaction mix

274 reactions across 19 posts, in 28 distinct kinds. The most used accounts for 25.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53888308914579176207025.5%
4717.2%
🔥248.76%
🤡248.76%
😁228.03%
❤‍🔥145.11%
💩114.01%
93.28%
🍌93.28%
🫡93.28%
👾72.55%
👎41.46%
31.09%
🆒20.73%
👀20.73%
👌20.73%
💊20.73%
🖕20.73%
🗿20.73%
10.365%
8 further kinds82.92%

Custom emoji. One row above is a 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 count beside it isTelegram’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 19 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 274reactions 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 5 February 2024 to 19 February 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

19 Feb 2025, 13:06 UTC≈9,290 views19 reactionsread 7 August 2026
Photo

Интеграция ИИ в Nuclei В последнем обновлении для нуклей (3.3.9) был добавлен флаг -ai, который позволяет на ходу генерировать темплейт на основе ваших запросов. Для начала пользования этой фичей нужно получить АПИ токен на сайте ProjectDiscovery. Затем запускаем нуклей с флагом auth: nuclei -auth И добавляем токен. Теперь мы можем пользоваться генератором темплейтов. Запуск выглядит следующим образом: nuclei -u "h

❤‍🔥8🤡43🆒2🍾1👍1

13 Feb 2025, 16:33 UTC≈2,110 views12 reactionsread 7 August 2026
Photo

Интеграция ИИ в расширения бурпа Сегодня вышел новый блог от портсвиггер, где они рассказывают про интеграцию ИИ в расширения. По их словам все данные, переданные таким расширениям будут "секьюрно" обработаны на стороне самого портсвиггера. Почему это может быть крайне полезно? Например, интеграция ИИ в расширение JS Miner позволила бы выискивать секретные данные в js файлах более точно, не полагаясь на привычный п

42👎2🗿2❤‍🔥1🤡1

3 Feb 2025, 16:12 UTC≈2,370 views14 reactionsread 7 August 2026
Photo

Спреим учетки под O365 В ходе Red Team-кампании учетные записи сотрудников играют ключевую роль в получении доступа внутрь. Чаще всего задействуются аккаунты Google и O365. Поговорим про O365. Для начала надо собрать почты сотрудников. Существуют разные сервисы: - Платные: phonebook, dehashed, snusbase, leakcheck, leakpeek; - Бесплатные но с ограниченным функционалом, вроде hunter[.]io, rocketreach[.]co или искать

🔥9🍌21🌭1💅1

31 Dec 2024, 22:06 UTC≈1,880 views18 reactionsread 7 August 2026

С новым годом, господа. Любви, смекалки, стальных нервов и задач, которых стоили того, чтобы вы их решали. С праздником!

14❤‍🔥4

13 Aug 2024, 16:58 UTC≈2,660 views13 reactionsread 7 August 2026

Web cache deception Слёту надо понять разницу между Cache Poisoning и Cache Deception: Cache Poisoning: Атакующий делает инъекцию в контент, который затем кэшируется для всех пользователей сервиса. Cache Deception: Атакующий делает инъекцию в контент, который при посещении жертвой кэшируется на сервисе и к нему может получить доступ только атакующий. Понятнее: У Серёги есть запрос, который возвращает ему его АПИ кл

custom 538883089145791762084🦄1

13 Aug 2024, 16:55 UTC≈1,690 views2 reactionsread 7 August 2026

Кто угадаёт о чем будет сейчас пост? Подсказка: это не сложно.

custom 53888308914579176202

13 Aug 2024, 16:55 UTC≈1,740 views3 reactionsread 7 August 2026

Так, я тут

custom 53888308914579176203

11 Apr 2024, 19:51 UTC≈2,670 views18 reactionsread 7 August 2026
Forwarded from @road_to_oscp

Today, we'll talk a bit about JavaScript recon in web applications. I've based my methodology on My Javascript Recon Process - BugBounty. Collecting links to JS files can be done using gau: gau example.com | grep -iE '\.js' | grep -ivE '\.json' | sort -u >> exampleJS.txt Alternatively, you can use waymore, which seems to be better: python3 waymore.py -i example.com -ko "\.js(\?|$)" We can also try fuzzing to fin

custom 538883089145791762012👾3🤡3

30 Mar 2024, 12:17 UTC≈1,930 views12 reactionsread 7 August 2026

[ XZ backdoor - CVE-2024-3094 ] ! Backdoor in upstream xz/liblzma leading to SSH server compromise ! Check: xz --version 5.6.0 & 5.6.1 — v u l n e r a b l e Update: sudo apt update && sudo apt install --only-upgrade liblzma5 Summary: https://boehs.org/node/everything-i-know-about-the-xz-backdoor How it all started (email): https://www.openwall.com/lists/oss-security/2024/03/29/4 GitHub Thread: https://web.arch

7👎2custom 53888308914579176202👌1

23 Mar 2024, 14:15 UTC≈1,850 views7 reactionsread 7 August 2026
Forwarded from @road_to_oscpPhoto

Secure Coding Cheatsheets Примеры уязвимых фрагментов кода и того как следует делать https://blog.devsecopsguides.com/secure-coding-cheatsheets

custom 53888308914579176206👾1

20 Mar 2024, 21:10 UTC≈2,220 views18 reactionsread 7 August 2026
Photo

Email Spoofing Тема не нова, но часто забываемая при пентесте веб-апликаций. Email Spoofing - атака на домены, которые не используют или используют криво настроенные SPF и DMARC записи, которая позволяет отправлять письма от лица этого самого домена. Используется при фишинге и спаме, т.к. у человека, который увидел знакомый домен больше доверия к письму. Два сервиса, которые позволяют проверить DMARC и SPF записи:

custom 5388830891457917620113🤡2💩1😈1

8 Mar 2024, 16:26 UTC≈1,830 views27 reactionsread 7 August 2026
Photo

С 8 Прекрасные девицы, поздравляю с восьмым марта. Желаю вам поменьше моразма по жизни, побольше любви и радости и продолжать осветлять туман жизни яркой улыбкой. Пускай колючие шипы красных роз ломают (ред-тим), а красивые и утонченные лепестки синей орхидеи защищают (блю-тим) наше с вами киберпространство. С праздником!

🫡97💩5🤡3💊2🍌1

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

“#Arm1tage” (@arm1tage), 1,574 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/arm1tage.

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.