24 Dec 2025, 11:13 UTC270 viewsread 8 August 2026
Photo
超搜朋友圈🎈@CSZWBOT (https://t.me/CSZWPYQ) 👇👇👇点击下方按钮，进行搜索
Channel
黑客大队 渗透劫持 木马改单透视
@xiaoqiang562
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
562subscribers
-3 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 | -1002164026515 |
|---|---|
| Type | Channel |
| Username | @xiaoqiang562 |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/xiaoqiang562 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 15:46 | 562 | -3 |
| 8 Aug 2026, 03:33 | 565 | no change |
| 7 Aug 2026, 17:26 | 565 | first reading |
Engagement
13 posts held, back to 16 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 13 posts for this entry, the most recent from 24 December 2025. An engagement rate over an empty window would be a number about nothing.
Reaction mix
128 reactions across 10 posts, in 7 distinct kinds. The most used accounts for 18.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 23 | 18.0% | |
| 🥰 | 23 | 18.0% | |
| ❤ | 20 | 15.6% | |
| 👍 | 17 | 13.3% | |
| 🎉 | 16 | 12.5% | |
| 👏 | 15 | 11.7% | |
| 🤩 | 14 | 10.9% |
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 10 of the 13 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 128reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 16 April 2025 to 24 December 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
18 Dec 2025, 01:49 UTC275 viewsread 8 August 2026
Photo
— 让搜索更高效 · 让信息更有价值 — 🔍帮你找到有趣的群组、频道、视频、音乐、电影、新闻 📢: @CJYQNEWS | 🤖: @CJYQ 👇点击下方按钮，进行搜索👇
15 Dec 2025, 01:59 UTC220 viewsread 8 August 2026
Photo
— 让搜索更高效 · 让信息更有价值 — 🔍帮你找到有趣的群组、频道、视频、音乐、电影、新闻 📢: @CJYQNEWS | 🤖: @CJYQ 👇点击下方按钮，进行搜索👇
3 May 2025, 16:07 UTC≈2,880 views14 reactionsread 8 August 2026
Photo
程序员对某些常用函数的错误使用 这些函数有iconv()、copy()等,如下面的这段代码(摘自SiteStar) 我们再来看看这段代码, img_create()函数的逻辑非常严密，安全检查做的很到位。然而问题出在了_savelinkimg()函数，即在保存文件的前面程序员错误的使用了iconv()函数,并且文件名经过了此函数,为什么是错用了呢?因为啊 iconv函数在转码过程中，可能存在字符串截断的问题： 在iconv转码的过程中,utf->gb2312(其他部分编码之间转换同样存在这个问题)会导致字符串被截断，如：$filename="shell.php(hex).jpg";(hex为0x80-0x99)，经过iconv转码后会变成$filename="shell.php "; 所以，经过iconv 后$struct_file['name'])为shell.php，于是我们利用这个逻辑缺陷可以成功的上传shell.p…
❤5👏3👍2🥰2🎉1🤩1
3 May 2025, 16:04 UTC464 views12 reactionsread 8 August 2026
Photo
简单粗暴的文件上传漏洞 代码审计 基础 关于PHP中$_FILES数组的使用方法 $_FILES\[‘file’][‘name’] 客户端文件名称 $_FILES\[‘file’][‘type’] 文件的MIME类型 $_FILES\[‘file’][‘size’] 文件大小 单位字节 $_FILES\[‘file’][‘tmp_name’] 文件被上传后再服务器端临时文件名，可以在php.ini中指定 需要注意的是在文件上传结束后，默认的被储存在临时文件夹中，这时必须把他从临时目录中删除或移动到其他地方，否则，脚本运行完毕后，自动删除临时文件，可以使用copy或者*move_uploaded_file两个函数 程序员对某些常用函数的错误认识 这些函数有:empty()、isset()、strpos()、rename()等，如上面的代码 我们来看上面的这段代码,要想文件成功的上传, if(empty($msg)) …
🤩3🥰3🎉2👍2❤1🔥1
30 Apr 2025, 10:36 UTC≈2,530 views13 reactionsread 8 August 2026
Photo
早上吃了兩個HITCON送的鳳梨酥作爲早飯(感謝～昨天下午送的，因爲準備倉促，沒有回禮，很監介。。。)一些隊友今日回去，我去San Jose International Airport，riatre和marche147乘坐Delta Air，在Seattle轉機回北京。我因爲和iromise又檢查了下套房衆人落下的東西，離開得稍晚了，就被拋下了😭又只好獨自打車到機場，好在在機場碰頭了，還遇到了A0E (0ops)的谭凌霄。大部隊乘坐Korean Air，還有幾個報了旅遊團在Planet Hollywood住兩天再回去。Misty和HITCON乘坐同一個Korean Air航班。我第一次在SJC出發離開，發現有個ride-sharing app的通道。 主辦方的過失很多： 網絡環境配置。Day2開賽時間拖延了兩個小時有點長，以前legitbs從沒有拖到過兩小時。 不慎暴露的Admin interface。 patch上傳機制。…
🔥5👏3🥰3👍1🤩1
28 Apr 2025, 10:36 UTC243 views12 reactionsread 8 August 2026
Photo
用選項1下載執行檔後發現這個程序把命令行參數、.text .fini和.rodata大部分計算MD5後顯示爲randomart。如果篡改程序，改變輸出的字串Order through Control，就會破壞randomart。有兩種思路： 修改.text，設法修復hash 修改__printf_chk的PLT項，跳轉到.eh_frame。我們選擇了這種，hook這個函數後用rsi-8!=rsp、format[0] != 'O'等方式檢測是第幾個printf調用，發現要輸出Order through Control則替換字串。riatre嫺熟地patch了交了一個版本上去，排到第五，之後又優化了下。我發現了r2 waf的幾處問題。
👍3🎉2🤩2🥰2❤1👏1🔥1
26 Apr 2025, 10:36 UTC219 views13 reactionsread 8 August 2026
Photo
賽後slipper說： 不利用漏洞，燒錢開服務器用4096核可以兌換到flag 有個type confusion漏洞 有個-Wsign-compare漏洞，可以直接拿flag 用scanf讀取nonce，可以算一次提交很多遍 大約有半小時套房內極路由和有線網斷開了。 裏面用的node_modules/express-validator和實際1.0.0版本不同，多了wasm模塊node_modules/express-validator/express-validator.wasm，index.js也有很多集成wasm到js的代碼。 routes/data.js(/report)可以寫入public/suspects.txt routes/suspects.js(/suspects)會讀取public/suspects.txt 我們把三個web手喚醒。大家使用wabt等工具分析。Day 2結束後嘗試了各種web applicat…
🤩3❤2🎉2🔥2🥰2👍1👏1
24 Apr 2025, 10:34 UTC248 views14 reactionsread 8 August 2026
Photo
賽後Fish Wang告訴我應該繼續逆向，修復程序的功能，利用隱藏指令簡化遊戲，不需要大力投入到完整的solver上。 BrieflyX根據主辦方提供的game_states.json簡單處理了下做了個內網portal。我用display: grid;稍微改了改。
🔥4❤3🎉2👍2🥰2🤩1
22 Apr 2025, 10:33 UTC≈2,420 views13 reactionsread 8 August 2026
Photo
不允許往其他隊伍機器接入網線。如果發現這類不正當行爲，可能會被長期ban(>1年)不能参加比赛 互聯網和比賽內網使用同一根網線，但今年主辦方沒有使用VLAN隔離。riatre和我9:00到達現場，稍晚6人和我們匯合 入場後發現網絡不通。因爲網絡問題主辦方推遲到了11:00。最早開放的題目是King of the Hill類型的reverse。每輪每支隊伍有12枚coins，投放一枚coin可以玩一次，是個x86-32 x86-64的disassemble選擇題遊戲，猜指令、指令地址等。有隊伍先玩到了90分，我通過r2/pwntools disassemble可以玩到100多分，但不久就有隊伍研製出自動化可以弄到600多分。服務端程序明顯有bug，有時會有重複選項，有時會有錯誤選項。
🎉4👏3🔥2🥰2❤1👍1
20 Apr 2025, 10:32 UTC918 views12 reactionsread 8 August 2026
Photo
主辦方因爲網絡配置原因延遲了1個小時開賽。投影的大屏幕上有比賽規則鏈接http://oooverflow.io/obey。除了DEFCON CTF決賽傳統的Attack and Defense類型題目外還設有King of the Hill (KoH)類型題目。 Attack and Defense：故意隱藏漏洞的服務，隊伍需要找出漏洞、修補服務(抵擋其他隊伍攻擊則獲得防禦分)、攻擊其他隊伍的服務獲得flag、提交flag得分(攻擊分) King of the Hill：根據解的質量得分。第一名每回合獲得10分，第二到五名分別獲得6、3、2、1分。我們推測這可能會考寫最短shellcode、達成最低延遲等。 比賽每5分鐘爲一輪，每輪每個服務，攻擊成功一個隊伍可以獲得1攻擊分，沒有隊伍攻擊成我方服務獲得1防禦分。總分=40%攻擊分+40%防禦分+20% KoH分。我們推測攻擊分最高隊伍獲得400分，其他隊伍按照比例得分；防禦分、…
🔥4👍2🥰2❤1🎉1👏1🤩1
18 Apr 2025, 10:32 UTC161 views12 reactionsread 8 August 2026
Photo
DEFCON 26 CTF參賽記 今年作爲Tea Deliverers一員參加DEFCON 26 CTF。Redbud、Nu1L、ROIS、長亭科技幾個員工組成Tea Deliverers，在DEFCON 26 CTF Quals中晉級Finals。DEFCON 21~25 CTF的主辦方Legitimate Business Syndicate退休之後原來Shellphish的一些人組成oooverflow接手了。我們推測賽制可能會發生較大變化(往年使用一種零和賽制，被很多比賽的決賽沿用) 其中，A*0*E(浙江大學AAA+上海交大0ops+騰訊eee+復旦大學六星)、r3kapig(Eur3kA+FlappyPig)、Tea Deliverers是來自中國大陸的隊伍。BFS(交通大學BambooFox、臺灣大學Balsn、中央大學DoubleSigma以及中科院Kerkeryuan CTF)、HITCON是來自臺灣的隊伍。…
👏3❤2🎉2👍2🥰2🔥1
Showing the 12 most recent of 13 posts we hold for @xiaoqiang562. 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
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“黑客大队 渗透劫持 木马改单透视” (@xiaoqiang562), 562 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/xiaoqiang562.
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.