Channel

OS Internals

@OxAA55

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

3,564subscribers

-7 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID	-1001352836538
Type	Channel
Username	@OxAA55
Created	Between 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded	7 August 2026
Last confirmed live	10 August 2026
Measurements held	4
Confirmed unchanged	1 time, most recently 10 August 2026
On Telegram	t.me/OxAA55

Growth

4 measurements spanning 4 days, net -7. 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 3,563–3,572 and does not start at zero.

Measurement log — every subscribers count we have recorded
Measured (UTC)	Subscribers	Change
10 Aug 2026, 20:33	3,564	-6
7 Aug 2026, 10:04	3,570	-1
7 Aug 2026, 05:00	3,571	no change
7 Aug 2026, 04:48	3,571	first reading

Engagement

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

What this channel posts

Video runtime: 9m 58s
Average length: 9m 58s

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.

Reaction mix

1,189 reactions across 16 posts, in 5 distinct kinds. The most used accounts for 81.5% of them.

Every reaction kind recorded on the sample, most used first
Reaction	Count	Share
❤	969	81.5%
👏	117	9.84%
👍	90	7.57%
🤔	12	1.01%
👎	1	0.084%

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 16 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 1,189reactions 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 1 June 2025 to 3 June 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

3 Jun 2026, 11:48 UTC≈1,870 views43 reactionsread 7 August 2026

سلام به همه عزیزان، یکی از کارهایی که تجربه خیلی با ارزشی است و یادگیری زیادی داره، کار کردن روی پروژه‌های متن‌باز و پیاده‌سازی یک موردی حتی کوچک در این پروژه‌هاست. اگر دوست دارید در زمینه‌ی توسعه سطح پایین کار کنید، آقای سینا کروندی که زحمت زیادی برای پروژه‌ی عالی HyperDbg کشیده کلی ایده داره که می‌تونید با پیادسازی‌شون هم روی یک پروژه خوب کار کنید و هم اینکه با Internal ویندوز و لینوکس بهتر آشنا بشید. بهشون از …

❤34👍9

Signed Abolfazl Kazemi

12 Dec 2025, 18:55 UTC≈6,600 views69 reactionsread 7 August 2026

📢 انتشار فصل هفتم دوره Linux Exploit Development ℹ️ جزئیات ساختار فایل‌های ELF. مشاهده‌ی این فصل به علاقه‌مندان به Internal لینوکس نیز توصیه می‌شود. 📚 در این فصل به‌صورت عمیق با ساختار فایل‌های ELF آشنا می‌شویم؛ فرمت استانداردی که تمام باینری‌ها، کتابخانه‌ها و ابزارهای لینوکسی بر پایه آن ساخته شده‌اند. درک صحیح ELF نه‌ تنها برای تحلیل آسیب‌پذیری‌ها و نوشتن اکسپلویت‌ها ضروری است، بلکه برای علاقه‌مندان Linux Internal…

❤69

Signed Abolfazl Kazemi

14 Nov 2025, 19:25 UTC≈5,330 views59 reactionsread 7 August 2026

📢 انتشار فصل ششم دوره Linux Exploit Development ℹ️ مقدمات برنامه‌نویسی ROP 📚 در این فصل وارد دنیای Return Oriented Programming (ROP) می‌شویم؛ تکنیکی قدرتمند برای دور زدن مکانیزم‌های امنیتی مدرن مثل NX، ASLR و PIE. با یادگیری ROP می‌توانیم بدون نیاز به اجرای مستقیم شل‌کد، با استفاده از «گجت»‌های موجود در باینری یا کتابخانه‌ها، جریان اجرای برنامه را کنترل کنیم و به اهداف دلخواه برسیم. در این فصل ابتدا با فلسفهٔ ROP…

❤59

Signed Abolfazl Kazemi

8 Nov 2025, 05:11 UTC≈3,230 views25 reactionsread 7 August 2026

Forwarded from @securebyte

#Note #CTF چالش های وب سایت باینری گلف (binary.golf) هدف BGGP5 این بود که کوچک‌ترین کد ممکن ساخته بشه که یک فایل متنی رو از وب‌سایت BGGP دانلود و نمایش بده. در این چالش روش Peter Ferrie برام جالب بود. XN4T4MP354Q0D+kP5X2P6CF0T4uOM/063349+76391 N7M0MMJ4/65L8L1762+3M7378LM92060+36394M6+0 N053L4J63690151013/461N73M1+J04N2M86614L86 0907/+/8M4J3000T3PMtEq3EM0hjgYsALA9STH/8q6 J+ruVAYxPBB4GHwe4AEvNIc0gGS9jY3VybCAtTCBia …

👍24❤1

Signed Abolfazl Kazemi

20 Oct 2025, 17:36 UTC≈6,370 views65 reactionsread 7 August 2026

📢 انتشار فصل پنجم دوره Linux Exploit Development ℹ️ مقدمات توسعه اکسپلویت ۶۴بیتی 📚 این فصل شما را با مقدمات اکسپلویت در معماری ۶۴ بیتی آشنا می‌کند. از معرفی محیط‌های CTF و انجام مثال عملی ازPicoCTF شروع می‌کنیم، سپس اسمبلی ۶۴ بیتی و قواعد اجرای توابع در این معماری را بررسی می‌کنیم و در نهایت اولین Buffer Overflow را روی باینری‌های ۶۴ بیتی پیاده‌سازی می‌کنیم. هدف فصل این است که پل بین مفاهیم ۳۲ بیتی و دنیای ۶۴ بیتی…

❤60👍4👏1

Signed Abolfazl Kazemi

30 Sept 2025, 06:04 UTCviews —

OS Internals pinned Deleted message

24 Sept 2025, 22:19 UTC≈5,790 views41 reactionsread 7 August 2026

📢 انتشار فصل چهارم دوره Linux Exploit Development ℹ️ حل چالش‌های Narnia و تمرین‌ عملی اکسپلویت آسیب‌پذیری 📚 در این فصل وارد بخش عملی و چالش‌محور ۳۲بیتی می‌شویم. مجموعه چالش‌های Narnia از سایت OverTheWire را مرحله‌به‌مرحله حل می‌کنیم تا مفاهیم مختلفی مثل Buffer Overflow، انجام Hijacking مسیر و استفاده از آسیب‌پذیری‌های Format String برای اجرای Shellcode را تمرین کنیم. هر مسئله یک تکنیک مشخص را در بر داشته و به شما…

❤37👍4

Signed Abolfazl Kazemi

4 Sept 2025, 07:38 UTC≈6,650 views78 reactionsread 7 August 2026

📢 انتشار فصل سوم دوره Linux Exploit Development 📚 در این فصل با مهم‌ترین مکانیزم‌های امنیتی لینوکس مثل Stack Canary و Position Independent Code (PIC) آشنا می‌شویم و یاد می‌گیریم این ویژگی‌ها چگونه جلوی بسیاری از حملات را می‌گیرند. ℹ️سپس وارد مباحث عملی‌تر مثل اجرای شل‌کد روی استک، باینری‌های setuid و استفاده از ابزارهای معروف اکسپلویت مثل Metasploit، msfvenom و Pwntools می‌شویم. در نهایت، اولین اکسپلویت کامل خود را…

❤74👏4

Signed Abolfazl Kazemi

28 Aug 2025, 10:21 UTCviews —

OS Internals pinned «📢🐧 مخزن دوره‌ی Linux Exploit Development روی گیت‌هاب ایجاد شد. از این به بعد همه‌ی منابع و فایل‌های کمکی دوره از طریق این مخزن منتشر می‌شن. 📂 لینک مخزن: 👉 https://github.com/akazemi67/Linux-Exploit-Development-Course ⚠️ ویدئوها به زبان فارسی هستن و مستندات…»

28 Aug 2025, 10:20 UTC≈5,990 views88 reactionsread 7 August 2026

📢 انتشار فصل دوم دوره Linux Exploit Development 📚 توی این فصل وارد دنیای اکسپلویت می‌شیم. قبل از هر چیز ابزارها و مفاهیم پایه مثل GDB و اسمبلی رو مرور می‌کنیم، بعد یاد می‌گیریم چطور توی سطح پایین با کدها و فراخوانی توابع کار کنیم. کم‌کم می‌ریم سراغ اصول اولیه اکسپلویت، تغییر آدرس بازگشت و در نهایت اولین Stack Overflow خودمون رو می‌سازیم. این فصل در واقع نقطه شروع عملی برای بحث توسعه اکسپلویت محسوب می‌شه. ✍️ لینک و…

❤74👏8👍6

Signed Abolfazl Kazemi

26 Aug 2025, 19:56 UTC≈5,860 views83 reactionsread 7 August 2026

📢🐧 مخزن دوره‌ی Linux Exploit Development روی گیت‌هاب ایجاد شد. از این به بعد همه‌ی منابع و فایل‌های کمکی دوره از طریق این مخزن منتشر می‌شن. 📂 لینک مخزن: 👉 https://github.com/akazemi67/Linux-Exploit-Development-Course ⚠️ ویدئوها به زبان فارسی هستن و مستندات مخزن به زبان انگلیسی آماده شدن. #linux #exploitdev #GitHub

❤72👍10👏1

Signed Abolfazl Kazemi

21 Aug 2025, 07:41 UTC≈9,100 views128 reactionsread 7 August 2026

📢 انتشار فصل اول دوره توسعه اکسپلویت در لینوکس 📚 این فصل شامل ۷ ویدئو می‌باشد و در آن با مفاهیم بنیادین اجرای برنامه‌ها در سیستم‌عامل لینوکس آشنا می‌شوید؛ از مروری بر برنامه‌نویسی و ساختار فایل‌های اجرایی گرفته تا نحوه‌ی ایجاد و اجرای پروسه‌ها و مدیریت حافظه. این فصل پایه‌ای محکم برای درک مباحث پیشرفته‌تری ایجاد می‌کند که در فصل‌های آینده به آن‌ها خواهیم پرداخت. ✍️ لینک ویدئوهای فصل در یوتیوب: 00) Course Introducti…

❤110👍10👏8

Signed Abolfazl Kazemi

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

Citation-graph rank

Citation-graph rank — 688,255 of 1,160,990entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

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

امنیت دانشگاه تهران
@utPentest · 2132 posts

Republishes

Channels on the register whose posts this channel has forwarded.

کانال بایت امن
@securebyte · 4,8462 posts

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

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.

امنیت دانشگاه تهران
@utPentest · 2131 post

Names

Channels on the register whose handles appear in this channel's posts.

کانال بایت امن
@securebyte · 4,8462 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.

“OS Internals” (@OxAA55), 3,564 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/OxAA55.

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.