Chatgpt Puls申请教程

Channel
黑客早知道
@csrinfo
On this record: Topic · Growth · Engagement · Posts · Cite this entry
1,349subscribers
-11 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001404481108 |
|---|---|
| Type | Channel |
| Username | @csrinfo |
| Created | Between 1 December 2018 and 30 November 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/csrinfo |
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 17 September 2026 and assigned it the closest of 31 fixed categories, at 90% 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 |
|---|---|---|
| 11 Oct 2026, 16:17 | 1,349 | -17 |
| 5 Oct 2026, 02:56 | 1,366 | -18 |
| 26 Sept 2026, 12:54 | 1,384 | -25 |
| 17 Sept 2026, 20:01 | 1,409 | -1 |
| 13 Sept 2026, 20:59 | 1,410 | -1 |
| 10 Sept 2026, 03:37 | 1,411 | -5 |
| 4 Sept 2026, 22:18 | 1,416 | -6 |
| 1 Sept 2026, 12:43 | 1,422 | +70 |
| 29 Aug 2026, 02:45 | 1,352 | -2 |
| 26 Aug 2026, 07:11 | 1,354 | -2 |
| 23 Aug 2026, 14:47 | 1,356 | -1 |
| 19 Aug 2026, 14:42 | 1,357 | -1 |
| 16 Aug 2026, 16:23 | 1,358 | +1 |
| 12 Aug 2026, 20:13 | 1,357 | -2 |
| 10 Aug 2026, 00:02 | 1,359 | -1 |
| 6 Aug 2026, 08:00 | 1,360 | no change |
| 6 Aug 2026, 06:59 | 1,360 | first reading |
Engagement
20 posts held, back to 11 December 2021 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 8 February 2023. An engagement rate over an empty window would be a number about nothing.
Recent posts
这个POC基本差不多: https://github.com/dinosn/spring-core-rce/blob/main/test.py
spring core rce是真的,class随意控制,玩法非常多
那个exe带vmp壳的poc, 是木马😅
来了来了 RCE他又来了
/check?cmd=ping..%2F..%2F..%2F..%2F..%2F..%2F..%2F..%2F..%2Fwindows%2Fsystem32%2FWindowsPowerShell%2Fv1.0%2Fpowershell.exe+" + cmd)
向日葵🌻就是个命令拼接漏洞
😂
Photo, posted without a caption
😂
几小时前新出炉的Linux“几乎”通杀提权:https://github.com/arthepsy/CVE-2021-4034
File, posted without a caption
Showing the 12 most recent of 20 posts we hold for @csrinfo. 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 11 October 2026 — this entry's latest reading, not the date you are reading this.
“黑客早知道” (@csrinfo), 1,349 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/csrinfo.
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.