Telegram RegisterThe public register of Telegram

Channel

hx0110

@hx0110

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

137subscribers

+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-1001612264390
TypeChannel
Username@hx0110
DescriptionWeb offensive security
CreatedBetween 1 December 2021 and 30 April 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/hx0110

Growth

1377 Aug 2026, 14:21 — 137 subscribers8 Aug 2026, 23:16 — 137 subscribers7 Aug 2026, 14:218 Aug 2026, 23:16
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 136–138 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 23:16137no change
7 Aug 2026, 14:21137first reading

Engagement

19 posts held, back to 29 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 19 posts for this entry, the most recent from 15 April 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
20
Videos
7
Links
64

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.

Video runtime
41s
Average length
14s

Measured directly from 3 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

213 reactions across 18 posts, in 17 distinct kinds. The most used accounts for 42.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
9142.7%
🔥5023.5%
❤‍🔥125.63%
👍125.63%
104.69%
🎉94.23%
🆒52.35%
41.88%
😍41.88%
🤯41.88%
🌭20.939%
🍓20.939%
👏20.939%
👨‍💻20.939%
😁20.939%
💘10.469%
🤝10.469%

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 213reactions 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 29 March 2025 to 15 April 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

15 Apr 2026, 16:29 UTC176 views14 reactionsread 8 August 2026

Всем привет! В последнее время дошли руки - досматриваю то, что не успел посмореть с black hat usa 2025. За что люблю блэкхэт - так это за глубину ресерчей. Так вот в Cross-Origin Web Attacks via HTTP/2 Server Push and Signed HTTP Exchange для меня показалось очень интересным наличие новго для меня типа origin. Как мы знаем, понятие origin - одно из осново пологающих в browser security. Важнейший механизм SOP, а в

🔥722👨‍💻2🤝1

3 Mar 2026, 13:47 UTC271 views20 reactionsread 8 August 2026
Photo

Удаленная отладка Go Всем привет! Буквально вчера мне подтвердили регистрацию еще одной CVE - на этот раз в Gitea. И как раз по этому поводу решил наконец-то начать серию статей про удаленную отладку. Тема очень полезная не только для разработчиков, но и для тех, кто занимается поиском уязвимостей. Я подготовил первую часть в формате блога: ❗️Remote Debugging for Vulnerability Research (Part 1. Go lang) В первой ч

9🔥7👍31

27 Jan 2026, 14:36 UTC793 views35 reactionsread 8 August 2026
Photo

Первая CVE! Всем привет! Давно я не писал ничего от себя. Ну, во-первых, всех с наступившим Новым годом, друзья! :) На самом деле большую часть свободного от работы времени в 2025 году я потратил на VulnResearch. В частности, цель была — начать находить уязвимости в опенсорсе. И цель, как мне кажется, была выполнена. На момент написания у меня лежит 7 уязвимостей (3 из которых — в продуктах с 44 000+ звёзд на GitHu

14🔥10🎉9👍1👏1

9 Dec 2025, 12:33 UTC300 views13 reactionsread 8 August 2026
Forwarded from @hackthishitPhoto

🎇 сводка по react2shell безумию events * китайские группировки сориентировались за 30 часов и начали раскидывать майнеры монеро и LD_PRELOAD руткиты * добрые (😈) хакеры пробивают таргеты и затем патчат их, устраивая дефейс с "сервер уязвим, фиксаните пж" * Vercel вышли на h1 с программой по обходам их WAF. платят 50к$ за обход react2shell. уже получили репортов на 750к$ facts * легче обновиться, чем защищаться waf

6🤯4🔥2👏1

8 Dec 2025, 12:02 UTC217 views8 reactionsread 8 August 2026

Fortinet vulnerability chain Исследователь уязвимостей Yaniv Nizry из Sonar,компании, занимающейся разработкой всем известного SAST-а SonarQube, продемонстрировал возможность компрометации множества узлов в сети при помощи EMS (Endpoint Management System). Цепочка действительно получилась очень красивой! 1. XSS для администратора. 2. Через неё — изменение адреса EMS для всех endpoint-ов на malicious EMS. 3. Эксплу

3🔥32

4 Dec 2025, 22:29 UTC191 views8 reactionsread 8 August 2026
Forwarded from @w3bpwnVideo

рабочий PoC CVE-2025-55182 подвез maple3142 https://gist.github.com/maple3142/48bc9393f45e068cf8c90ab865c0f5f3

3🔥32

24 Nov 2025, 10:14 UTC195 views15 reactionsread 8 August 2026
Forwarded from @hackthishitPhoto

file://localhost/etc/passwd что вернёт? Да, вернётся /etc/passwd. В RFC 8089, верный формат протокола описан как file://<host>/<path>, в то время как все шпоры на LFR при SSRF говорят лишь о file:///<path> Причём, в <host> возможно вписать домен. Система резолвнет его, и если тот указывает на 127.0.0.1, то вернётся содержимое файла. В противном случае получишь лишь отстук в DNS. питон пок from urllib.request imp

5🔥54👍1

5 Oct 2025, 11:43 UTC235 views9 reactionsread 8 August 2026
Forwarded from @pentestnotesPhoto

Подготовил для вас подробное руководство по тестированию на проникновение Outlook Web Access (OWA). 😈 ➡️ В статье я разобрал все основные атаки и уязвимости OWA. Собрал и структурировал самое полезное в одном месте. ➡️ Также материал идеально подойдет для тех, кто все еще путает между собой OWA, Outlook и MS Exchange :) Даже если вы раньше не сталкивались с почтовыми сервисами Microsoft, после прочтения смело може

71🔥1

15 Aug 2025, 19:15 UTC329 views6 reactionsread 8 August 2026

опять фортик :) https://labs.watchtowr.com/should-security-solutions-be-secure-maybe-were-all-wrong-fortinet-fortisiem-pre-auth-command-injection-cve-2025-25256/ #vuln

3😁2🔥1

12 Jul 2025, 11:03 UTC362 views9 reactionsread 8 August 2026

WatchTowr порадовали очередной классной цепочкой. Она достаточно простая, но, на мой взгляд, весьма красивая. Причём для получения удалённого исполнения была использована техника, о которой я упоминал выше — site-specific configuration hooks в Python. В общем, рекомендую к прочтению! https://labs.watchtowr.com/pre-auth-sql-injection-to-rce-fortinet-fortiweb-fabric-connector-cve-2025-25257/ #web #chain #vuln

4👍2🔥2💘1

28 May 2025, 18:03 UTC611 views13 reactionsread 8 August 2026

Offensive Con Конференция, записи с которой, если честно, я очень ждал!) https://www.youtube.com/watch?v=kF31SYIVob8&list=PLYvhPWR_XYJk0p40BrX7K2z-_j_tJmvhc&ab_channel=OffensiveCon #offensive #conf

6❤‍🔥4🔥2😍1

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

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

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

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.