Telegram RegisterThe public register of Telegram
Telegram profile photo for IXCM工作室

Channel

IXCM工作室

@ixcmstudio

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

36subscribers

-1 since we began measuring on 12 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001226732414
TypeChannel
Username@ixcmstudio
CreatedBetween 1 April 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live16 November 2026
Measurements held3
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/ixcmstudio

Topic

Hacking & security — a classification, not a measurement. An on-box language model (qwen3.6:35b-a3b, prompt version 1) read this channel’s own recent posts on 16 November 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 the other topics.

Growth

363736.512 August 2026 — 37 subscribers13 August 2026 — 37 subscribers16 November 2026 — 36 subscribers12 August 202616 November 2026
3 measurements spanning 96 days, 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 36–37 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Nov 2026, 14:1736-1
13 Aug 2026, 05:4737no change
12 Aug 2026, 16:3137first reading

Engagement

20 posts held, back to 6 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 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 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

3 reactions across 1 post, in 2 distinct kinds. The most used accounts for 66.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🫡266.7%
❤133.3%

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

Measured over the 20 most recent posts we hold, published 6 December 2025 to 7 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

7 Aug 2026, 10:05 UTC6 viewsread 12 August 2026

Linux KVM 虚拟化逃逸漏洞 CVE-2026-64561 此漏洞存在导致虚拟机逃逸的风险,所有运行 KVM/QEMU 虚拟化环境的用户应当及时检查 Linux 内核版本并更新补丁。 该漏洞存在于 Linux Kernel KVM x86 MMU 子系统中,在处理虚拟机内存页表状态时,由于对失效/过期 MMU root 状态检查不足,特定情况下可能导致宿主机内核异常,并存在从 Guest 虚拟机影响 Host 宿主系统的潜在风险。 受影响版本: Linux Kernel 5.9 及以上版本(启用 KVM x86 虚拟化环境时受影响) 建议所有使用 Proxmox VE、KVM/QEMU、libvirt、OpenStack 等虚拟化平台的管理员尽快升级宿主机内核,并重启加载最新内核版本,以降低虚拟机逃逸风险。 #特别安全事件 #需要注意的安全事件 #安全报告

17 Jun 2026, 00:56 UTC209 viewsread 12 August 2026

哪吒监控疑似出现批量入侵事件 攻击者在获取 Dashboard 控制权限后,可通过 Agent 的远程命令执行能力,向所有接入节点批量下发恶意命令,植入挖矿程序、后门、公钥及内存马等恶意组件。 注意:该攻击无需 SSH 登录,即使已禁用 SSH 密码登录,若 Agent 以 root 权限运行,节点仍可能受到影响。 建议: 升级至最新版本或临时下线 Dashboard; 排查所有 Agent 节点是否存在异常进程、自启动服务及未知 SSH 公钥; 已确认失陷的主机及时更换 SSH Key、轮换重要凭据,重要业务建议重装系统。 参考检查 #安全报告 #需要注意的安全事件 #特别安全事件

14 May 2026, 06:05 UTC250 viewsread 12 August 2026

【紧急】NGINX 远程代码执行漏洞 CVE-2026-42945 此漏洞存在远程代码执行的风险,所有使用NGINX的用户都应当立即检查版本与 rewrite 配置。 该漏洞存在于 rewrite 模块中,特定 rewrite/if/set 规则在处理恶意请求时可能触发堆内存溢出(Heap Overflow),造成 Worker 崩溃,并存在潜在远程代码执行(RCE)风险。 受影响版本: 0.6.27 - 1.30.0 修复版本: 1.30.1+ 官方公告 #紧急安全事件 #特别安全事件 #需要注意的安全事件 #安全报告

8 May 2026, 01:54 UTC264 viewsread 12 August 2026

【安全提示】Linux Dirty Frag 本地提权漏洞 近日,安全研究员公开披露 Linux 内核 Dirty Frag 本地提权漏洞链。该漏洞可在攻击者已获得本地代码执行权限的情况下,将普通用户权限提升至 root。PoC 已公开,暂未看到正式 CVE 编号,部分发行版补丁状态仍需持续关注。本事件不属于远程无认证漏洞,但对多用户服务器、VPS、容器宿主机、Kubernetes 节点、CI Runner、Web 面板服务器等环境风险较高。 临时缓解: 在确认业务不依赖 IPsec ESP、RxRPC、AFS 等功能的前提下,可临时禁用相关模块: sh -c "printf 'install esp4 /bin/false\ninstall esp6 /bin/false\ninstall rxrpc /bin/false\n' > /etc/modprobe.d/dirtyfrag.conf; rmmod esp4 esp…

8 May 2026, 01:52 UTC28 viewsread 12 August 2026

关于 Linux 内核 Dirty Frag 本地提权漏洞的风险说明 近日,安全研究员 Hyunwoo Kim(V4bel)公开披露了 Linux 内核本地提权漏洞链 “Dirty Frag”。 根据作者公开的 GitHub 仓库和 oss-security 公告,Dirty Frag 通过串联两个 Linux 内核 page cache 写入问题实现本地提权: xfrm-ESP Page-Cache Write RxRPC Page-Cache Write 该漏洞链与 Dirty Pipe、Copy Fail 属于相近的 page cache / zero-copy / splice 相关漏洞类型,但 Dirty Frag 并不是 Copy Fail 本身。 Dirty Frag 属于本地权限提升漏洞(LPE)。攻击者需要先具备本地代码执行能力,例如: 普通 Linux 用户账号 WebShell 被入侵的服务进程 CI/…

2 May 2026, 14:17 UTC26 views3 reactionsread 12 August 2026

服务器总控制室奖励升级Debian13的用户7天VPS使用时间延长 受到 Linux内核提权漏洞 Copy Fail / CVE-2026-31431 影响 为了促进系统更新,服务器总控制室(术)决定: 奖励所管辖区域内所有升级到Debian13的Debian用户延长7天VPS使用时长。 收到相关通知的用户可以在活动期间通过购买VPS的所属平台打开工单并发送符合规定的截图以兑换。 谢谢大家的理解与支持。

🫡2❤1

1 May 2026, 03:22 UTC24 viewsread 12 August 2026

Debian 11 bullseye:已修复,bullseye-security 5.10.251-3 fixed Debian 12 bookworm:已修复,bookworm-security 6.1.170-1 fixed Debian 13 trixie:已修复,trixie-security 6.12.85-1 fixed Debian sid / forky:已修复,sid 7.0.3-1 fixed,forky 6.19.14-1 fixed Ubuntu 20.04 / 22.04 / 24.04 / 25.10:已发布 kmod 临时缓解更新,内核修复仍在发布过程中 Ubuntu 26.04:不受影响 RHEL / Rocky Linux:官方仍显示 Ongoing / Important,建议按等待修复内核处理 AlmaLinux:testing 仓库已有抢先修复内核,正式生产仓库仍需继续关注 …

30 Apr 2026, 04:00 UTC261 viewsread 12 August 2026

【紧急】Linux内核提权漏洞 2026-04-30公布 所有 Linux 服务器、容器宿主机、虚拟化节点和多用户环境应优先处理。 近期公开的 Copy Fail / CVE-2026-31431 是 Linux 内核本地提权漏洞。攻击者在获得普通用户权限后,可能进一步提权到 root。 受影响范围主要包括未更新安全补丁的 Linux 系统,尤其是 Docker、LXC、Kubernetes、CI Runner、多用户服务器、虚拟主机、VPS 等共享内核或多人使用环境。 漏洞大致原理是:内核加密接口相关逻辑存在缺陷,可能导致系统文件的内存缓存被篡改,从而实现提权。 请Linux发行版用户或管理员尽快执行系统更新,并在更新后重启服务器,例如Debian/Ubuntu: apt update && apt full-upgrade -y reboot 无法立即更新的用户,可临时禁用相关模块作为缓解措施: echo "inst…

23 Apr 2026, 13:39 UTC32 viewsread 12 August 2026

IXCM工作室正在对服务器进行维护,ICDOWN下载站降级运行

17 Apr 2026, 13:43 UTC39 viewsread 12 August 2026

ICDOWN下载站架构已调整完毕 本次架构调整未影响任何服务 ICDOWN下载站主站 https://d.icdown.club ICDOWN CLI Download Station http://list.d.icdown.club

15 Apr 2026, 12:08 UTC43 viewsread 12 August 2026

ICDOWN下载站设计架构将由Ver.9/10/11逐步迁移至第12版本 ICDOWN 下载站所使用的 Ver.9 / 10 / 11 架构,已经从 2021 年持续运行至 2026 年。随着使用环境、维护需求和整体架构方向的变化,这一代架构将开始逐步迁移至 Ver.12。 本次调整是面向后续数年使用体验、兼容性和维护方式的整体更新。关于旧架构的回顾、目前存在的问题、新架构的设计方向,以及后续的替换过程,已经整理成文。 建议看看全文

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

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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 16 November 2026 — this entry's latest reading, not the date you are reading this.

“IXCM工作室” (@ixcmstudio), 36 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/ixcmstudio.

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.