人家做的群发项目做的挺好,所以我不予公开😁,想玩请购买正版
👍2🔥2❤1

Channel
@wa_001
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
71subscribers
+38 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003923696694 |
|---|---|
| Type | Channel |
| Username | @wa_001 |
| Created | Between 1 April 2026 and 8 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/wa_001 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 23:18 | 71 | +2 |
| 8 Sept 2026, 23:15 | 69 | +4 |
| 30 Aug 2026, 21:34 | 65 | +9 |
| 24 Aug 2026, 19:28 | 56 | +8 |
| 16 Aug 2026, 19:57 | 48 | +9 |
| 10 Aug 2026, 20:16 | 39 | no change |
| 8 Aug 2026, 19:23 | 39 | +6 |
| 8 Aug 2026, 12:02 | 33 | first reading |
19 posts held, back to 8 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 19 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.
31 reactions across 12 posts, in 4 distinct kinds. The most used accounts for 61.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 19 | 61.3% | |
| 👍 | 9 | 29.0% | |
| 🔥 | 2 | 6.45% | |
| 🥰 | 1 | 3.23% |
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 13 of the 19 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 31 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 8 August 2026 to 10 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.
人家做的群发项目做的挺好,所以我不予公开😁,想玩请购买正版
👍2🔥2❤1
ename 机制:project/ 下 .php 返回 404 发现:文件支持 rename 那么继续提rce权限😁 上传图片马 —- rename 成 .php —- 执行 成功提rce✅ 部署到 admin.php 登录检查之前,未登录可触发😁
该网站文件上传提rce漏洞又被管理员修复 但是网页还是未修复,依旧一片中国红 貌似为了证据提交印度条子
❤2🥰1
破解成功,并且拿到原卡密验证接口的后台登录地址
❤4👍1
你猜管理员会先恢复服务器数据还是先修复漏洞😁
CV. Sarana Jasa Bersama – 光纤与电信基础设施
👍4❤1
Photo, posted without a caption
❤3
本次对 163.227.52.49 服务器的渗透,核心原因是后台弱密码 + 上传漏洞,最终拿下整台服务器的多个站点权限 1 用简单弱密码登录了系统后台面板;404 Not Found(为了气管理员我已经将后台更改了站点,以及后台密码🙈,所以你们点开是404) 2 后台上传功能没有任何文件格式限制,可以直接上传 PHP 木马文件; 3 访问上传的木马后,成功获取服务器执行权限,实现远程命令执行;(依旧是提权rce) 4顺势拿下同服务器4 个业务站点,窃取到账号密码、数据库、各类平台密钥等核心数据;(为什么做这些应为我想从泄露的数据里看看能不能找到系统sudu的密码,结果没找到🤡): |SJB Core管理面板 | https://jasabersama.id/admin.php | 无账号,仅密码 | Long#554109 | | absensi考勤系统普通HR账号 | https://absensi.jagoandata.…
印尼这台服务器费尽周折修复了一堆漏洞 好消息是他不止一个站点并且存在漏洞 子站点:jasabersama.id 直接下手 接下来分享一下全过程
还勾吧的限速了
所有站点漏洞皆被发现并修复
❤1
管理员发现了漏洞点禁止上传php文件😂
❤1
Showing the 12 most recent of 19 posts we hold for @wa_001. 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.
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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“网络安全维护部” (@wa_001), 71 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/wa_001.
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.