国家计算机病毒应急处理中心预警“Sorry”勒索病毒 国家计算机病毒应急处理中心 8 月 10 日通报,近日发现多起境内用户遭“Sorry”勒索病毒攻击事件。该病毒使用 GO 语言编写,主要瞄准暴露在互联网的 Linux Web 服务器,利用 cPanel 漏洞获取管理权限后植入,会伪装成 sshd 进程。病毒运行后会回传系统信息、窃取业务数据与内部文件,使用 AES 算法加密用户文件,并通过扫描 SSH 端口、弱密码爆破等方式在内网横向传播,可能造成企业内网大面积感染。目前,被加密数据在没有解密密钥的情况下暂无可靠恢复方法。 中心建议相关单位和用户及时修补 cPanel、WHM 等相关服务漏洞,避免管理后台直接暴露于互联网,做好口令安全管理与数据离线备份,并保持杀毒软件实时监控开启。 国家计算机病毒应急处理中心 🌸 在花频道 · 茶馆水群 · 投稿通道

Channel
Augists新闻精选
@Augists
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
46subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001474842953 |
|---|---|
| Type | Channel |
| Username | @Augists |
| Description | 手工汇集各类新闻频道,人工筛选,只转发有价值的新闻 |
| Created | Between 1 April 2019 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/Augists |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 14:45 | 46 | no change |
| 7 Aug 2026, 20:19 | 46 | first reading |
Engagement
19 posts held, back to 5 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 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 4.69%
- avg views ÷ 46 subscribers
- Avg views / post
- 2.2
- 19 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 19
- of 19 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.
| Window | Rolling 30 days · latest post in window 10 August 2026 |
|---|---|
| Posts held | 19 (5 August 2026 – 10 August 2026) |
| Views total | 41 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Aug 2026, 14: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.
What this channel posts
- Photos
- ≈4,550
- Videos
- ≈224
- Links
- ≈8,040
Lifetime counters from Telegram’s own channel header, read 10 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
- Video runtime
- 32s
- Average length
- 32s
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Recent posts
Dopamine 3.0 为 iOS 26 带来首个越狱 iOS 26 发布 326 天后迎来首个越狱。Dopamine 开发者 Lars Fröder(opa334)发布 Dopamine 3.0,新增对 iOS 26.0 和 iOS 26.0.1 的支持,但适用设备限于搭载 A12 或 A13 芯片的机型。 新版本还支持运行 iOS 16.5.1 至 iOS 17.3.1 的所有设备,进一步扩大了兼容范围。 MacRumors 🌸 在花频道 · 茶馆水群 · 投稿通道
macOS 屏幕共享曝高危漏洞,无需密码即可登录任意账户 安全研究人员公开了苹果 macOS 屏幕共享功能中的一个关键漏洞 PoC(CVE-2026-65400)。一旦屏幕共享处于开启状态,任何网络攻击者都可在不知道密码的情况下,以任意账户身份登录受影响的 Mac。 苹果已在 macOS 26.6.1 中修复此漏洞,用户应尽快升级。研究人员称已逆向工程该补丁以厘清漏洞根因与利用路径,完整技术分析将于明日发布。 Calif 🌸 在花频道 · 茶馆水群 · 投稿通道
Microsoft Edge 即将屏蔽流行扩展 uBlock Origin #Internet_Explorer 微软正在跟随 Google 的脚步,即将停止支持 Manifest V2 扩展如广告屏蔽扩展 uBlock Origin。微软称其扩展商店 Edge Add-On Store 只有 58 个高使用量扩展仍然是基于 Manifest V2,只有 3 个没有提供 Manifest V3 扩展。微软表示从本月开始逐步默认关闭所有剩余的 Manifest V2 扩展,用户会收到通知。微软计划到今年年底消费者用户扩展迁移到 Manifest V3,2027 年初关闭企业用户的 Manifest V2 扩展。使用 uBlock Origin 的用户可以改用精简版本 uBlock Origin Lite,或者用 Edge 下载 Firefox。 https://www.theverge.com/tech/976880/micro…
字节跳动开发 10 万亿参数模型 #人工智能 字节跳动正在训练一款 10 万亿参数模型。新模型目前正处于预训练阶段。这一过程通常需要耗时三到六个月,随后才能进入微调并最终发布。中国 AI 公司如月之暗面的 Kimi K3 模型有 2.8 万亿参数,而美团的 LongCat-2.0 与 DeepSeek 的 V4-Pro 有 1.6 万亿的参数。Anthropic 最先进的 Mythos 5 参数量估计为 8 万亿,Fable 5 约为 5 万亿。这意味着,单从规模指标来看,字节跳动研发的新模型在规模上已与 Mythos 相近。 https://www.ft.com/content/9b8383b1-a28d-4940-8c4e-2f0cd21556ef https://www.zaobao.com/news/china/story20260807-9486328
AMD 收购将权重直接刻在芯片上的 AI 初创公司 #AMD AMD 收购了将权重直接刻在芯片上的 AI 初创公司 Taalas。Taalas 创办于 2023 年,它研发专门用于执行 AI 模型推理任务的集成电路 MSIC(代表 model-specific integrated circuits),其推理速度比 GPU 和其它专用加速器高出一个数量级以上。Taalas 今年 2 月展示了它用台积电 6nm 工艺制造的测试芯片 HC1,测试显示芯片能以每秒 16,960 个 tokens 的速度处理 Meta 的 Llama 3.1 8B 模型,这一速度比英伟达的 GPU 快 48 倍,比 Cerebras 的加速器快 8.5 倍。Taalas 计划今夏推出第二代 HC2 芯片,目标是将参数数量提升至 200 亿。它的缺点是一旦部署只能使用当前的模型,新模型需要重新设计芯片,但并不需要从零开始设计,只需要更换两层金属,因此既…
中国科学家确认胶球存在 #科学 在粒子物理学中,胶球是仅仅由胶子组成的复合粒子,不包含任何价夸克。在实际发现胶球前,理论预测中的胶子是可以达成这种特殊束缚态的,因为胶子本身带有色荷,所以能够通过强核力相互作用。但由于胶球总是与其它普通的介子束缚态一同产生,所以很难在粒子加速器中探测出来。北京正负电子对撞机的北京谱仪III实验(BESIII)国际合作组,周四在巴西举行的国际高能物理大会上宣称,经过 15 年的持续研究,BESIII 实验已建立了证明胶球存在的完整证据链。2011年,BESIII合作组依靠北京正负电子对撞机产生的大量J/psi粒子,在J/psi粒子的衰变产物中发现了一个新粒子X(2370),疑似为胶球。研究团队于2024年首次利用100亿个J/psi粒子,测定了X(2370)的自旋和宇称量子数,其质量与格点量子色动力学对相同量子数胶球的理论一致。 https://zh.wikipedia.org/wiki/%E8%…
严重/漏洞:Linux KVM/x86 shadow MMU 页回收逻辑存在虚拟机逃逸漏洞 漏洞编号:CVE-2026-64561 / PoC 名称:Zapscape 严重等级:严重(KVM 虚拟机逃逸、宿主机内核代码执行) CVSS 分数:无 影响范围: 受影响组件:Linux kernel KVM/x86 legacy shadow MMU 受影响代码路径: arch/x86/kvm/mmu/mmu.c arch/x86/kvm/mmu/paging_tmpl.h 受影响版本: Zapscape (CVE-2026-64561) 涵盖从 f95eec9bed76 (2020-07-08) 到 2abd5287f083 (2026-07-21) 的范围。 受影响功能: KVM/x86 嵌套虚拟化中的 EPT/NPT shadowing、shadow page quota reclaim、recursive zap、in…
#安全资讯 安全研究员披露苹果付费的 iCloud + 隐私中继安全缺陷,会泄露用户的真实 IP 地址和 DNS。 隐私中继可以在用户使用 Safari 时使用中继节点路由流量,从而避免用户真实 IP 和 DNS 泄露。 不过安全研究员发现通行密钥使用的凭证服务会直接从设备发出请求,从而绕过隐私中继保护。 查看全文:https://ourl.co/114218?t 😁订阅 🤔解封 🥰推特 🎉CN2VPS
#人工智能 [立即抢注用户名] Cloudflare 推出面向 AI 智能体的可编程钱包,可用于 API 和内容微支付等。 这个钱包主要就是给 AI 智能体使用的,即智能体可以在访问特定商户时支付费用,与 Cloudflare 货币化网关服务配合使用。 目前该服务正在预注册用户名,每个账号仅可预注册 1 个用户名。 查看全文:https://ourl.co/114204?t 😁订阅 🤔解封 🥰推特 🎉CN2VPS
#软件资讯 企业 IT 管理员纷纷抱怨微软未经同意强制推送安装 OneDrive Photos 应用,而且该应用只能个人登录,企业账号压根无法使用。 这段时间微软悄悄向大量用户推送 OneDrive Photos,该应用捆绑在 OneDrive 中且无法单独卸载,仅支持个人用户登录。 但没想到大量企业设备也同样收到推送,IT 管理员们直接懵圈,因为没有任何策略可以阻止微软的推送安装。 查看全文:https://ourl.co/114210?t 😁订阅 🤔解封 🥰推特 🎉CN2VPS
#云计算 [紧急通知] 这下彻底死心了:甲骨文发送邮件通知,免费 VPS 必须在 8 月 18 日前主动降配,否则将被删鸡。 如果用户当前实例仍然是 4 核 + 24GB 内存 (共享总额),则必须降配,否则在 8 月 18 日甲骨文将强制删除实例。 此前有网友咨询客服得到的消息是存量用户可以继续 4 核 + 24GB 内存,现在还是得缩减到 2 核 + 12GB 内存。 查看全文:https://ourl.co/114212?t 😁订阅 🤔解封 🥰推特 🎉CN2VPS
Showing the 12 most recent of 19 posts we hold for @Augists. 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
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Mentions
Names
Channels on the register whose handles appear in this channel's posts.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“Augists新闻精选” (@Augists), 46 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/Augists.
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.