Telegram RegisterThe public register of Telegram

Channel

Пингискок

@rmrf_0

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

615subscribers

+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-1003738199226
TypeChannel
Username@rmrf_0
DescriptionЗдесь про баги, уязвимости и security-ресерч. Web2, Web3, Bug Bounty https://rmrf.tips https://x.com/pingiskok
Created22 February 2026measured — dated from the channel’s first post
First recorded6 August 2026
Last confirmed live7 August 2026
Measurements held2
On Telegramt.me/rmrf_0

Growth

6156 Aug 2026, 08:26 — 615 subscribers6 Aug 2026, 17:46 — 615 subscribers6 Aug 2026, 08:266 Aug 2026, 17:46
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 614–616 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Aug 2026, 17:46615no change
6 Aug 2026, 08:26615first reading

Engagement

20 posts held, back to 22 February 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.

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 1 May 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
7
Links
9

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

320 reactions across 19 posts, in 12 distinct kinds. The most used accounts for 49.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥15749.1%
4313.4%
😁3210.0%
👍278.44%
😱216.56%
🗿175.31%
82.50%
🆒61.88%
🏆51.56%
👻20.625%
👎10.313%
👏10.313%

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 320reactions 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 22 February 2026 to 1 May 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
1
posts carrying an erid · 1 distinct token
Median views · ads
481
over 1 measured post
Median views · rest
619
over 18 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.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
transferId128 February 202628 February 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 20 most recent posts we hold, published 22 February 2026 to 1 May 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

1 May 2026, 07:27 UTC885 views29 reactionsread 6 August 2026
Photo

Белый хакер: “может, всё-таки responsibly disclose?” Google: давай! memory corruption - 500$, controlled write - 5к$. И мало просто найти баг, так PoC еще должен лечь правильными файлами, без harness/shell scripts/CDP, с идеальной репрой на их стороне. Индустрия сама выдаёт сомневающимся вайтхэтам билет в “enjoy cybercrime”. Естественно вслед за гуглом подтянутся и другие компании. И только на стендофе и бизоне в

😁21😱5👻2🗿1

13 Apr 2026, 10:41 UTC≈1,250 views13 reactionsread 6 August 2026

DeFi-протоколы не взламывают. Они просто не закрыты. Омар рассказал кейс про то как их AI-агент задетектил эксплойт DeFi-протокола в реальном времени. Пока алерт горел, фаундер протокола 30-60 минут пытался разбудить своего CTO. За это время деньги были почти полностью украдены. Масштаб в целом таков: - Wormhole не проверяли подписи валидаторов и $326M ушли в один вызов - В Ronin Bridge взлом заметили только через

👍12🗿1

8 Apr 2026, 07:18 UTC≈1,280 views17 reactionsread 6 August 2026
Photo

Claude Mythos.. .. еще не выпущен, но опубликовали исследование про него: https://red.anthropic.com/2026/mythos-preview/ Я ещё сам не дочитал, но вот несколько мыслей по тому, что успел прочесть. Антропики говорят, что целенаправленно не обучали модель что-то ломать и это просто вылезло само потому что модель стала умнее по всем направлениям. И вот это, кажется, загоняет их в угол. Нельзя выпилить эти навыки, не с

😱6😁54👍1🗿1

6 Apr 2026, 09:06 UTC≈1,060 views29 reactionsread 6 August 2026

Как КНДР полгода играла в квант-фонд и вынесла $285M из Drift Drift - крупнейший перпетуальный DEX на Solana. 1 апреля 2026 протокол потерял ~$285M. Не из-за бага в смарт-контракте. Осень 2025. На конференции к команде Drift подходят ребята из "квантового трейдингового фонда". Технически грамотные, проверяемые биографии. Встречи вживую в нескольких странах, переписка в Telegram, рабочие сессии. В декабре-январе вно

🔥13😱8🏆5👎1🗿1🆒1

3 Apr 2026, 18:35 UTC991 views43 reactionsread 6 August 2026
Photo

Мое лицо когда закрыл серию статей (думайте, какое именно лицо мое) Закрыл, да не полностью. 15 и 16 частей нет. Не знаю будут ли. Подробнее написал в 17-й. Захардкоженные секреты, альтернативы JWT, RFC 8725 и постквантовая криптография: 17. Hardcoded secrets - CVE-2025-20188 (CVSS 10.0), 17% JWT CVE за 2024-2026, где искать секреты 18. Что вместо JWT - PASETO, Macaroons, opaque tokens, server-side sessions 19. RF

🔥24👍87😁3🗿1

28 Mar 2026, 08:20 UTC≈1,880 views37 reactionsread 6 August 2026
Photo

Продолжение серии про JWT - шесть новых статей Криптография, шифрование, библиотеки, OAuth/OIDC, XSS и продвинутые криптоатаки: 9. Криптография JWT для хакеров - ECDSA, RSA-PSS, EdDSA и где ломается математика 10. JWE — зашифрованные токены, Bleichenbacher, Invalid Curve, PBES2 DoS 11. JWT-библиотеки — рейтинг дырявости, Top 5 CVE, fingerprinting по токену 12. JWT в OAuth 2.0 и OIDC — token confusion, cross-service

🔥239👍4🗿1

21 Mar 2026, 17:13 UTC≈3,520 views24 reactionsread 6 August 2026
Photo

Опубликовал новые статьи из серии статей про JWT Не пугайтесь графика на скриншоте - он просто для наглядности того почему именно работает уязвимость От структуры токена до атак с PoC: 1. Почему JWT сломан by design 2. Анатомия токена 3. alg:none - одна строчка и ты admin 4. Algorithm Confusion - публичный ключ как пароль 5. kid injection - SQLi через заголовок токена 6. jku/x5u/jwk/x5c - весь заголовок это attack

🔥173😱21🗿1

20 Mar 2026, 18:23 UTC≈2,110 views12 reactionsread 6 August 2026
Photo

Так, начинаю серию статей про JWT Это будет настолько глубоко, насколько хватило моих мозгов разобраться. Каждая статья чуть больше чем пост в телеграме, поэтому выходить они будут на отдельном ресурсе. В канал тоже буду постить что-то интересное. Первые статьи уже тут: rmrf.tips

🔥101🗿1

13 Mar 2026, 21:50 UTC933 views11 reactionsread 6 August 2026

Обфускация на стероидах: Как base64+reverse в JS бандле "защищает" 24 секрета DeFi протокола Пишу пока что про Web3, потому что там сейчас примерно так же как в Web2 было в 2015-м. Web3-проекты усвоили (не все), что хранить API-ключи в REACT_APP_ переменных плохо - их видно в бандле через Ctrl+F. Решение? Обфускация. Но не нормальная серверная архитектура, а base64(reverse(key)) прямо в клиентском JavaScript. Securi

🔥81🗿1🆒1

2 Mar 2026, 22:16 UTC619 views11 reactionsread 6 August 2026
Video

MEV за чужой счет: Как публичные RPC-ключи превращают юзеров в сэндвичи Web3-проекты любят хардкодить RPC-ключи в фронтенд. Разработчики думают: «Мы просто читаем балансы из блокчейна, кому нужен наш ключ?». На деле они дарят MEV-ботам и снайперам идеальный, а главное - бесплатный инструмент для фронтраннинга своих же пользователей. Вектор атаки: Мемпул как на ладони Открываем рандомный DEX. В минифицированном JS

🔥711👍1🗿1

28 Feb 2026, 19:16 UTC481 views10 reactionsread 6 August 2026
Advertisementerid transferId

GraphQL Injection через строковую интерполяцию Проект - bridge для перевода токенов между L1 и L2. Фронтенд обращается к The Graph для чтения данных о трансферах. Исходный код нашли через source maps, оставленные в production (2159 файлов). Что в коде Файл queries.ts содержал функции с прямой подстановкой пользовательского ввода в тело GraphQL-запроса через template literals: const query = ` { transferSents

🔥71👍1🗿1

27 Feb 2026, 14:04 UTC563 views10 reactionsread 6 August 2026
Photo

CERTIK это конечно очень важно и нужно. А что с вебом делать то будем? Как ДОЛЖНА работать Web3 аутентификация Нормальный flow аутентификации через кошелёк: 1. Клиент серверу: "Хочу войти, мой адрес 0xАБВ" 2. Сервер клиенту: "Подпиши этот уникальный nonce: a7f3b2..." 3. Клиент подписывает nonce приватным ключом в MetaMask 4. Клиент серверу: "Вот подпись: 0x8e3f..." 5. Сервер проверяет подпись через ecrecover - сов

🔥621🗿1

Showing the 12 most recent of 20 posts we hold for @rmrf_0. 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 — 242,608 of 1,345,403entries 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 3 registered channels — 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.

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

“Пингискок” (@rmrf_0), 615 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/rmrf_0.

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.