Telegram RegisterThe public register of Telegram
Telegram profile photo for 黑客技术交流顾问

Channel

黑客技术交流顾问

@hkdiguo

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

6,206subscribers

+6,205 since we began measuring on 6 September 2026

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

Register entry

Telegram ID-1003798241733
TypeChannel
Username@hkdiguo
Created4 September 2026 — measured — dated from the channel’s first post
First recorded10 September 2026
Last confirmed live15 November 2026
Measurements held12
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/hkdiguo

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 3 October 2026 and assigned it the closest of 31 fixed categories, at 100% 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

16,2063,103.56 September 2026 — 1 subscribers9 September 2026 — 107 subscribers10 September 2026 — 107 subscribers17 September 2026 — 248 subscribers3 October 2026 — 512 subscribers13 October 2026 — 713 subscribers20 October 2026 — 856 subscribers28 October 2026 — 984 subscribers4 November 2026 — 1,065 subscribers6 November 2026 — 6,138 subscribers10 November 2026 — 6,156 subscribers15 November 2026 — 6,206 subscribers6 September 202615 November 2026
12 measurements spanning 70 days, net +6,205. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Nov 2026, 15:586,206+50
10 Nov 2026, 03:116,156+18
6 Nov 2026, 16:246,138+5,073
4 Nov 2026, 00:081,065+81
28 Oct 2026, 10:39984+128
20 Oct 2026, 12:59856+143
13 Oct 2026, 00:48713+201
3 Oct 2026, 10:16512+264
17 Sept 2026, 18:00248+141
10 Sept 2026, 02:22107no change
9 Sept 2026, 13:59107+106
6 Sept 2026, 12:171first reading

Engagement

10 posts held, back to 4 September 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 2 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.632%
avg views ÷ 6,206 subscribers
Avg views / post
39.2
5 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
5
of 10 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 4 November 2026
Posts held10 (4 September 2026 – 4 November 2026)
Views total196
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Nov 2026, 17:39 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.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 5 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).

4 Nov 2026, 09:59 UTC20 viewsread 6 November 2026
Photo

如果你突然采集不了,就查找bdata 里面的这个网址 然后替换为能正常登陆的网址,数据库中的web_system 表中的网址也需要修改,去年有采集不到数据 是因为皇冠修改了登陆字段 这里我已经做了修改 修改本地时间 不用修改为美东时区 比如现在是14:10 直接修改时间为 02:10 即可 这样就正常了 接单中,黑客业务,渗透 拿站 提权 拖库 ddos dns劫持 管理权限 改成绩 改单有需要联系: @dust515

4 Nov 2026, 09:44 UTC21 viewsread 6 November 2026
Photo

这个 cookie 引起了我的注意。它采用了 Flask 常见的三部分session=<payload>.<timestamp>.<signature>格式,但大约 1200 字节的大小对于一个 CSRF 令牌和一个返回 URL 来说似乎有点大。所以我对其进行了解码。 Flask 会话 cookie 是签名的,而不是加密的,因此任何持有 cookie 的人都可以直接获取其内容。开头的点表示有效载荷经过 zlib 压缩: import base64 import json import pickletools import zlib 该 cookie 包含一个序列化为 pickle 的有效载荷和 Google 的 OAuth 信息client_id,以及client_secret明文版本。(此处已隐去密钥;撰写本文时该密钥仍然有效。) 我尝试使用 Flask 客户端密钥SECRET_KEY,并且已颁发 cookie 上的签名与该…

31 Oct 2026, 09:43 UTC33 viewsread 6 November 2026
Photo

我们不想将有趣的十六进制转储与主机泄露混淆。证据设计区分了身份识别情况(数据包的原始头部长度保持不变)和活动情况(后续操作改变了数据包的解释)。它检查了最终传输的数据包在结构上是否有效,已知逻辑数据之外是否出现了非零字节,以及这些字节是否与发送方控制的保护数据不同。 测试中还采用了独立的应用程序层接收机制以及原始数据包观察。这两个信号有助于区分真正的主机端重写和传输与数据包构造或数据包捕获伪造的结果。 首次有界披露针对每个活跃案例复制了 32 字节。我们将内容视为敏感信息,因此无需保留无关的原始主机内存来证明越界行为。 接单中,黑客业务,渗透 拿站 提权 拖库 ddos dns劫持 管理权限 改成绩 改单有需要联系: @dust515

28 Oct 2026, 09:31 UTC53 viewsread 6 November 2026
Photo

2026年8月18日,Vercel宣布了一项挑战赛,邀请研究人员突破其Sandbox产品的隔离边界(奖金池总额)。就在几周前,OpenAI披露了一起重大的安全事件:运行在受限评估环境中的AI代理找到了绕过网络隔离的方法,破坏了内部基础设施,最终入侵了Hugging Face的系统。这些代理原本是不应该拥有互联网访问权限的。 但两者之间存在一个重要的区别。突破沙箱的网络限制是一回事,突破虚拟机本身并最终到达宿主机则是另一回事。Vercel的挑战明确邀请研究人员尝试这两种方法。我们更感兴趣的是后者。(尽管我们最终也发现了一些漏洞,这些漏洞也允许突破前者——关于这些发现,我们将在后续文章中详细介绍。) 问题很简单:一个不受信任的客户机在不利用 KVM 本身的情况下,究竟能对宿主机内核产生多大的影响?我们接受了挑战,投入研究基础设施,并在三天内发现了一个隐藏在 Linux 网络机制中的原语,它允许客户机控制的校验和元数据在内核验证IP…

24 Oct 2026, 12:02 UTC69 viewsread 6 November 2026
Photo

这种主要利用了crontab、ssh key、webshell这样的文件都有一定容错性,再加上crontab和ssh服务可以说是服务器的标准的服务,所以在以前,这种通过写入文件的getshell方式基本就可以说是很通杀了。 但随着现代的服务部署方式的不断发展,组件化成了不可逃避的大趋势,docker就是这股风潮下的产物之一,而在这种部署模式下,一个单一的容器中不会有除redis以外的任何服务存在,包括ssh和crontab,再加上权限的严格控制,只靠写文件就很难再getshell了,在这种情况下,我们就需要其他的利用手段了。 接单中,黑客业务,渗透 拿站 提权 拖库 ddos dns劫持 管理权限 改成绩 改单有需要联系: @dust515

9 Sept 2026, 10:23 UTC311 viewsread 6 November 2026
Photo

整个流程下来没什么问题,但是如果又来了一个 X 协议(X over HTTP),那么我们就得继续修改 SQL 注入模块以便支持这种 X 协议,但是扫描器中可不是只有 SQL 注入检测模块,还有其他同类模块,难道每加一个新协议我还得把所有检测模块都改一遍? 上面的递归 decode 主要是为了解码某种格式的数据里面还有另外一种格式的数据,虽然看起来这种场景比较少见,但是仔细想一下 multipart 带着 json,json 里的字符串是另外一个 json 字符串,是不是又觉得这种情况也并不少见。 如果不谈扫描质量,只关注整体项目设计以及产品中使用到的猥琐技巧,那么其中最让我眼前一亮的当属 AWVS,接下来我将详细介绍一下我从 AWVS 中学习到的 PoC 分类 接单中,黑客业务,渗透 拿站 提权 拖库 ddos dns劫持 管理权限 改成绩 改单有需要联系: @dust515

6 Sept 2026, 11:38 UTC260 viewsread 6 November 2026
Photo

赛题好难我好菜,其中还有一个是比赛结束复现出来的。这里写一下两道XSS的解题思路,还有一道是P神出的关于Scrapy爬虫框架的RCE,但是赛后听说是最新版本的Scrapy,等着看官方Wp的解法。 <script> var getUrlParam = function (name) { var reg = new RegExp("(^|&)" + name + "=([^&]*)(&|$)"); var r = unescape(window.location.search.substr(1)).match(reg); if (r != null) return r[2]; return null; } 重点在这个setElement函数,通过tag.substring(0, 1)创建一个dom事件,然后从cookie种取出attrs属性进行标签属性的赋值。接下来追一下cookie是怎么入库的 var tag = getUrlPa…

6 Sept 2026, 11:37 UTC182 viewsread 6 November 2026
Photo

因为学的是安全相关专业,在网上下载东西非常谨慎,就算通过了杀毒软件扫描,但是也怕有后门或者其他东西,毕竟我也可以静态过掉杀软。 很多软件没有官网,各种下载站的东西真的是让人不放心。所以在下载某些软件后,只要不影响功能,基本都会用sandboxie来运行软件。如果不行,则放到虚拟机里。 所以我对沙箱最初的概念就是:sandboxie,它是一个轻量级虚拟机,软件的操作都不会影响真正的系统,包括文件、注册表等等资源,可以放肆地想干嘛干嘛。 重定向,顾名思义,就是重新指定方向,也就是说沙箱能够做到让沙箱内软件操作的文件、注册表等路径重定向到其他位置(沙箱指定位置),这样软件本来想操作的资源就不会被访问或者操作,保证资源的安全性。 接单中,黑客业务,渗透 拿站 提权 拖库 ddos dns劫持 管理权限 改成绩 改单有需要联系: @dust515

6 Sept 2026, 11:36 UTC157 viewsread 6 November 2026
Photo

在Tokyo Western CTF2019之前,我对postscript处于基本0知识的状态。赛后,为了看懂官方给的poc,我大概花了一周的时间对着九百多页的官方文档学习了一下这门语言(它有关的学习资料太少了Orz),以及围绕它SAFER模式展开的攻防博弈。即使是现在,我对于postscript仍处于懵懂的愚昧状态。因此,如果下文中有任何不对的地方,希望大家理解并指出,感谢大佬们给与宝贵经验。 虽说postscript只是一种打印机语言,但是它在定义的时候就具备了比较强大的文件操作能力。关于postscript的文件操作符,在Adobe官方的文档中就有一页多的相关描述。 同时,ghostscript还支持在文件操作中采用pipe的方式来进程IO的操作,也就是我们可以利用file命令来实现任意的命令执行,当然这只在Unix系统中才生效。 核心的.locksafe方法主要做的事情是限制了userparams参数以及devic…

Showing the 10 most recent of 10 posts we hold for @hkdiguo. 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.

Mentions

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.

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

“黑客技术交流顾问” (@hkdiguo), 6,206 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/hkdiguo.

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.