File, posted without a caption
Signed Mj

Channel
@ExploitChi
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,264subscribers
+3 since we began measuring on 22 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003057436848 |
|---|---|
| Type | Channel |
| Username | @ExploitChi |
| Created | Between 1 August 2025 and 16 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 22 August 2026 |
| Last confirmed live | 1 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 1 October 2026 |
| On Telegram | t.me/ExploitChi |
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 18 September 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Oct 2026, 14:21 | 1,264 | -3 |
| 16 Sept 2026, 08:00 | 1,267 | +2 |
| 12 Sept 2026, 05:39 | 1,265 | +1 |
| 7 Sept 2026, 14:20 | 1,264 | +2 |
| 27 Aug 2026, 04:25 | 1,262 | +1 |
| 24 Aug 2026, 00:08 | 1,261 | no change |
| 22 Aug 2026, 09:45 | 1,261 | first reading |
20 posts held, back to 16 October 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 26 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 videos 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.
313 reactions across 18 posts, in 10 distinct kinds. The most used accounts for 67.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 212 | 67.7% | |
| 👍 | 53 | 16.9% | |
| 👏 | 16 | 5.11% | |
| 👾 | 12 | 3.83% | |
| 💯 | 8 | 2.56% | |
| 🙏 | 3 | 0.958% | |
| 🤩 | 3 | 0.958% | |
| 🤯 | 3 | 0.958% | |
| 👎 | 2 | 0.639% | |
| 🎉 | 1 | 0.319% |
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 18 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 313 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 16 October 2025 to 26 July 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.
File, posted without a caption
Signed Mj
یکی از رایجترین اشتباهاتی که در مباحث Windows Security میبینم، استفادهی نادرست از مفاهیمی مانند Privilege، Permission، Right، Access و حتی Security Descriptor است. در این XMind تلاش کردهام تمام اجزای Security Descriptor، ارتباط بین آنها و نقش هر بخش در مدل امنیتی ویندوز را بهصورت ساختاریافته و بهعنوان یک Quick Reference ارائه کنم. امیدوارم برای علاقهمندان به Windows Internals و Cyber Security مفید باشد.
❤11👍1💯1
Signed Mj
وطنی @ExploitChi #bypass
❤7👍3👏2🤯1
Signed Mj
Analyzing Avast AV: Kernel Hooking and Driver Reverse Engineering 👾Presentation Video Blog: https://binary-win.github.io/2025/12/27/AVAST-Kernel-Hooks-and-AV-ANALYSIS.html
👏6👍2💯1
Signed Mj
"It’s a pleasure and an honor to present to you once again." #avast #av #reverse
❤5👾2💯1
Signed Mj
Photo, posted without a caption
❤15
واسه راست چین شدن نوشن پلاگین notion - enhancer لازمه
https://chain-walnut-1b1.notion.site/Kerbrosting-2b91bf2faaf88008b3aedb1fb5f47539 سلاطین اینم رد تیم: حمله kerbrosting بخونین اگر چیزی باید کم یا زیاد شه یا سوالی داشتین حتما بهم پیام بدین اگه خوشتون اومد ری اکشن بدین تا در ادامه در مورد ابزارها و راه های اجرای این سناریو رو در حالت های Gray و بلک براتون پست بزارم ❤️❤️ @MjsBabaei @ExploitChi #RedTeam #Kerbrosting #cybersecurity #PrivilegeEscalation
❤18👍5👏1👾1💯1🤯1
🔥 اسکریپت ساده برای گذاشتن Breakpoint روی تمام WinAPIهای مهم در IDA 🎯 هدف اسکریپت در تحلیل بدافزار، یکی از مهمترین کارها اینه که روی توابع حساس سیستم مثل VirtualAlloc, LoadLibrary, CreateFile, ReadFile و … بهصورت خودکار Breakpoint بگذاریم تا به محض اینکه بدافزار از آنها استفاده کرد، اجرا متوقف بشه. مزیت این روش اینه که: ✔️ روی Stub واقعی API در IAT BP گذاشته میشه ✔️ در اولین باری که بدافزار API را صدا بزند، …
❤12👍4
ساختار محیط آزمایشگاهی برای آنالیز و تحلیل بدافزار از دید منابع معتبر در این حوزه علمی که از استاد دانا و کتاب راستین نیاموزی، همچون مالی است که از دزد گرفته باشی، نه نفع دارد و نه بقا خلاصه که دنبال سرچشمه باشید و مرجع معتبر - سواد اصلی و ریشه ای تو کتابه نه دوره ممد آنالیز یا اسی هکر😂 اینام خوبه و کار رو راحت میکنه اما اصل کاری رو از دست ندین @ExploitChi #MalwareAnalysis #ReverseEngineering #RedTeam #Sysinterna…
❤20💯1🤯1
🔥 FLARE VM محیط آماده برای آنالیز بدافزار در ویندوز اگه میخوای سریع وارد فاز تحلیل بشی و وقت نصب ابزارها رو نداری، FLARE VM از تیم Mandiant یه گزینه فوقالعادهست! 🚀 فقط با یه اسکریپت، صدها ابزار تحلیل ایستا، پویا، مهندسی معکوس و حافظه روی ویندوزت نصب میشه. مخصوص تحلیلگرهایی که دنبال سرعت و نظم در کار هستن. ⚙️ مناسب برای: 🔹 تحلیل بدافزار (Malware Analysis) 🔹 مهندسی معکوس (Reverse Engineering) 🔹 پاسخ به رخداد (In…
❤11👍2🙏2👾1
🧩 انواع لینک کردن در exe فایل ها — چرا برای آنالیز بدافزار مهمه؟ Types of Linking Static linking — لینک ایستا توضیح: کد کتابخانهها هنگام کامپایل درون فایل اجرایی کپی میشود. مشخصات فنی در تحلیل : نشانهٔ مشخصی در هدر PE ندارد؛ بخشهای .text/.rdata بزرگتر میشوند و اندازه فایل افزایش مییابد. Normal Usage : برای ساخت single-executable یا اجرا در محیطهایی که کتابخانه نصب نیست. در بدافزار: پنهان کردن و بهم ری…
❤9👏3👾1
Showing the 12 most recent of 20 posts we hold for @ExploitChi. 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.
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.
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 1 October 2026 — this entry's latest reading, not the date you are reading this.
“ExploitChi” (@ExploitChi), 1,264 subscribers as measured 1 October 2026. Telegram Register, tgregister.com/channel/ExploitChi.
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.