Channel
@VulnCity
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
243subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002532568830 |
|---|---|
| Type | Channel |
| Username | @VulnCity |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 29 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 29 August 2026 |
| On Telegram | t.me/VulnCity |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 07:49 | 243 | +2 |
| 14 Aug 2026, 10:09 | 241 | -1 |
| 8 Aug 2026, 09:47 | 242 | no change |
| 7 Aug 2026, 13:48 | 242 | first reading |
20 posts held, back to 3 July 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 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 5 August 2026 |
|---|---|
| Posts held | 20 (3 July 2026 – 5 August 2026) |
| Views total | 71 |
| Reactions total | 2 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 09:47 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.
62 reactions across 19 posts, in 4 distinct kinds. The most used accounts for 48.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 30 | 48.4% | |
| ❤ | 26 | 41.9% | |
| 🔥 | 5 | 8.06% | |
| 🙏 | 1 | 1.61% |
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 19 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 62reactions 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 3 July 2026 to 5 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.
ا Stealer Log چیه ؟ ا Stealer Log خروجی دادهای بدافزارهای Information Stealer است که اطلاعات حساس سیستم قربانی را استخراج میکنند. رایجترین و موثرترین روش آلودگی به Information Stealer، دانلود و اجرای نرمافزارهای کرکشده است. کاربران در جستجوی نرمافزارهای رایگان یا فعالسازهای غیرقانونی، مستقیماً بدافزار را اجرا میکنند. وقتی یک Red Teamer در مرحله Initial Access با موانع امنیتی مواجه میشود — فایروال پیکربندی شد…
👍2
روزانه یه سری چیزایی که میخونم و دم دستی هست رو میزارم توی قسمت Feed چیزای به درد بخوری میزارم توی این بخش، یه جورایی شبیه دفترچه یادداشتمه. شما هم میتونید پست بزارید vulncity.com/feed
👍4
پورت های مربوط به Kuber که توی Recon به دردتون میخوره : 443/TCP kube-apiserver 2379/TCP etcd 6666/TCP etcd 4194/TCP cAdvisor 6443/TCP kube-apiserver 8443/TCP kube-apiserver 8080/TCP kube-apiserver 10250/TCP kubelet full mode access 10255/TCP running kubelet 10256/TCP kube-proxy 9099/TCP calico-felix 6782-4/TCP weave 30000-32767/TCP NodePort 44134/TCP Tiller View Feed 📎 🆔 @vulncity
👍7❤1
🚀 کوبرنتیز فقط یک ابزار Orchestration نیست؛ بلکه زیرساختی پیچیده است که از Control Plane، Worker Nodeها و لایه شبکه تشکیل شده و امنیت هر کدام نقش مستقیمی در امنیت کل کلاستر دارد. اگر این معماری بهدرستی Hardening نشود، همان قابلیتهایی که مدیریت کانتینرها را آسان میکنند، میتوانند به نقاط ورود مهاجمان تبدیل شوند. در این مقاله ابتدا ساختار داخلی Kubernetes را به زبان ساده بررسی کردهایم و سپس از دید یک Red Team به را…
تیر ماه برای VulnCity ماه رشد و توسعه بود؛ با رسیدن به 160 کاربر، انتشار 31 مقاله و اضافه شدن بخشهایی مثل Red Team Path، تالار مشاهیر و Partners. در این ماه VulnDark هم فعال شد و تعداد فیدها به 1,698,320 رسید؛ همچنین Feed و Chat بهبود پیدا کردند. ماه بعد هم با راهاندازی Code Playground و برگزاری یک رویداد آنلاین، مسیر رشد VulnCity ادامه دارد. 🔐 🆔 @vulncity
👍6
🔴ا Persistence در لینوکس | Red Team Series اگه هدفت اینه توی یه لینوکس جا خوش کنی : تو این مقاله ۱۴ تکنیک عملی Persistence رو بررسی کردیم — از ساخت کاربر تا Git Hooks و APT Backdoor. هر تکنیک: ✅ کد اجرایی داره ✅ با MITRE ATT&CK (TA0003) مپ شده ✅ روش Detection برای Blue Team داره 🔗 مقاله کامل رو بخون 🆔 @vulncity
❤2
🔴ا Exchange Server از دید Red Team ا Microsoft Exchange یکی از پرتکرارترین نقاط ورود در حملات واقعیه — چون مستقیم رو به اینترنته، به AD وصله، و سطح حمله چندلایه داره. در این مقاله پوشش دادیم: 🔹 آسیبپذیریهای معروف: ProxyLogon، ProxyShell، ProxyNotShell 🔹 شناسایی سرورها با Shodan و استخراج اطلاعات داخلی از NTLMSSP 🔹 ا Username Harvesting با MailSniper 🔹 ا Password Spray روی OWA، EAS و EWS 🔹 دامپ GAL با exchanger.p…
❤2
اگه تونستید ریپوی زیر رو بالا بیارید. https://github.com/koala73/worldmonitor چیز جالبیه با API های مختلف یه داشبورد کامل پیاده سازی کرده و همچنین با AI اومده بین این اخبار که شامل اخبار سیاسی و اقتصادی و .. میشه ارتباط برقرار میکنه 🆔 @vulncity
❤4
در مورد wp2shell به زودی هم مقاله میزارم توی سایت هم اینکه Exploit هایی که عمومی شده رو میزارم که راحت بتونید استفاده کنید 🆔 @vulncity
❤4
یه سایتی هست به آدرس Onion.run که میتونی لینکهای .onion رو بدون استفاده از Tor باز کنی. کافیه اخر لینک Onion کلمه .run رو اضافه کنی. (ترجیحا با VPN باهاش کار کنید) 🆔 @vulncity
❤4
📛Modern Defense Architecture معماری دفاعی مدرن از فیلتر سادهی مرز شبکه (Firewall) به هفت لایهی بههمپیوسته تکامل یافته؛ هر نسل شکاف دید نسل قبل را پر کرده: AV فایلمحور شد، EDR رفتار In-memory را پوشاند، SIEM لاگها را متمرکز کرد، NDR ترافیک East-West را دید، UEBA بُعد هویت و Baseline رفتاری کاربر را افزود، و XDR همهی این سیگنالها را در یک روایت واحد End-to-End جمع کرد. برای Red Team این یعنی موفقیت دیگر «دور ز…
❤3
🤦🏻♂️ Initial Access By Client Side Attack ا Client-Side Attack در Red Team: با مسدود شدن مسیرهای مستقیم نفوذ، مهاجمان به لایهی کاربر روی میآورند — از LNK Icon Smuggling و WSH Abuse گرفته تا VBA Stomping و HTML/SVG Smuggling، همگی با سوءاستفاده از فرمتهای «کمخطر تلقیشده» و LOLBinهای امضاشدهی ویندوز. بیشتر حملات واقعی زنجیرهایاند (Decoy + Launcher + LNK/Macro در یک ZIP)، نه تکمرحلهای؛ به همین دلیل شناسایی …
❤2
Showing the 12 most recent of 20 posts we hold for @VulnCity. 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 — 431,316 of 1,626,711entries 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.
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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“#! VulnCity” (@VulnCity), 243 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/VulnCity.
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.