Channel
@HackerCCTV
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
14,546subscribers
-43 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002434340272 |
|---|---|
| Type | Channel |
| Username | @HackerCCTV |
| Description | 频道主： @KHCHADANG 双向机器人： @SHANGGANSHEN_bot 我的接口频道： https://t.me/BYJIEKOSHEN 我的数据频道： https://t.me/SGSSHUJUKU 我的技术频道： https://t.me/HackerCCTV 我的倾诉频道： https://t.me/SGSYYDSNB 我的倾诉群聊： https://t.me/NNSGSYYDS 记住我的名字就好 我是个极度厌世的人 |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/HackerCCTV |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 14:58 | 14,546 | -6 |
| 12 Aug 2026, 10:59 | 14,552 | -11 |
| 11 Aug 2026, 07:51 | 14,563 | -5 |
| 10 Aug 2026, 07:41 | 14,568 | -5 |
| 9 Aug 2026, 09:52 | 14,573 | -8 |
| 8 Aug 2026, 10:58 | 14,581 | -8 |
| 7 Aug 2026, 14:45 | 14,589 | first reading |
12 posts held, back to 7 December 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 18 pagesof 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 12 posts for this entry, the most recent from 31 March 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 14 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.
147 reactions across 10 posts, in 9 distinct kinds. The most used accounts for 72.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 107 | 72.8% | |
| 🤯 | 16 | 10.9% | |
| 😍 | 7 | 4.76% | |
| 🤩 | 6 | 4.08% | |
| 🤨 | 5 | 3.40% | |
| 👌 | 3 | 2.04% | |
| 👏 | 1 | 0.68% | |
| 🙏 | 1 | 0.68% | |
| 🤔 | 1 | 0.68% |
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 12 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 147reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 7 December 2025 to 31 March 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.
今天是你离开的第一天，我回想了很多关于我们之间的故事。我认为我是一个极其冷血的动物，对于你是否自杀成功与否，我并没有对你的回归抱太大希望。我认为你对这个世界失望透顶，自杀对于你来说甚至是一种享受。当我知道你再也不会回来后，我的大脑告诉我我应该哭泣，去为你难过，但是我并没有这样做，我只是为你的离开感到了遗憾和惋惜。 晚安，伤肝肾
❤23👌3🙏1
Signed 烨筱（影子）
东北大学 大连理工大学 安徽大学 同理加密内容 在获取登录或其他填写获取到的网络请求 （login）中rsa其中就是包含有名文 比如: asdfgh 123456 rsa: asdfgh123456LT-13945240-9LF60zXoWKigsdvdrDDoK6Dtuf3R3c-tpass lt: LT-13945240-9LF60zXoWKigsdvdrDDoK6Dtuf3R3c-tpass 但是内部是有处理的 前端的JOUERY的框架有 $("#rsa").val(u+p+lt); 这样的内容 通过快捷搜索也可以看到 enc 内容 u : strEnc(u , '1' , '2' , '3') , p : strEnc(p , '1' , '2' , '3') 经过跳转就可以看到 var leng = data.length; var encData = ""; var firstKeyBt,secondKe…
❤13🤩5
Signed 伤肝肾（海上钢琴师）
湖北政务 解密 #登录所用的公钥 login_publicKey = 047a877a8fb4a8174f6d85659f06c5d266d5ca18f417cb858583fd008616b36c3bb5a8d10a954eb38ea62a0026c008302614ae968903eb7a3d1514602fd6b64cb5 #登录所用的私钥 #login_privateKey = b3abbd79d78692ef4b2fd27989c9c33aa5e7d6b43fa8c4b873985e148910d136 #前端接口加解密公钥和私钥 #encrypt_public_key=0460ff66ae5bbcf43ceab417632ed56400c730126b2f59da55f87f34c674bc728224d51620c67567b10bd7391a3f0698fe6d1eaa73f81168ef7a95836bdf0…
❤17👏1
Signed 伤肝肾（海上钢琴师）
小米所谓的超级小爱再每次启动时都会向https://i.xiaomixiaoai.com/api/suggest/dispatch/oauth/proxy POST巨额包含用户隐私信息的内容，高危的包括但不限于： · 设备ID（设备唯一识别码，可用于长期追踪） · 用户ID（用户账户识别码，可关联到个人账号） · 应用包名和版本（显示正在使用的具体应用） · 设备型号（具体硬件型号信息） 其他的： · Android系统版本（12） · MIUI系统版本（14） · 操作系统具体版本（22.10.26） · 小米AI服务版本信息 · 20项系统设置状态（蓝牙、WiFi、位置服务等开关状态） · 隐私设置（个性化推荐开关） · 当前运行的应用活动页面 · 第三方应用查询信息（本次为空）
❤15😍6🤨5🤯3🤩1
Signed 伤肝肾（海上钢琴师）
内蒙古 名下证 不动产 身份证 结婚证 等等... 蒙古个人政务上传地址 来自个人证件 https://zwfw.nmg.gov.cn/elec/namelist?name= 空查询如: 件办理\"},{\"defineAuthorityName\":\"中华人民共和国公安部\",\"certificateHolderCategory\":\"1\",\"subjectId\":\"8FBEB09982DCF90FE050817B0CFE27AB\",\"certificateTypeName\":\"户口迁移证\",\"validityRange\":\"长期 选择好 电子证照 我们去 https://zwfw.nmg.gov.cn/personal_center/getPersonCard?curr=1&pageSize=10®ionCode=&keyword=&_=1766256805566 ==========…
❤3🤔1
Signed 伤肝肾（海上钢琴师）
目标链接：http://eflybird.com/products_list.php?nid=19 技术栈：PHP 5.2.17, Apache,MySQL >= 5.0.12 在对目标进行信息收集中，发现 http://eflybird.com/products_list.php?nid=19 这个URL存在注入风险，毕竟依赖后端嘛wwww sqlmap一扫果然有货（依旧御三家，我是不是不应该再玩sql注入了？换一个别的玩玩？）一个一个布尔盲注、一个联合注入，因为联合查询的存在，基本可以判断无WAF，直接开始脱库（本次只脱了一部分） 成功获取数据库，叫bdm252107493_db 其中的user十分肥美啊！（篇幅限制原因这里不展示，自行查看压缩包） 密码还是MD5加密，暴力破解燃尽了，rockyou没出，许愿有人为我破解 总结：很典的sql注入，不过多解释了。对了我就是个渗透兴趣爱好者，我玩玩这种小站就好~ 作者： @Yuh…
❤7
Signed 伤肝肾（海上钢琴师）
一名Java 后端开发工程师，同时也是电信诈骗受害者，披露了一起涉及 “苹果 + 支付宝免密支付授权” 的严重安全问题。 受害者在完全不知情的情况下，仅一次 0.1 元操作，就被连续盗刷 999 元两笔。 @Yuhui_ddos 👏👏👏
🤯13❤3
Signed 伤肝肾（海上钢琴师）
jhyjczx.com 此站脱库数据
Signed 伤肝肾（海上钢琴师）
今日渗透分享：北京京瀚禹电子工程技术有限公司SQL注入 目标：北京京瀚禹电子工程技术有限公司 ( jhyjczx.com ) 技术栈：PHP 5.2.17, Apache, MySQL 5.0.12 在对目标进行信息收集中，发现 about.php?cid=1&id=2 这个URL存在注入风险。 直接上sqlmap，扫描结果非常给力： 一个时间盲注、一个布尔盲注、一个联合注入，UNION查询的存在，基本可以判断无WAF，直接开始脱库。 数据获取： 成功获取数据库 bdm10851955_db，其中 admin 表引起了我们的注意： Database: bdm10851955_db Table: admin [1 entry] +--------------+----------------------------------+ | aname | apass |…
❤4
Signed 伤肝肾（海上钢琴师）
今日分享：森玛克精工科技（江苏）有限公司 链接： http://www.semirke.com/about.php?id=1 等级：SQL注入 -> Getshell 首先在对目标进行信息收集时，发现其官网一处 about.php 参数存在sql注入漏洞。通过sqlmap进行探测，确认了时间盲注和联合查询注入的存在，并成功获取数据库 adm82571079_db 的权限。 深入数据库后发现，其中存放着公司最核心的业务数据。这里共计拿到该公司的一些技术数据，包括各类减速机、电机的核心设计图纸、技术参数、物料清单（BOM表）。此外，还获取了国内客户的详细联系方式、历年销售合同及定价策略，以及国内供应商名单。 接着，为进一步窃取服务器上的文件资料，我们利用SQL注入的 INTO OUTFILE 功能，在读取网站配置文件获取到物理路径后，成功写入webshell，控制了服务器 这里成功进入内网了，后续在进行内部资料寻找，把中心放在研…
❤5
Signed 伤肝肾（海上钢琴师）
留言内涵的不是蛤蟆，而是其他人😪，不要乱套
Signed 伤肝肾（海上钢琴师）
今日分享：黑龙江省公安厅 等级：高危 这里我们选择个人登录，只有登陆后才能更好的去测试 进入后发现系统维护中，这里我们使用 F12，查看源码，把系统维护中的遮罩删除 删除后我们发现可以正常使用了，这里我们选择进入进度查询 （一般来说我们挖掘后台洞都会选择 查询 预约 申报 个人信息这些功能点） 这里我们查看Js源码 发现存在一个/api/hljga-serv/projectApplyDelivery 这里我们抓包进行访问 成功拿到获取敏感数据上千条 @Yuhui_ddos
❤17😍1
Signed 伤肝肾（海上钢琴师）
Showing the 12 most recent of 12 posts we hold for @HackerCCTV. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“BYSGS会所---网站漏洞公布” (@HackerCCTV), 14,546 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/HackerCCTV.
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.