Telegram RegisterThe public register of Telegram
Telegram profile photo for Proxy Bar

Channel

Proxy Bar

@proxy_bar

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

21,734subscribers

+628 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001524188931
TypeChannel
Username@proxy_bar
DescriptionExploits, Hacking and Leaks Чат группы - https://t.me/ Связь с администрацией и реклама: @NULL_vm Поддержать проект: BTC bc1q39tnnjlzac97pahc0cn5rrqddgncc6fjprwg9s
Created17 November 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live10 November 2026
Measurements held64
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/proxy_bar

Topic

Hacking & security — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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

21,10621,73421,4206 August 202610 November 2026
64 measurements spanning 96 days, net +628. 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 21,012–21,828 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)SubscribersChange
10 Nov 2026, 09:3521,734+5
8 Nov 2026, 22:0021,729+3
7 Nov 2026, 11:4021,726-1
6 Nov 2026, 12:2521,727+14
5 Nov 2026, 12:3921,713-5
4 Nov 2026, 10:5621,718+6
3 Nov 2026, 08:1621,712+10
2 Nov 2026, 06:4621,702+13
1 Nov 2026, 03:1421,689+22
31 Oct 2026, 01:1921,667+83
30 Oct 2026, 01:3721,584+100
29 Oct 2026, 03:3621,484-3
28 Oct 2026, 01:3921,487-7
27 Oct 2026, 03:0421,494-16
26 Oct 2026, 05:3621,510-17
25 Oct 2026, 05:1021,527-26
24 Oct 2026, 07:2721,553-2
23 Oct 2026, 06:0721,555+2
22 Oct 2026, 07:4921,553-41
20 Oct 2026, 22:1621,594first reading

Engagement

89 posts held, back to 22 July 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 85 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
39.2%
avg views ÷ 21,734 subscribers
Avg views / post
8,520
20 posts measured
Reaction rate
0.479%
reactions ÷ views · ER floor
Posts in window
20
of 89 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 10 November 2026
Posts held89 (22 July 2026 – 10 November 2026)
Views total170,470
Reactions total816
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 03:11 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
≈1,760
Videos
≈109
Links
≈1,790

Lifetime counters from Telegram’s own channel header, read 11 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
8m 17s
Average length
1m 11s

Measured directly from 7 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

2,736 reactions across 89 posts, in 3 distinct kinds. The most used accounts for 49.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1,35149.4%
🔥94434.5%
😱44116.1%

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

Measured over the 89 most recent posts we hold, published 22 July 2026 to 10 November 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: 1 of 20 posts held from the last 30 days (5.00%) 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).

10 Nov 2026, 10:13 UTC≈3,330 views30 reactionsread 11 November 2026
Photo

хороошо что я не в регманиии

🔥26👍2😱2

9 Nov 2026, 10:16 UTC≈4,140 views13 reactionsread 11 November 2026
Photo

В информационной безопасности ценятся не только те, кто умеет пользоваться инструментами, но и специалисты, которые понимают, как устроены программы изнутри. Реверс-инжиниринг позволяет анализировать вредоносное ПО, исследовать механизмы защиты и разбирать сложные инциденты на уровне машинного кода. Курс «Профессия Реверс-инженер» от Codeby Academy позволит перейти от работы с инструментами к глубокому пониманию ма…

😱7👍3🔥3

5 Nov 2026, 15:52 UTC≈7,210 views83 reactionsread 11 November 2026
Photo

sshole * who: alpine, openwrt, buildroot, yocto, and a lot of the docker images you've pulled Принимает вообще любой пароль от 256 символов , прикольный bug 😁

👍50😱26🔥7

31 Oct 2026, 22:41 UTC≈9,230 views34 reactionsread 11 November 2026
Photo

AnythingLLM * Занятно занятно. Дергаем одну учетку или 1 api key, можно читать все переписки и перенаправить все запросы к LLM на свой сервер. Конфиг LLM можно менять. Сидит себе такой бизнес $USERNAME, думает что чятится со своей LLM, а по факту с LLM атакера. * ANYLLMSCOPE - Single-User Auth Gate + P7 Data-Plane Redirect

👍19🔥14😱1

30 Oct 2026, 13:46 UTC≈9,510 views48 reactionsread 11 November 2026

Binance St0RY * Подозрительные лица: Lazarus - пока не доказано некоторый инженер из Binance - как первоначальный вектор атаки, через "заряженный" ноутbook Тенг Ричард - СЕО бананса, никак не заткнется, ну работа такая Чжао Чанпен - основатель бинанса, но сразу отморозился Эмитеты вроде tether/cirlce и тд - шараги которые блочили токены sesurity lab - ну все кто не спал * Стороны атаки ! атака не на криптографию, а …

👍33🔥11😱4

30 Oct 2026, 05:26 UTC≈6,620 views24 reactionsread 11 November 2026

CVE-2026-98432 | Linux Kernel * такой себе patch конечно 😕 iptables -I INPUT 2 -p tcp -m u32 --u32 '0>>22&0x3C=0x18:0x3C' -j DROP Ну за то идея хорошая, можно с NXDOMAIN поиграться или с TCP Header / TCP payload

👍16🔥5😱3

29 Oct 2026, 21:31 UTC≈12,400 views103 reactionsread 11 November 2026
Photo

Binance подломили на $2.5b ETH А все почему ? сплоеты, дыры ? Нет, просто идиоты))) Ключик утек на онлайн казино на Филиппинах ! 🏴‍☠️

🔥80😱23

29 Oct 2026, 00:31 UTC≈7,590 views34 reactionsread 11 November 2026
Photo

Linux core vuln Случайно раскрыли дыр в Zero Day Initiative, до патча, из-за ошибочной отправки информации не в тот список (lol) ZDI-CAN-33549 - уязвимость в модуле ksmbd c реализацией файлового сервера на базе протокола SMB ZDI-CAN-33774 - состояние гонки в модуле ядра ksmbd ZDI-CAN-33367 - уязвимость в сетевом стеке ядра ZDI-CAN-34068 - переполнение буфера в графическом драйвере VMWGFX ZDI-CAN-34076 - уязвимость в …

👍16🔥14😱4

28 Oct 2026, 19:26 UTC≈7,200 views24 reactionsread 11 November 2026
Photo

Pre-boot RCE in EDK II PXE driver * Специально сформированный сетевой пакет потенциально позволяет выполнить вредоносный код ещё до загрузки ОС, когда Secure Boot даже не успел включиться. * read

😱16👍4🔥4

28 Oct 2026, 19:13 UTC≈8,400 views87 reactionsread 11 November 2026
Photo

Просто праздник Ждем TXT2Shell

😱59👍17🔥11

25 Oct 2026, 13:43 UTC≈10,600 views90 reactionsread 11 November 2026
Photo

с днем рождения Джонни

👍65🔥25

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

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

“Proxy Bar” (@proxy_bar), 21,734 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/proxy_bar.

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.