Telegram RegisterThe public register of Telegram

Channel

Укротитель змей

@JFernandezzzz

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

253subscribers

+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-1001950055864
TypeChannel
Username@JFernandezzzz
CreatedBetween 1 April 2023 and 31 October 2023— 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/JFernandezzzz

Growth

2537 Aug 2026, 13:09 — 253 subscribers8 Aug 2026, 09:19 — 253 subscribers7 Aug 2026, 13:098 Aug 2026, 09:19
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 252–254 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 09:19253no change
7 Aug 2026, 13:09253first reading

Engagement

18 posts held, back to 6 August 2024the 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 18 posts for this entry, the most recent from 18 March 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
10
Videos
1
Links
14

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.

Video runtime
35s
Average length
35s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

229 reactions across 17 posts, in 10 distinct kinds. The most used accounts for 32.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥7532.8%
👍5021.8%
❤‍🔥4720.5%
😴219.17%
🆒125.24%
custom 525120341039645895793.93%
👏52.18%
👾52.18%
41.75%
😁10.437%

Custom emoji. One 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 count beside it isTelegram’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 17 of the 18 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 229reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 6 August 2024 to 18 March 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.

Telegram Stars

Stars received
7
across the posts below
Posts paid on
4
of 17 we hold a reading for · 24%
Most on one post
2
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @JFernandezzzz. 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 18 most recent posts we hold for this entry, published 6 August 2024 to 18 March 2025. 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

18 Mar 2025, 16:33 UTC742 views15 reactions2 Starsread 8 August 2026
Forwarded from @P0x3k_1N73LL1G3NC3Video

CVE-2025-24071: NTLM Hash Leak via RAR/ZIP Extraction and .library-ms File When a specially crafted .library-ms file containing an SMB path is compressed within a RAR/ZIP archive and subsequently extracted, Windows Explorer automatically parses the contents of this file due to its built-in indexing and preview mechanism. This behavior occurs because Windows Explorer processes certain file types automatically upon ex

🔥7❤‍🔥3👍3😴1custom 52512034103964589571

6 Mar 2025, 22:28 UTC662 views9 reactions2 Starsread 8 August 2026
Forwarded from @OffensiveTwitterPhoto

😈 [ Mayfly @M4yFly ] New Active Directory Mindmap v2025.03! 🚀 📖 Readable version: 🔗 https://orange-cyberdefense.github.io/ocd-mindmaps/img/mindmap_ad_dark_classic_2025.03.excalidraw.svg 🔧 Now fully generated from markdown files—way easier to update and maintain! 💡 Got improvements? PRs welcome! 👇 🔗 https://github.com/Orange-Cyberdefense/ocd-mindmaps/tree/main/excalimap/mindmap/ad 🐥 [ tweet ]

❤‍🔥4👍2🔥2😴1

3 Mar 2025, 15:41 UTC784 views16 reactions1 Starread 8 August 2026
Photo

Интересный диссер в Wazuh (CVE-2025-24016) Для всех тех, кто тоже недавно подключился в интернет, как я, в Wazuh была обнаружена критическая уязвимость, связанная с десериализацией JSON в API /security/user/authenticate/run_as. Проблема заключается в том, что метод as_wazuh_object в framework/wazuh/core/cluster/common.py обрабатывает пользовательский JSON без фильтрации, позволяя передать мета-поля class и args. Эт

❤‍🔥6🔥4custom 52512034103964589573👍1👾1😴1

28 Jan 2025, 18:30 UTC659 views11 reactionsread 8 August 2026
Photo

Интроспекционный запрос GraphQL, как вытащить всю схему API и что с этим делать Все чаще и чаще замечаю, что в разработке используется технология GraphQL для более гибкого и эффективного взаимодействия между клиентом и сервером. GraphQL позволяет отправлять единый запрос, объединяя несколько данных из разных источников, а также точно указывать, какие поля и типы данных необходимо получить, что оптимизирует загрузку

❤‍🔥4🔥4👍2😴1

12 Dec 2024, 13:01 UTC479 views10 reactionsread 8 August 2026
Forwarded from @haxx_itPhoto

🛠 Как-то незаметно прошел релиз NetExec 1.3.0, а туда тем временем добавили несколько интересных вещей. Вывод инфы по доступным интерфейсам, так что поиск пивота стал гораздо приятнее. nxc smb 192.168.13.37 -u 'USERNAME' -p 'LOLKEKPOHEK' --interfaces Проверка на всякие Coerce штуки (PetitPotam, DFSCoerce, PrinterBug, MSEven, ShadowCoerce). Подробнее тут nxc smb 192.168.13.37 -u 'USERNAME' -p 'LOLKEKPOHEK' -M coerc

🔥3😴2custom 52512034103964589572❤‍🔥1👍1👾1

4 Dec 2024, 08:48 UTC≈1,390 views18 reactions2 Starsread 8 August 2026
Photo

CVE-2024-42327 в Zabbix 1 декабря наткнулся на уязвимость CVE-2024-42327 и решил ее изучить, прочитав пару постов, было сказано, что злоумышленник может внедрять произвольные SQL запросы. Нашел PoC и немного удивился, провел ресерч и ничего общего с SQLi не увидел. Давайте разберемся, о чем же эта бага. CVE-2024-42327 - это крит уязвимость (CVSS 9.9), связанная с JSON-RPC API Zabbix. Она позволяет хакеру с минимальн

🔥10👍3❤‍🔥2😴2👾1

30 Nov 2024, 12:01 UTC411 views15 reactionsread 8 August 2026

Posted without readable text

👍11😴2❤‍🔥1👾1

28 Nov 2024, 16:25 UTC408 views12 reactionsread 8 August 2026

Posted without readable text

🔥4custom 52512034103964589573❤‍🔥2👏2👾1

28 Nov 2024, 16:23 UTC414 views14 reactionsread 8 August 2026

Ну что, привет дорогие, неподкупные читатели моих редко выходящих постов! Да, я немного пропал. За это время накопилось столько мыслей и материалов, посты возвращается с новой силой) И первое, что хочется сказать - огромное спасибо вам всем! Недавно мы перевалили за 200 человек, и для меня это не просто цифра. Это 200 людей, которые разделяют интерес к тому, о чем я пишу. Ваше внимание и поддержка вдохновляют, буду

❤‍🔥8🔥3👏2😴1

16 Oct 2024, 18:03 UTC468 views10 reactionsread 8 August 2026
Forwarded from @RalfHackerChannel

Так, новая техника инъекции в процессы - Early Cascade Injection. Ну и ресерч достаточно подробный) https://www.outflank.nl/blog/2024/10/15/introducing-early-cascade-injection-from-windows-process-creation-to-stealthy-injection/ #redteam #maldev #bypass

👍5❤‍🔥2🔥2😴1

5 Oct 2024, 14:03 UTC576 views11 reactionsread 8 August 2026
Photo

CVE-2024-45519 — уязвимость в сервисе postjournal Zimbra Collaboration Suite, которая позволяет выполнить произвольные команды на сервере. Уязвимость связана с неправильной обработкой входных данных в SMTP-сообщениях. Версии Zimbra, подверженные этой уязвимости, включают все версии до 9.0.0 Patch 41, а также 8.8.15 Patch 46. Баг заключается в том, что функция popen(), использующаяся в версии сервиса, передает пользов

👍5🔥3❤‍🔥2😴1

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

Forward network

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.

“Укротитель змей” (@JFernandezzzz), 253 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/JFernandezzzz.

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.