又一个日本网站拖库交付 群里有需要目标网站数据的,可以联系小鹿提供目标网站地址。小鹿会先评估目标情况,确认是否存在价值后,再安排渗透测试。 小鹿: @xl8863 AI渗透教学:@dx8666 AI渗透交流群(禁广,只技术交流):@hack366

Channel
【稻香】渗透教学频道
@dx86663
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
1,363subscribers
-112 since we began measuring on 25 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002506742394 |
|---|---|
| Type | Channel |
| Username | @dx86663 |
| Created | Between 1 February 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 24 September 2026 |
| Last confirmed live | 5 October 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 5 October 2026 |
| On Telegram | t.me/dx86663 |
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 25 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Oct 2026, 09:18 | 1,363 | -143 |
| 27 Sept 2026, 11:37 | 1,506 | -6 |
| 24 Sept 2026, 23:22 | 1,512 | no change |
| 18 Sept 2026, 03:17 | 1,512 | -10 |
| 13 Sept 2026, 20:59 | 1,522 | -11 |
| 10 Sept 2026, 01:40 | 1,533 | -1 |
| 4 Sept 2026, 18:38 | 1,534 | +18 |
| 1 Sept 2026, 08:15 | 1,516 | +23 |
| 29 Aug 2026, 00:23 | 1,493 | +15 |
| 26 Aug 2026, 10:23 | 1,478 | +3 |
| 25 Aug 2026, 23:00 | 1,475 | first reading |
Engagement
14 posts held, back to 27 August 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 1 page of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 33.9%
- avg views ÷ 1,363 subscribers
- Avg views / post
- 462
- 10 posts measured
- Reaction rate
- 0.215%
- reactions ÷ views · ER floor
- Posts in window
- 10
- of 14 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. It is computed over the 5 of 10 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 23 September 2026 |
|---|---|
| Posts held | 14 (27 August 2026 – 23 September 2026) |
| Views total | 4,621 |
| Reactions total | 5 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 24 Sept 2026, 23:22 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
7 reactions across 7 posts, in 2 distinct kinds. The most used accounts for 71.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 💩 | 5 | 71.4% | |
| ❤ | 2 | 28.6% |
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 7 of the 14 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 7 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 27 August 2026 to 23 September 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
全自动 AI 渗透,主打的就是真实可靠。这个站的数据量不算大,5W+ 左右。好在整个过程基本不用怎么动脑,小白 0 基础也能快速上手,让 AI 自动完成渗透和漏洞挖掘,还能自动整理复现步骤。 确认漏洞后,再用工具完成数据拖库导出整理,最后交付客户完工,整个流程下来比起以前省了太多时间。 群里有需要目标网站数据的,可以联系小鹿提供目标网站地址。小鹿会先评估目标情况,确认是否存在价值后,再安排渗透测试。 小鹿: @xl8863 AI渗透教学:@dx8666 AI渗透交流群(禁广,只技术交流):@hack366
一个小小的美国保险站,个人信息数据量不大。客户刚好有需求,整理出来就可以交付了。 群里有需要目标网站数据的,可以联系小鹿提供目标网站地址。小鹿会先评估目标情况,确认是否存在价值后,再安排渗透测试。 小鹿: @xl8863 AI渗透教学:@dx8666 AI渗透交流群(禁广,只技术交流):@hack366
💩1
温馨提醒一下:现在 AI 的渗透能力越来越强。如果你人在村内,使用 AI 对村内网站进行渗透,提示词没有做好范围和权限限制,一旦误操作到相关网站,需要特别注意自身安全问题。网站运营者通常可以通过访问日志、IP、请求特征等信息进行溯源。大家在使用 AI 做安全测试时,务必做好自身隐身安全。 群里有需要目标网站数据的,可以联系小鹿提供目标网站地址。小鹿会先评估目标情况,确认是否存在价值后,再安排渗透测试。 小鹿: @xl8863 AI渗透教学:@dx8666 AI渗透交流群(禁广,只技术交流):@hack366
❤1
日本电商站的防护就这么脆弱吗?AI又挖到一个高危注入漏洞,基本就是直接拖库的节奏了。 群里有需要目标网站数据的,可以联系小鹿提供目标网站地址。小鹿会先评估目标情况,确认是否存在价值后,再安排渗透测试。 小鹿: @xl8863 AI渗透交流群(禁广,只技术交流):@hack366
💩1
越南医疗网站防御做得这么好?跑了一圈下来,高危漏洞一个没发现,反而先挖出几个中危信息泄露。 群里有需要目标网站数据的,可以联系小鹿提供目标网站地址。小鹿会先评估目标情况,确认是否存在价值后,再安排渗透测试。 小鹿: @xl8863 AI渗透交流群(禁广,只技术交流):@hack366
💩1
今天这个站前前后后深挖了 3 次。 第一次 AI 跑完后,报告直接说没有发现漏洞,我当时也以为这个站应该没什么问题。但经验告诉我,这个站没那么简单,所以又重新跑了几轮。果然,第三次终于挖出了漏洞。 现在发现的这个 信用卡表,感觉不太像是铭文的数据。关键是目前这个点属于布尔盲注,真要直接拖库,估计得跑很久,确实有点头大。 群里有需要目标网站数据的,可以联系小鹿提供目标网站地址。小鹿会先评估目标情况,确认是否存在价值后,再安排渗透测试。 小鹿: @xl8863 AI渗透交流群(禁广,只技术交流):@hack366
💩1
群友提供的越南某政府网站,AI漏扫过程中发现了一个明显过期的 SharePoint 版本,存在进一步排查已知漏洞的价值(高危漏洞),但仅凭版本号还不能证明可以直接利用,感觉供给面确实小了点。应该拿不下这个站。 群里有需要目标网站数据的,可以联系小鹿提供目标网站地址。小鹿会先评估目标情况,确认是否存在价值后,再安排渗透测试。 小鹿: @xl8863 AI渗透交流群(禁广,只技术交流):@hack366
复现这个 TW 购物站中,SQLMap 在遇上时间盲注枚举阶段确实非常慢。结合目前已经枚举出的表名来看,dbo.ASP_CUSTOMER 高度疑似与用户/客户信息相关,后续我将重点关注该表的字段结构。 渗透技术无广告交流群: @hack366
AI 渗透实战,又挖出一个注入漏洞,目标是台湾某大型购物网站。看了下漏洞情况,感觉这条链子不止于注入,后面还有机会继续往上提权。 渗透技术无广告交流群: @hack366
AI 渗透实战:一个带 WAF 的台湾电商网站,丢给 AI 自主跑。 小睡 30 分钟醒来,SQL 注入直接挖出来了。 AI 渗透的效率拉满,这波数据不就信手拈来了? 渗透技术无广告交流群: @hack366
💩1
新建渗透技术交流群,欢迎想交流AI渗透技术的进来;广告请去其他几个群。 https://t.me/hack366
Showing the 12 most recent of 14 posts we hold for @dx86663. 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.
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 5 October 2026 — this entry's latest reading, not the date you are reading this.
“【稻香】渗透教学频道” (@dx86663), 1,363 subscribers as measured 5 October 2026. Telegram Register, tgregister.com/channel/dx86663.
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.