Telegram RegisterThe public register of Telegram

Channel

𝙏𝙂 · 𝙎𝙀𝘾

@tgsec

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

3,090subscribers

+286 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1004435650371
TypeChannel
Username@tgsec
CreatedBetween 1 June 2026 and 23 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/tgsec

Growth

2,8043,0902,9477 August 2026 — 2,804 subscribers8 August 2026 — 2,849 subscribers11 August 2026 — 2,967 subscribers14 August 2026 — 3,090 subscribers7 August 202614 August 2026
4 measurements spanning 6 days, net +286. 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 2,761–3,133 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 07:083,090+123
11 Aug 2026, 03:062,967+118
8 Aug 2026, 08:062,849+45
7 Aug 2026, 22:452,804first reading

Engagement

16 posts held, back to 23 July 2026the 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.

ERR · 30 days
81.8%
avg views ÷ 3,090 subscribers
Avg views / post
2,530
16 posts measured
Reaction rate
0.27%
reactions ÷ views · ER floor
Posts in window
16
of 16 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 August 2026
Posts held16 (23 July 20264 August 2026)
Views total40,420
Reactions total109
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 22:45 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.

Reaction mix

109 reactions across 16 posts, in 11 distinct kinds. The most used accounts for 60.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
6660.6%
👍2321.1%
👎43.67%
😡32.75%
😢32.75%
🤬32.75%
💩21.83%
🤮21.83%
10.917%
🎄10.917%
🔥10.917%

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

Measured over the 16 most recent posts we hold, published 23 July 2026 to 4 August 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

4 Aug 2026, 05:17 UTC≈1,650 views7 reactionsread 7 August 2026

🏳️ @TGSEC - 《AI模型决定的一些事,以及各种模型体验感》 前言: 常在社区群的成员都知道小国常用的Claude,其余的不在这里多叙述,因为没体验过… 正文: 🤖Claude模型分为: (以小国使用频率为基准) Fable5,Sonnet5/4.6,Opus4.7(4.6,4.8、5)。 有些小伙伴盲目追求高级别模型,高智能,高水平,但是前置条件都是由消费水平而定,我们追求的东西都是性价比,以及漏洞输出率,准确率,是否为资金类型/高危/掌管服务器/后台等。 😀其中以上三种主流使用模型以及版本,在我这里的感受如下: Opus5:性价比和水准对标Fable5、Sonnet5,价格差不多,但是Opus5的限制会比上述的模型要低。 Opus4.6、4.7:中流砥柱的水平,以及对漏洞的敏感度,测试成果很不错。 Sonnet5、4.6:属于Claude中的“流氓”使用正确方法如果有RCE也会执行,但是以上的未必能执行

6👍1

Signed 小国

3 Aug 2026, 03:19 UTC≈2,480 views13 reactionsread 7 August 2026

😀TeleGram赛博人物志: @kooyv 方阳,曾用名:酷维。 😀战绩突出: 2-4月: 新币漏洞一战成名!获利金额未知,应与其和解。 4-5月: 永发娱乐,KK电子模版全系列成功拿取Webshell,获得全部权限,获利3-5万U,其余被冻结,封禁账户。 6-7月: @Youbo 娱乐被打穿,方阳索要技术修复费用,富贵集团开价1888美金,索性曝光。 (后续富贵集团悬赏50万美金方阳信息) OK PAY商户漏洞一战千万!获利300万U!冻结45万U YYPAY商户漏洞获利45万U 7-8月: 富贵集团旗下: @JUFU @FGYL 成功突破,其中巨富娱乐获利9万U,冻结6万美金,富贵娱乐无获利冻结10万美金+

11👎2

Signed 小国

3 Aug 2026, 02:23 UTC≈2,410 views3 reactionsread 7 August 2026
Photo

🏳️ @TGSEC 《富贵娱乐 @FGYL 再次被突破》 于今日9点左右,Hack方阳开始在其群组内放出消息…其中富贵集团主产品 (富贵娱乐)也被突破余额,可惜富贵集团应急响应迅速,方阳此次未曾获利。 📷其中富贵集团旗下: @Youbo @Jufu @FGYl 均以被方阳渗透…那么下一个会是谁?

👍21

Signed 小国

2 Aug 2026, 00:44 UTC≈1,540 views7 reactionsread 7 August 2026

🏳️ @TGSEC - 《关于能不能学会AI审计的那些事》 其实可以给大家分几个层面讲一下。 一, 1️⃣,代码基础: 理解代码,但是并不代表你需要会,比如说让你简单写一个机器人,你首先需要知道用什么语言写,用什么条件来搭建。 2️⃣,英语基础: 说来惭愧,我也不会很多,只认识Ctrl,C,V,Yes,No。基本上感觉够用了。 3️⃣,术语基础: 调用AI去做审计你首先需要知道漏洞分哪些,有哪种,比如常规漏洞,逻辑类型漏洞,你理解触发逻辑流程就好了,使用Skill,或者是自己构思一个自动化流程让AI去跑。 二, 1️⃣,感受漏洞的存在: 比如打开一个目标,你很清楚的就能看出来,这个目标是不是AI编写,是不是老框架老模板编写,那么AI可能出现逻辑性漏洞,反之老模板就可能存在一些CVE,或者是一些常规性的漏洞,上述说的三个基础,你都可以用经验去弥补不足,打的多了,失败/成功的多了,你自然会理解。 ——TGSEC分享

3👍3😡1

Signed 小国

1 Aug 2026, 12:10 UTC≈1,560 views2 reactionsread 7 August 2026
Photo

🏳️ @TGSEC 渗透晚报 😀今日最新消息,新宝娱乐旗下人人包网的模板出现数据泄露,具体手法漏洞端点,TGSEC已经掌握,其中泄漏3W用户数据以及若干数据,据“某不愿意透露姓名的Hack”透露细节,还在持续深入研究此漏洞问题。 🫥8/2日最新消息,新宝与人人包网已确认数据泄漏,具体漏洞已经修复,并且支付“某Hack”封口费。

1🤮1

Signed 小国

1 Aug 2026, 03:22 UTC≈4,340 views12 reactionsread 7 August 2026
Photo

🏳️ @TGSEC 渗透午报 ✅随着TG越来越多的人才涌入漏洞挖掘的行业,网络安全问题也日益突出,方阳,一个让某钱包以及富贵娱乐产品头疼的Hack,我始终坚信一点,攻防无绝对,技术无黑白。 💎方阳在6月份发现的 @Youbo 娱乐BUG,其中已早早反馈给富贵集团方面,可惜富贵娱乐只开价1888美金,这时又悬赏50万美金信息,小国想说,当时大方一点,是不是没后面这些事了呢?没有人愿意多一个敌人,更希望是多一个朋友,同时也希望更多的人加入这一行业,打击垃圾技术产品。 📍我在TGSEC等你!

👍65😡1

Signed XiaoGuo

30 Jul 2026, 14:07 UTC≈1,920 views3 reactionsread 7 August 2026
Video

🧧 兮夜 发了一个会员红包 💴 188 CNY · 剩余 0/20 💎 仅 TG 会员(Premium)可领 🔒 领取条件: · 需在 HackBar 内 · 累计发言 ≥ 20 次 🥇 12.9 💴 - 结果比过程重要 🥈 12.88 💴 - Teto查档/天眼查/信息调取/开盒 🥉 12.76 💴 - 鲨鱼@mili 🧧 12.51 💴 - ￴ 🧧 12.11 💴 - 7 🧧 12.1 💴 - H 🧧 10.94 💴 - 宇 接CC 🧧 10.19 💴 - 漢壽亭 🧧 9.78 💴 - 周同學 🧧 9.61 💴 - ❄️入几 🧧 9.42 💴 - 峰 🧧 8.84 💴 - 白月光 🧧 7.37 💴 - 归途 🧧 6.84 💴 - 大鱼 🧧 6.71 💴 - 冷风 … 更多领取记录请打开红包查看

2😡1

Signed 兮夜

27 Jul 2026, 02:04 UTC≈2,430 views6 reactionsread 7 August 2026

✈️ @TGSEC·社区整体在发展 ⬆️技术/安全/开发人员通过靶场测试即可免费进入 🔨考官风起: @GGGWW 🪙付费进入88💲通过狗经理付款进入~ @gouer 👤对于广告计划暂时没有打算开启 ➡️目前社区群内管理位置比较紧张,请各位朋友不要再申请了。 🛡群内成员位置也比较有限,因为我们致力于做专业化、标准化的社区建设,严格审核每一位成员。 ⭐️对于广告席位暂时不接受投放,也感谢多位无私奉献的朋友,比较多暂不一一列举。 💎对于想投放广告的老板支持赞助模式,在社区群内举行抽奖活动,不限制金额,以及份数,因为只要有心意即可。 👤近期还有部分朋友,信任 @TGSEC 信任小国和兮夜的老板被恶意诈骗,在这里小国说一声对不起,再次提示大家! ✅小国 : @GODK ✅兮夜 : @XIYE ✅狗儿 : @GOUER

5👎1

Signed 小国

26 Jul 2026, 23:25 UTC≈5,630 views2 reactionsread 7 August 2026
Photo

😀 @TGSEC 热点渗透事件快报 今日凌晨 @Farmtg 农场被某Hack入侵后台导致全服务器玩家游戏金币暴增!导致农村经济体系紊乱。 小国评价: 应该是疑似来自于 @TGSEC 社区的群友 @Ji1111 因为种子修改为大克西瓜等…🍉

2

Signed 小国

24 Jul 2026, 19:45 UTC≈2,340 views20 reactionsread 7 August 2026

😀《新手SEC快速升级指南》 一、基础知识速通: 1.逻辑漏洞类型: 并发、条件竞争: 多线程并发发包‑ 余额10元,并发2次提现10元,两次同时执行,扣一次钱、提现两次。 越权: 1.水平越权(改参数 user_id=123,直接看别人订单、手机号、收货地址;代码只查id,不校验归属人。) 2.垂直越权:(普通用户直接访问管理员接口 /admin/delUser,没有角色校验,直接当管理员。) 3.未授权(不用登录Token,直接访问后台接口、文件、后台页面。) 支付/交易逻辑: 1. 金额客户端可控 前端传 price=1,抓包修改价格,1分钱买高价商品。 2. 负数金额 传 -999,平台给账户充值余额。 3. 重复下单(重复支付) 支付成功后页面刷新,多次扣款;或者多次生成订单,只扣一次钱拿到多份商品。 4. 优惠券叠加无限制 多张优惠券无限叠加,订单金额变成0。 5. 订单状态篡改 抓包修改订单

12👍7😢1

Signed 国 @godk

24 Jul 2026, 14:02 UTC≈3,450 views8 reactionsread 7 August 2026
Photo

Photo, posted without a caption

7🤮1

Signed 国 @godk

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

Citation-graph rank — 864,720 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.

Mentions

Named by 3 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 14 August 2026 — this entry's latest reading, not the date you are reading this.

“𝙏𝙂 · 𝙎𝙀𝘾” (@tgsec), 3,090 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/tgsec.

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.