Channel
@buhecha
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,392subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001986959144 |
|---|---|
| Type | Channel |
| Username | @buhecha |
| Created | Between 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/buhecha |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 09:26 | 1,392 | -2 |
| 11 Aug 2026, 09:24 | 1,394 | +1 |
| 7 Aug 2026, 10:02 | 1,393 | no change |
| 7 Aug 2026, 09:59 | 1,393 | first reading |
15 posts held, back to 29 April 2025 — the 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 15 posts for this entry, the most recent from 22 May 2026. An engagement rate over an empty window would be a number about nothing.
113 reactions across 11 posts, in 13 distinct kinds. The most used accounts for 19.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 22 | 19.5% | |
| 👍 | 18 | 15.9% | |
| 🫡 | 17 | 15.0% | |
| 💩 | 13 | 11.5% | |
| 🤯 | 11 | 9.73% | |
| 😈 | 10 | 8.85% | |
| 🤡 | 9 | 7.96% | |
| 🍾 | 4 | 3.54% | |
| 🖕 | 3 | 2.65% | |
| 😭 | 3 | 2.65% | |
| ❤🔥 | 1 | 0.885% | |
| 👎 | 1 | 0.885% | |
| 🥰 | 1 | 0.885% |
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 13 of the 15 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 113reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 29 April 2025 to 22 May 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.
V2Board全系列漏洞可修改任意用户账号密码，已有大AFF账号被盗号提现。 复现URL：api/v1/passport/auth/forget Payload： { "email":"任意一个已注册用户", "password": "密码", "email_code": false } 修复： app/Http/Requests/Passport/AuthForget.php 将'email_code' => 'required' 修改为'email_code' => 'required|string|digits:6' 原理： 如果攻击者发送的请求参数中 email_code 是一个空字符串或者导致转换后为空的值，且此时缓存刚好失效（返回 null），那么： "" !== "" 的结果为 false，从而判定验证通过。
Posted without readable text
Telegram 伪装成用户名1次点击绕过代理暴露真实IP 问题的核心在于Telegram的自动代理验证机制。当用户遇到一个伪装的代理链接时 （通常隐藏在用户名后，例如 @test 实际背后链接是 t.me/proxy?server=attacker-controlled ） ，应用程序在添加代理服务器之前会先对其进行”ping”操作测试连通性。至关重要的是，这个”ping”请求会绕过所有用户配置的代理，直接从受害者的设备路由出去，从而暴露其真实IP。此过程不需要密钥，类似于Windows上的NTLM哈希泄露——认证尝试本身就会暴露客户端信息。 攻击可能造成的影响： 1.自动代理测试：Telegram向攻击者的服务器发送连通性探测请求。 2.代理被绕过：该请求忽略SOCKS5、MTProto或VPN设置，使用设备的原生网络栈。 3.IP被记录：攻击者的服务器捕获来源IP、地理位置和元数据。 防护措施： (1).行为层面不…
❤6👍2
继汇旺后新一波大规模抓捕行动已经展开 一周前多家国际担保及黑产上下游受到牵连影响，已证实多个核心人员受到控制，牵连上下游开始大面积陆续跑路。
🥰1
Ios 26.1 目前国内已可提权用于取证 奇安信的盘古团队实现了ios 26.1 的提权可用于Telegram等应用的数据提取（支持范围从 iOS 17.0 - 26.1）。 为了数据安全，建议更新ios到最新版系统。
💩13😈4🖕3😭3
Gitee、Gitcode已开始针对机场行业针对性封号、封控。 目前已有多家机场受影响。
两高《关于常见犯罪的量刑指导意见(二)》(试行) (一)非法经营罪 1.构成非法经营罪的，根据下列情形在相应的幅度内确定量刑起点：(1)犯罪情节严重的，在二年以下有期徒刑、拘役幅度内确定量刑起点。(2)情节特别严重的，在五年至六年有期徒刑幅度内确定量刑起点。2.在量刑起点的基础上，根据非法经营数额、违法所得数额等其他影响犯罪构成的犯罪事实增加刑罚量，确定基准刑。3.构成非法经营罪的，根据非法经营数额、违法所得数额等犯罪情节，综合考虑被告人缴纳罚金的能力，决定罚金数额。4.构成非法经营罪的，综合考虑非法经营数额、违法所得数额、退缴赃款等犯罪事实、量刑情节，以及被告人的主观恶性、人身危险性、认罪悔罪表现等因素，决定缓刑的适用。 附则：第二百二十五条【非法经营罪】违反国家规定，有下列非法经营行为之一，扰乱市场秩序，情节严重的，处五年以下有期徒刑或者拘役，并处或者单处违法所得一倍以上五倍以下罚金；情节特别严重的，处五年以上有期徒刑，…
❤3
方滨兴投资的积至公司超过 500 GB 的源代码、工作日志和内部通信记录被泄露 泄漏资料显示该团队于2024年有对VPN客户端进行API及特征分析及阻断 有网友称文件中大量无效文件填充，该报告大概率为伪造抹黑，请理性看待。 下载链接 BitTorrent: https://enlacehacktivista.org/geedge.torrent HTTPS 直接下载: https://files.enlacehacktivista.org/geedge/ 文件使用方法：https://github.com/net4people/bbs/issues/519#issuecomment-3286329872 来源：积至公司与MESA实验室：防火长城史上最大规模文件外泄分析 其他有关报道：国外机构整理的资料显示方滨兴投资的积至(海南)信息技术有限公司参与福建江苏等地的省墙建设
👍12❤4
大范围通报重启 2025.09.12 18:00～19:00 (GMT+8) 目前已知信息： 1.订阅自毁机场 有被通报 2.全封端机场 有被通报 3.全部重置过订阅链接机场 有被通报 4.之前没被通报过的机场 有被通报 怀疑方向： 1.人工采集 2.协议特征
🤯11😈3❤2
注意：从该文件名以及文件描述显示，该组织及文件有明显的反华倾向，请理性阅读。
🤡9🍾4👍4👎1
国外机构整理的资料显示方滨兴投资的积至(海南)信息技术有限公司参与福建江苏等地的省墙建设 （注意：从该文件名以及文件描述显示，该组织及文件有明显的反华倾向，请理性阅读。） 该报告显示2022年积至公司开始在福建开始省级防火墙试点，在厦门、泉州、福州、漳州、宁德多地机房数据中心安装硬件。 出于反诈目的于2023年2月开始在江苏南京开始投入测试，并于2024年3月正式运行。 相关资料：（以下资料为灰色天空风向标频道整理搜集，转载请保留灰色天空风向标频道来源） 1.积至(海南)信息技术有限公司官网 2.有关报道 2.1.互联网服务供应商否认使用中国技术监控用户 2.2.澄迈新增1家院士工作站-新华网 2.3.积至（海南）信息技术申请基于多阶段属性指纹的加密流量分类方法专利，减少加密流量分类的观察等待时间—新浪财经 2.4.积至信息技术申请基于多模态AI语言模型的智能编程辅助方法及系统专利，可显著提升编程效率与代码…
❤5❤🔥1
Photo, posted without a caption
🫡17😈3
Showing the 12 most recent of 15 posts we hold for @buhecha. 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 — 662,325 of 1,350,102entries 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.
Named by 1 registered channel — 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“灰色天空风向标” (@buhecha), 1,392 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/buhecha.
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.