Telegram RegisterThe public register of Telegram
Telegram profile photo for EPIPHYTE CORP

Channel

EPIPHYTE CORP

@epiphytecorp

On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry

14subscribers

-1 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-1001576314727
TypeChannel
Username@epiphytecorp
Created7 January 2022 — measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live19 November 2026
Measurements held5
Confirmed unchanged4 times, most recently 19 November 2026
On Telegramt.me/epiphytecorp

Topic

Hacking & security — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 1 October 2026 and assigned it the closest of 31 fixed categories, at 69% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Growth

1416157 August 2026 — 15 subscribers11 August 2026 — 15 subscribers29 August 2026 — 16 subscribers1 October 2026 — 15 subscribers26 October 2026 — 14 subscribers7 August 202626 October 2026
5 measurements spanning 80 days, net -1. 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 14–16 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
26 Oct 2026, 01:1714-1
1 Oct 2026, 02:0015-1
29 Aug 2026, 07:3416+1
11 Aug 2026, 23:3015no change
7 Aug 2026, 04:3615first reading

Engagement

17 posts held, back to 7 January 2022 — 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 page of 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 17 posts for this entry, the most recent from 30 March 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

11 reactions across 4 posts, in 4 distinct kinds. The most used accounts for 54.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍654.5%
❤218.2%
😱218.2%
🔥19.09%

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

Measured over the 17 most recent posts we hold, published 7 January 2022 to 30 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.

Recent posts

30 Mar 2025, 01:47 UTC64 views1 reactionsread 11 August 2026

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Ну что, мои непослушные даркнет хулиганы, мы всё ещё живы и здесь. вериф - как всегда ключом -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEdU4V8dUv6VnURKk3xO9i2LAPEl4FAmfoolAACgkQxO9i2LAP El74RA//dbP/l30rlO89FeUWqxvHi3dcVKMEJr2PknMtj7pTKcHw2SJL0vBY5cK4 sn9FhkIxSmAS4OCcBKu05M+JQ3dx5FrKA2h+OfXACrYMb6JoeRLhv/F++GdkE2QO OzCB1oRXv09t2W7shYaXY0qSUR9swomq2tq/I3UxDKPX9NYGB5ft…

🔥1

Signed you know my name

26 Sept 2023, 06:05 UTC342 views5 reactionsread 11 August 2026

насчёт инвайтов. стучитесь в джаббер, указан на титульной странице форума, и вам ответят.

👍3😱2

Signed you know my name

7 Sept 2023, 22:46 UTC353 viewsread 11 August 2026

у нас тут были мелкие тех. работы связанные как раз с тором, мы их доблестро провели. форум летает.

Signed you know my name

3 Sept 2023, 13:44 UTC373 views4 reactionsread 11 August 2026

Тор выкатил защиту встроенную защиту eqiux от абьюза пропускной способности (DoS) сети на основе PoW, делал её тот же чувак, который сделал PoW алгоритм для XMR с ником Tevador. Её подвезли с версией тора 0.4.8.4. Мы обязательно перейдём на неё, но позже, потому что ни Tails, ни Whonix из коробки не поддерживают пока указанную версию, о чём будет объявлено дополнительно. Почитать за вундервафлю: https://blog.torproje…

👍3❤1

Signed you know my name

3 Sept 2023, 01:51 UTC276 viewsread 11 August 2026

из этой ссылки сделаем шлюз, основной канал сделаем чуть позже.

Signed you know my name

2 Sept 2023, 15:16 UTC270 viewsread 11 August 2026

Из весёлого: угон сайтов на Wordpress через необновлённый Essential Addons for Elementor POC https://github.com/RandomRobbieBF/CVE-2023-32243

Signed you know my name

2 Sept 2023, 15:09 UTC214 viewsread 11 August 2026

трейдерам массово впихивают ратники через уязвимость в винрар. POC https://github.com/b1tg/CVE-2023-38831-winrar-exploit https://www.group-ib.com/blog/cve-2023-38831-winrar-zero-day/

Signed you know my name

2 Sept 2023, 14:45 UTC213 viewsread 11 August 2026

попался мне на глаза сайтик рансомщиков 2+ эшелона. ransomed.vc http://209.141.35.54/ https://179.43.142.108/ что-то выкупы совсем слабенькие, видимо данные того не стоят, хотя корпы по ревенью есть вполне себе нормальные, да и те, судя по кол-ву висящих на сайте, им не платят. вот такой вот слабенький рансом.

Signed you know my name

31 Aug 2023, 15:58 UTC215 viewsread 11 August 2026

https://github.com/3xp0rt/LockBit-Tattoo гыгы

Signed you know my name

28 Aug 2023, 12:00 UTC194 viewsread 11 August 2026

Были тех работы на серваках, сейчас всё ок.

Signed you know my name

10 Aug 2023, 03:41 UTCviews —

EPIPHYTE CORP pinned «хочешь к нам? подписывайся на канал. мы будем время от времени разыгрывать инвайты, аккаунты VPN и аккаунты джаббер. кидать с розыгрышем нет смысла - кому надо и так выдадим аккаунты.»

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

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

“EPIPHYTE CORP” (@epiphytecorp), 14 subscribers as measured 26 October 2026. Telegram Register, tgregister.com/channel/epiphytecorp.

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.