Telegram RegisterThe public register of Telegram
Telegram profile photo for ai创业与ai灰产

Channel

ai创业与ai灰产

@aicyyhc

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

3,888subscribers

+1 since we began measuring on 14 August 2026

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

Register entry

Telegram ID-1004414038120
TypeChannel
Username@aicyyhc
Created12 August 2026measured — dated from the channel’s first post
First recorded14 August 2026
Last confirmed live15 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/aicyyhc

Growth

3,8873,8883,887.514 Aug 2026, 13:17 — 3,887 subscribers15 Aug 2026, 20:37 — 3,888 subscribers14 Aug 2026, 13:1715 Aug 2026, 20:37
2 measurements spanning 1 day, net +1. 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 3,887–3,888 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 20:373,888+1
14 Aug 2026, 13:173,887first reading

Engagement

8 posts held, back to 12 August 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
0.118%
avg views ÷ 3,888 subscribers
Avg views / post
4.6
7 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
8
of 8 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 14 August 2026
Posts held8 (12 August 202614 August 2026)
Views total32
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Aug 2026, 13:17 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

14 Aug 2026, 03:23 UTC6 viewsread 14 August 2026
Photo

恶意程序负责socket通信,同时把命令写入到管道1中,shell从管道1中读取命令执行,并将结果写入到管道2中,恶意程序从管道2中读取数据,通过socket回传给攻击者。

13 Aug 2026, 06:54 UTC6 viewsread 14 August 2026
Photo

Webpack打包站点手工审计JS寻找接口往往慢人一步,生成的JS文件数量异常之多并且总JS代码量异常庞大(多达上万行),这给我们的手工测试带来了极大的不便,利用此工具可以很好解决此问题 读取/root/.ssh/authorized_keys可以发现获取到的公私钥与目标服务器的公钥匹配 尝试SSH直接登陆。多地ping了一下发现不是CDN,对目标的IP全端口扫描,发现SSH开在一个高端口,但是很遗憾登不上。这个SSH是Nginx服务器的,并不是漏洞所在的服务器。 但是刚刚读authorized_keys和history的时候发现目标服务器部署了jumpserver,并且自身在jumpserver的管理范围内

12 Aug 2026, 15:44 UTC6 viewsread 14 August 2026
Photo

查看收集到的资产,确实有一个jumpserver相关域名,解析IP与当前目标服务器为同一IP。现在就看能否获取jumpserver控制台权限。 读取jumpserver配置文件/opt/jumpserver/config/config.txt,可以获取一些敏感信息如数据库、redis密码,但是jumpserver是容器化部署,没办法直接连上。 除此之外就是SECRET_KEY和BOOTSTRAP_TOKEN

12 Aug 2026, 15:44 UTC4 viewsread 14 August 2026
File

但通过泛解析字符处理,会得到 `project/api/pdf/extract_table 401 response "not login" project/api/pd1f/extract_table 401 response "not login" project/api1/pdf/extract_table 404 response "404"` 在project/api任意类实现,都需要认证,无认证返回401,login 在project任意实现,不存在返回404 MySQL 8.0:在随后的 MySQL 8.0 版本中,JSON 支持得到了进一步增强,包括: 更丰富的 JSON 函数:新增了更多操作 JSON 数据的函数,如 JSON_TABLE 等。 性能优化:提升了 JSON 数据的处理性能,特别是在大规模数据集上的表现。 更好的与 SQL 标准的兼容性。 为了更好地理解 MySQL 的 JSON 数据类型,下面给

12 Aug 2026, 15:43 UTC3 viewsread 14 August 2026
Photo

MySQL 8.0:在随后的 MySQL 8.0 版本中,JSON 支持得到了进一步增强,包括: 更丰富的 JSON 函数:新增了更多操作 JSON 数据的函数,如 JSON_TABLE 等。 性能优化:提升了 JSON 数据的处理性能,特别是在大规模数据集上的表现。 更好的与 SQL 标准的兼容性。 为了更好地理解 MySQL 的 JSON 数据类型,下面给出了一个使用 JSON 数据类型的简单示例。

12 Aug 2026, 15:43 UTC3 viewsread 14 August 2026
Photo

宝塔的前世今生 早些年宝塔还是一个纯净的一键建站工具,不知道从什么开始,有用户发现宝塔竟然会私自把服务器信息回传到宝塔官方,回传的信息包括但不限于:服务器IP,你访问后台时的IP,服务器硬件信息,所有网站的域名等。很多人只是为了方便才使用宝塔,殊不知宝塔早就已经取证好了,要是搭建点违规网站,那后果可想而知。

12 Aug 2026, 15:43 UTC4 viewsread 14 August 2026
Photo

在 Windows 中有一个 WSC(Windows 安全中心)服务,供防病毒软件向 Windows 通知系统存在其他防病毒软件,从而禁用 Windows Defender。这个 WSC API 没有公开文档,而且需要签署与微软的保密协议(NDA)才能获取其文档。所以我决定采取一种有趣的方法,使用已经存在的防病毒软件 Avast。这个防病毒引擎包含一个名为 wsc_proxy.exe 的服务,本质上是为 Avast 设置 WSC API。 SmokeLoader会根据系统解密并加载32位或64位载荷。 随后通过RtlCreateUserThread注入到explorer中进行执行。

Showing the 8 most recent of 8 posts we hold for @aicyyhc. 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 — 1,258,255 of 1,481,217entries 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 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 August 2026 — this entry's latest reading, not the date you are reading this.

“ai创业与ai灰产” (@aicyyhc), 3,888 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/aicyyhc.

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.