Telegram RegisterThe public register of Telegram

Channel

Системные логи

@sytem10gs

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

190subscribers

+0 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002446048475
TypeChannel
Username@sytem10gs
DescriptionПью пиво, тыкаю вебчик
CreatedBetween 1 September 2024 and 24 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live15 August 2026
Measurements held2
On Telegramt.me/sytem10gs

Growth

1906 Aug 2026, 08:23 — 190 subscribers7 Aug 2026, 07:15 — 190 subscribers6 Aug 2026, 08:237 Aug 2026, 07:15
2 measurements taken within a single 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 189–191 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 07:15190no change
6 Aug 2026, 08:23190first reading

Engagement

15 posts held, back to 24 March 2025the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 15 posts for this entry, the most recent from 24 November 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
25
Videos
3
Links
27

Lifetime counters from Telegram’s own channel header, read 7 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

89 reactions across 15 posts, in 6 distinct kinds. The most used accounts for 38.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 51886123451857051983438.2%
custom 54610555854934702912831.5%
custom 5474177535216459084910.1%
custom 5474597686097223791910.1%
custom 518869368757132403066.74%
custom 518827211935135279233.37%

Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

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 15 of the 15 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 89reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 15 most recent posts we hold, published 24 March 2025 to 24 November 2025, 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

24 Nov 2025, 09:50 UTC333 views4 reactionsread 7 August 2026
Forwarded from @hackthishitPhoto

file://localhost/etc/passwd что вернёт? Да, вернётся /etc/passwd. В RFC 8089, верный формат протокола описан как file://<host>/<path>, в то время как все шпоры на LFR при SSRF говорят лишь о file:///<path> Причём, в <host> возможно вписать домен. Система резолвнет его, и если тот указывает на 127.0.0.1, то вернётся содержимое файла. В противном случае получишь лишь отстук в DNS. питон пок from urllib.request imp

custom 51886123451857051984

5 Nov 2025, 13:06 UTC299 views1 reactionsread 7 August 2026
Forwarded from @hahackingPhoto

📈 #наработки #defense #offense #web #web3 #malware Видели историю про BSidesNYC? Выступила с этой статьёй в Нью-Йорке, в колледже уголовного правосудия имени Джона Джея ⚡️ А тот самый доклад Neplox из Токио и Сеула про уязвимости, обнаруженные в известных криптокошельках — ‟Атакуем криптокошельки: свежий взгляд на безопасность браузерных расширений”, но в Москве, на PHDays, видели? 🤔 ➡Теперь в тексте: собрала и

custom 54745976860972237911

22 Aug 2025, 18:14 UTC432 views4 reactionsread 7 August 2026
Forwarded from @bugbeerFile

File, posted without a caption

custom 51882721193513527923custom 51886123451857051981

22 Aug 2025, 08:47 UTC446 views9 reactionsread 7 August 2026
Photo

Всем ку, хацкеры 👋 На стенде WB (за подписку на канал) выдаем промики на +10.000р к вашему отчету, кто багхантит или хочет багхантить на вб будет приятным бонусом Так же выдаем тестовые учетки ( например Менеджер ПВЗ ) До встречи на стенде! 🌟

custom 51886123451857051984custom 54610555854934702913custom 54741775352164590842

9 Aug 2025, 19:32 UTC335 views5 reactionsread 7 August 2026
Forwarded from @shadow_group_tgPhoto

James Kettle дропнул свой ресерч про новые классы атак через HTTP Request Smuggling и, к моему большому респекту, подкрепил все это доступной лабой на Portswigger. Публичного решения нет, но лаба довольно простая. Теперь можно убивать HTTP/1.1 на реальных целях.

custom 54610555854934702914custom 51886936875713240301

6 Aug 2025, 12:12 UTC369 views6 reactionsread 7 August 2026
Forwarded from @deteact

Уязвимости в Electron-приложениях: RCE через небезопасную конфигурацию В данной статье мы рассмотрим эксплуатацию приложений с отключенными параметрами contextIsolation: false и sandbox: false, что позволило нам выполнить произвольный код на целевой системе. https://blog.deteact.ru/electron-rce/

custom 51886123451857051982custom 54610555854934702912custom 54745976860972237912

23 Jun 2025, 18:03 UTC390 views4 reactionsread 7 August 2026
Forwarded from @deteact

Server-Side XSS → SSRF → Компрометация облачной инфраструктуры: как одна картинка стоила целого облака В этой статье разберем атаку, начавшуюся с уязвимости XSS в генераторе изображений и завершившуюся получением полного доступа к облачной инфраструктуре. https://blog.deteact.ru/serverside-xss-ssrf-cloud-hacking/

custom 54610555854934702913custom 54741775352164590841

21 Jun 2025, 12:37 UTC297 views4 reactionsread 7 August 2026
Forwarded from @wr3dmast3rvsPhoto

Сегодня в лайв-режиме знакомились с анализом кода на примере SSRF в Stirling-PDF (CVE-2025-46568): чтение локальных файлов через WeasyPrint. Не было особо важно, какая CVE. Главное — потренировать анализ кода 🏃‍♂️ Stirling-PDF — это веб-приложение для работы с PDF (конвертация, редактирование). В версиях до 0.45.0 обнаружена SSRF-уязвимость, позволяющая атакующему читать локальные файлы на сервере через обработку HT

custom 54610555854934702912custom 51886123451857051981custom 54745976860972237911

16 Jun 2025, 08:22 UTC276 views6 reactionsread 7 August 2026
Forwarded from @linuxkaliiPhoto

🛡️ Public Pentesting Reports — архив реальных отчётов по взлому Репозиторий на GitHub собирает более 200 публичных отчётов по тестированию на проникновение от компаний и независимых исследователей. 📂 Что внутри: • Взлом web‑приложений, облаков, корпоративной инфраструктуры • Настоящие кейсы от Google, Yahoo, HackerOne, NCC Group и др. • Отчёты в формате PDF, Markdown, блоги и презентации • Отличная база для обучен

custom 54741775352164590844custom 51886123451857051982

6 Jun 2025, 18:25 UTC276 views4 reactionsread 7 August 2026
Forwarded from @cybredPhoto

🔥 9.9 Critical Post Auth RCE для Roundсube Небезопасная десериализация. Инжектится через GET-параметр _from, — в Roundcube он указывает на раздел, куда надо вернуться, после отправки сообщения. ?_task=settings&_action=upload&_from=mail%2Finbox Пошагово, как работает эксплоит: 1. Подменяет _from сериализованным объектом. 2. Заинжекченное значение подтягивается в сессию. 3. Дальше оно обрабатывается через rcube_pgp_e

custom 51886123451857051981custom 54610555854934702911custom 54741775352164590841custom 54745976860972237911

4 Jun 2025, 10:55 UTC437 views6 reactionsread 7 August 2026

У intigriti вышла статья-руководство, по обнаружению скрытых параметров 😒 В данной статье рассматриваются эффективные методы выявления скрытых параметров, а также представлены инструменты с открытым исходным кодом, которые помогут автоматизировать этот процесс Ссылка на статью

custom 54610555854934702913custom 54745976860972237912custom 51886123451857051981

26 May 2025, 07:43 UTC351 views7 reactionsread 7 August 2026
Photo

Как вам phdays? чем занимались эти 3 дня? Я в основном заводил новые знакомства и общался со знакомыми коллегами 🦆 Много кто пишет про то какие доклады им понравились, я бы выделил доклад своего друга, он достаточно содержательный и может помочь решить вам вопросы с автоматизацией и реконом перед тестированием приложения 🤩Источники данных для фаззинга API веб-приложений

custom 51886936875713240305custom 51886123451857051982

Showing the 12 most recent of 15 posts we hold for @sytem10gs. 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 — 508,801 of 1,478,351entries 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

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

“Системные логи” (@sytem10gs), 190 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/sytem10gs.

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.