Telegram RegisterThe public register of Telegram

Channel

IP4M1R

@IP4M1R

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

153subscribers

+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-1002435778327
TypeChannel
Username@IP4M1R
Descriptionچیزایی که میخونم اینجا میزارم. IP Instagram -> https://instagram.com/IP4M1R Twitter -> https://x.com/IP4M1R GitHub -> https://github.com/IP4M1R پوریا شهبا : https://t.me/hackhaven_new
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/IP4M1R

Growth

1537 Aug 2026, 18:25 — 153 subscribers8 Aug 2026, 19:15 — 153 subscribers7 Aug 2026, 18:258 Aug 2026, 19:15
2 measurements spanning 1 day. 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 152–154 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 19:15153no change
7 Aug 2026, 18:25153first reading

Engagement

20 posts held, back to 20 July 2026the 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
62.7%
avg views ÷ 153 subscribers
Avg views / post
96.0
20 posts measured
Reaction rate
2.40%
reactions ÷ views · ER floor
Posts in window
20
of 20 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. It is computed over the 11 of 20 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 8 August 2026
Posts held20 (20 July 20268 August 2026)
Views total1,919
Reactions total24
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 19:15 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
26
Videos
4
Links
92

Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

24 reactions across 11 posts, in 4 distinct kinds. The most used accounts for 62.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1562.5%
🔥729.2%
👍14.17%
🗿14.17%

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 11 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 24reactions 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 20 July 2026 to 8 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.

Advertising

Ad load
5.00%
1 of 20 posts carry an ad marker
Regulatory tokens
0
none — marked by hashtag only
Median views · ads
57.0
over 1 measured post
Median views · rest
108
over 19 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor.A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Measured over the 20 most recent posts we hold, published 20 July 2026 to 8 August 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

8 Aug 2026, 12:39 UTC31 views1 reactionsread 8 August 2026
Poll

چه نوع حمله‌ای رخ میده؟

  1. Algorithm Confusion79%
  2. SQL Injection5%
  3. Privilage Escalation to xss11%
  4. CSRF5%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

🗿1

5 Aug 2026, 07:53 UTC58 viewsread 8 August 2026
Poll

کدام یک از آسیب‌پذیری‌های زیر به مهاجم اجازه می‌دهد که درخواست‌های معتبر کاربران را بازپخش (Replay) کند و معمولا ناشی از نبود یا ضعف در مدیریت توکن‌های تراکنش است؟

  1. HTTP Request Smuggling22%
  2. Cross-Site Request Forgery (CSRF)63%
  3. Open Redirect7%
  4. Server-Side Request Forgery (SSRF)7%

Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.

2 Aug 2026, 07:31 UTC80 views1 reactionsread 8 August 2026
Poll

توی حمله Session Fixation، مهاجم چه کاری انجام میده؟

  1. 1. سرقت کوکی‌های نشست (session cookies) کاربر با استفاده از XSS21%
  2. 2. ارسال درخواست‌های جعلی برای جعل هویت کاربر در سایت0%
  3. 3. جایگزینی شناسه نشست (session ID) قربانی با یک شناسه ثابت که مهاجم از قبل تعیین کرده است79%
  4. 4. تزریق دستورات SQL برای دسترسی غیرمجاز به پایگاه داده0%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

1

1 Aug 2026, 17:41 UTC85 viewsread 8 August 2026
Poll

در حملات Remote Code Execution (RCE) که توسط مهاجم از طریق ورودی‌های ناامن رخ می‌دهد، کدام یک از اقدامات زیر موثرترین روش برای جلوگیری از این نوع حملات است؟

  1. 1. استفاده از فایروال وب (WAF) فقط13%
  2. 2. فیلتر و اعتبارسنجی دقیق تمامی ورودی‌های ورودی کاربران84%
  3. 3. رمزنگاری داده‌های حساس در پایگاه داده0%
  4. 4. محدود کردن تعداد درخواست‌ها به سرور3%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

31 Jul 2026, 07:21 UTC92 views2 reactionsread 8 August 2026
Poll

توی یک حمله Blind SQL Injection، مهاجم نمیتونه پاسخ‌های مستقیم و واضح از سرور دریافت کنه. تو این حالت، کدوم روش برای استخراج داده‌ها اغلب استفاده میشه؟

  1. 1. استفاده از خطاهای نمایش داده شده (Error-based SQLi)22%
  2. 2. تزریق کد داخل جاوااسکریپت سمت کلاینت6%
  3. 3. استفاده از Boolean-based blind SQL injection56%
  4. 4. حمله XSS برای سرقت اطلاعات دیتابیس16%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

2

30 Jul 2026, 15:37 UTC92 views2 reactionsread 8 August 2026
Photo

موقع سوکت زنی به درد میخوره

2

30 Jul 2026, 08:16 UTC77 viewsread 8 August 2026
Poll

کدوم حمله وب اپلیکیشن معمولاً از طریق تزریق کد مخرب داخل ورودی‌های کاربران انجام میشه و میتونه باعث اجرای کد داخل مرورگر بقیه کاربران بشه؟

  1. SQL Injection14%
  2. Cross-Site Scripting (XSS)80%
  3. Cross-Site Request Forgery(CSRF)3%
  4. Directory Traversal3%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

29 Jul 2026, 17:51 UTC60 views4 reactionsread 8 August 2026
Forwarded from @NetSecZFile

File, posted without a caption

🔥31

29 Jul 2026, 17:51 UTC57 views5 reactionsread 8 August 2026
AdvertisementForwarded from @NetSecZPhoto

سلام دوستان تو این پست رفتیم سراغ تحلیل و بررسی عملی یکی از آسیب‌پذیری‌های جدید و خیلی جذاب تو اکتیو دایرکتوری و سرویس‌های گواهی مایکروسافت (AD CS) یعنی CVE-2026-54121 که معروف شده به Certi-Ghost. داستان از این قراره که وقتی سرور CA نتونه اطلاعات یک هویت رو به‌طور مستقیم به دست بیاره، یک مکانیزم پشتیبان به نام Chase فعال میشه. در این پست بررسی کردیم که چطور یک مهاجم با دستکاری دو مشخصهٔ CDC و RMD می‌تونه سرور CA رو

🔥32

26 Jul 2026, 07:21 UTC110 viewsread 8 August 2026
Poll

چه نوع حمله‌ای اینجا اولویت داره؟

  1. IDOR29%
  2. Session fixation16%
  3. Token leakage via Referer header47%
  4. SQL injection8%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

25 Jul 2026, 09:43 UTC117 views2 reactionsread 8 August 2026

VLAN Hopping Attack چیه؟ یکی از حمله‌های لایه ۲ که هدفش اینه از مرز VLANها رد بشه و به VLANهای دیگه دسترسی پیدا کنه. دو روش رایج داره: Switch Spoofing: مهاجم خودش رو به‌جای یک سوئیچ جا می‌زنه. اگر DTP فعال باشه، ممکنه لینک Trunk تشکیل بشه و مهاجم به VLANهای مجاز روی اون Trunk دسترسی پیدا کنه. Double Tagging: مهاجم یک فریم با دو تگ VLAN می‌فرسته. اگر Native VLAN همون VLAN 1 پیش‌فرض باشه، سوئیچ اول تگ اول رو حذف

2

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

Polls

The 6 most recent of 12 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

8 Aug 2026, 12:39 UTCAnonymous Quiz19 voters

چه نوع حمله‌ای رخ میده؟

  1. Algorithm Confusion79%
  2. SQL Injection5%
  3. Privilage Escalation to xss11%
  4. CSRF5%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

5 Aug 2026, 07:53 UTCAnonymous Quiz27 voters

کدام یک از آسیب‌پذیری‌های زیر به مهاجم اجازه می‌دهد که درخواست‌های معتبر کاربران را بازپخش (Replay) کند و معمولا ناشی از نبود یا ضعف در مدیریت توکن‌های تراکنش است؟

  1. HTTP Request Smuggling22%
  2. Cross-Site Request Forgery (CSRF)63%
  3. Open Redirect7%
  4. Server-Side Request Forgery (SSRF)7%

Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.

2 Aug 2026, 07:31 UTCAnonymous Quiz34 voters

توی حمله Session Fixation، مهاجم چه کاری انجام میده؟

  1. 1. سرقت کوکی‌های نشست (session cookies) کاربر با استفاده از XSS21%
  2. 2. ارسال درخواست‌های جعلی برای جعل هویت کاربر در سایت0%
  3. 3. جایگزینی شناسه نشست (session ID) قربانی با یک شناسه ثابت که مهاجم از قبل تعیین کرده است79%
  4. 4. تزریق دستورات SQL برای دسترسی غیرمجاز به پایگاه داده0%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

1 Aug 2026, 17:41 UTCAnonymous Quiz32 voters

در حملات Remote Code Execution (RCE) که توسط مهاجم از طریق ورودی‌های ناامن رخ می‌دهد، کدام یک از اقدامات زیر موثرترین روش برای جلوگیری از این نوع حملات است؟

  1. 1. استفاده از فایروال وب (WAF) فقط13%
  2. 2. فیلتر و اعتبارسنجی دقیق تمامی ورودی‌های ورودی کاربران84%
  3. 3. رمزنگاری داده‌های حساس در پایگاه داده0%
  4. 4. محدود کردن تعداد درخواست‌ها به سرور3%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

31 Jul 2026, 07:21 UTCAnonymous Quiz32 voters

توی یک حمله Blind SQL Injection، مهاجم نمیتونه پاسخ‌های مستقیم و واضح از سرور دریافت کنه. تو این حالت، کدوم روش برای استخراج داده‌ها اغلب استفاده میشه؟

  1. 1. استفاده از خطاهای نمایش داده شده (Error-based SQLi)22%
  2. 2. تزریق کد داخل جاوااسکریپت سمت کلاینت6%
  3. 3. استفاده از Boolean-based blind SQL injection56%
  4. 4. حمله XSS برای سرقت اطلاعات دیتابیس16%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

30 Jul 2026, 08:16 UTCAnonymous Quiz35 voters

کدوم حمله وب اپلیکیشن معمولاً از طریق تزریق کد مخرب داخل ورودی‌های کاربران انجام میشه و میتونه باعث اجرای کد داخل مرورگر بقیه کاربران بشه؟

  1. SQL Injection14%
  2. Cross-Site Scripting (XSS)80%
  3. Cross-Site Request Forgery(CSRF)3%
  4. Directory Traversal3%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 20 most recent posts we hold, published 20 July 2026 to 8 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

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

“IP4M1R” (@IP4M1R), 153 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/IP4M1R.

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.