Telegram RegisterThe public register of Telegram

Channel

Mandegar SEC🎩

@mandegar_sec

On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry

3,301subscribers

-61 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-1002358640675
TypeChannel
Username@mandegar_sec
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/mandegar_sec

Growth

3,3013,3623,331.57 August 2026 — 3,362 subscribers8 August 2026 — 3,341 subscribers11 August 2026 — 3,301 subscribers7 August 202611 August 2026
3 measurements spanning 4 days, net -61. 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,292–3,371 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 13:563,301-40
8 Aug 2026, 15:063,341-21
7 Aug 2026, 17:483,362first reading

Engagement

20 posts held, back to 29 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
23.2%
avg views ÷ 3,301 subscribers
Avg views / post
767
14 posts measured
Reaction rate
0.978%
reactions ÷ views · ER floor
Posts in window
14
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.

What these figures were computed from
WindowRolling 30 days · latest post in window 23 July 2026
Posts held20 (29 June 202623 July 2026)
Views total10,736
Reactions total105
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 23:54 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.

Reaction mix

133 reactions across 20 posts, in 4 distinct kinds. The most used accounts for 82.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
11082.7%
👍96.77%
🏆75.26%
👾75.26%

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 20 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 133reactions 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 29 June 2026 to 23 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.

Telegram Stars

Stars received
4
across the posts below
Posts paid on
1
of 20 we hold a reading for · 5%
Most on one post
4
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @mandegar_sec. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 20 most recent posts we hold for this entry, published 29 June 2026 to 23 July 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

21 Jul 2026, 16:35 UTC610 views6 reactionsread 7 August 2026

84. JSON containing JavaScript code: { "login": "admin<script>alert('hi')</script>", "password": "password" } 85. Negative numbers as strings: { "login": "-123", "password": "-456" } 86. Values as URLs: { "login": "https://admin.com", "password": "https://password.com" } 87. Strings with email format: { "login": "admin@admin.com", "password": "password@password.com" } 88. Strings with IP address format: { "login": "1

6

21 Jul 2026, 12:50 UTC≈1,940 views6 reactionsread 7 August 2026

موقع تست SSRF فقط روی "169.254.169.254" تمرکز نکنید خیلی وقت‌ ها مشکل اصلی، اختلاف بین Parser ها و Resolver هاس، نه خود Payload. برای همین این موارد رو هم به Wordlist اضافه کنید : http://127.1/ http://0/ http://[::ffff:127.0.0.1]/ http://user@internal.host/ http://allowed.com@127.0.0.1/ Decimal / Octal IP Redirect → Internal Target 📌Tips : حتماً سناریوی Redirect رو هم تست کنید بعضی برنامه‌ ها فقط URL اولیه رو اعتبا

6

19 Jul 2026, 19:32 UTC513 views5 reactionsread 7 August 2026
Forwarded from @pentesterland1

همین الان این ریلز رو ببین! 🚀 یه آسیب‌پذیری بحرانی جدید در وردپرس کشف شده که یه فرصت طلایی برای شکارچی‌های باگ (Bug Hunters) ایجاد کرده. اگه دست بجنبونی و از متدولوژی و ابزارهایی که توی این ویدیو و دایرکت توضیح دادم استفاده کنی، شانس بالایی برای گرفتن بانتی‌های سنگین داری. بانتی ها این ریلز به دلیل اینکه ایمپکت کرتیکال هست از ۲-۳ هزاردلار به بالا هست پس زمان به شدت مهمه تایم‌لاین این آسیب‌پذیری به شدت حساسه؛ پس معطل

5

Signed Mandegar Ahmadzade

19 Jul 2026, 09:18 UTC490 views7 reactionsread 7 August 2026
Forwarded from @CodeReview0o0Photo

توی این ویدیو سعی کردم به صورت ساده و با یه CTF ساده بهتون بگم چجوری از AI برای بحث پنتست / باگ بانتی / رد تیم و ... استفاده کنیم. (سعی کنین خودتون تست کنین تا دستتون بیاد کامل) https://youtu.be/Tedkf30g00E

7

Signed Mandegar Ahmadzade

16 Jul 2026, 18:16 UTC≈1,120 views11 reactionsread 7 August 2026

41. Only keys, without values: { "login":, "password": } 42. Insertion of control characters: { "login": "ad\u0000min", "password": "pass\u0000word" } 43. Long Unicode Strings: { "login": "\u0061"*10000, "password": "\u0061"*10000 } 44. Newline Characters in Strings: { "login": "ad\nmin", "password": "pa\nssword" } 45. Tab Characters in Strings: { "login": "ad\tmin", "password": "pa\tssword" } 46. Test with HTML cont

👾74

16 Jul 2026, 18:13 UTC457 views8 reactionsread 7 August 2026
Forwarded from @Chaos_nexus_techPhoto

https://youtu.be/K-mMLETBE0g آسیب‌پذیری CVE-2026-20896 در Gitea؛ جعل هویت هر کاربر با یک هدر HTTP؟ در این ویدیو به بررسی CVE-2026-20896 در Gitea می‌پردازیم؛ یک آسیب‌پذیری مرتبط با پیکربندی احراز هویت از طریق Reverse Proxy در نسخه‌های آسیب‌پذیر Docker Image. در این سناریو، تنظیمات نادرست مربوط به Trusted Proxies باعث می‌شود درخواست‌هایی که مستقیماً از سمت کلاینت ارسال می‌شوند، به‌عنوان درخواست‌های معتبر از طرف Rever

8

16 Jul 2026, 10:47 UTC≈1,560 views7 reactionsread 7 August 2026

Server Side Template Injection (SSTI) in AI Prompt Templates Python-based Web Application Attacks👾 با رشد استفاده از فریم‌ ورک‌هایی مثل LangChain و Template های داینامیک برای ساخت اپلیکیشن‌های AI، یک سطح حمله جدید هم به وجود آمده این مقاله از PyFu به بررسی Server-Side Template Injection (SSTI) در سیستم‌های مبتنی بر هوش مصنوعی میپردازد؛ جایی که ترکیب اشتباه ورودی کاربر با Prompt Template میتونه از یک مشکل ساده به یک

7

16 Jul 2026, 10:11 UTC422 views7 reactions4 Starsread 7 August 2026

⚠️ در نتیجه، اگر قابلیت Reverse Proxy Authentication فعال باشد، هر مهاجمی که به پورت HTTP کانتینر دسترسی داشته باشد میتونه با جعل هدر "X-WEBAUTH-USER"، خودش رو به‌ جای هر کاربر (حتی ادمین) معرفی بکنه و احراز هویت را دور بزنه. نکته مهم اینکه فقط Docker Image های رسمی تا نسخه 1.26.2 را تحت تأثیر قرار میدهد و نسخه‌ های Binary یا نصب‌هایی که از تنظیمات پیش‌فرض "app.example.ini" استفاده میکنند، آسیب‌پذیر نیستند. Dork :

7

16 Jul 2026, 10:08 UTC752 views6 reactionsread 7 August 2026
Photo

🚨 Gitea (CVE-2026-20896) cvss : 9.8 📌 این آسیب‌پذیری نسخه‌های رسمی Docker Image مربوط به Gitea تا نسخه 1.26.2 را تحت تأثیر قرار میدهد و در صورت فعال بودن Reverse Proxy Authentication، مهاجم میتواند تنها با ارسال یک HTTP Header، احراز هویت را دور زده و هویت کاربران را جعل کند. ریشه این آسیب‌پذیری به Misconfiguration در Docker Image های رسمی Gitea برمیگردد. پچ در نسخه‌ های 1.26.3 و 1.26.4 منتشر شده به‌طور پیش‌فرض، D

6

16 Jul 2026, 08:33 UTC789 views6 reactionsread 7 August 2026

104 JSON Tests for for Authentication Endpoints 👾 1. Basic credentials { "login": "admin", "password": "admin" } 2. Empty credentials: { "login": "", "password": "" } 3- Null values: { "login": null, "password": null } 4. Credentials as numbers: { "login": 123, "password": 456 } 6. Credentials as booleans: { "login": true, "password": false } 7. Credentials as arrays: { "login": ["admin"], "password": ["password"]

6

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Citation-graph rank

Citation-graph rank — 234,638 of 1,169,250entries 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.

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.

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

“Mandegar SEC🎩” (@mandegar_sec), 3,301 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/mandegar_sec.

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.