Telegram RegisterThe public register of Telegram
Telegram profile photo for Склад

Channel

Склад

@cyberwarehouse

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

347subscribers

+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-1001845996784
TypeChannel
Username@cyberwarehouse
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live16 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/cyberwarehouse

Growth

3463523497 August 2026 — 346 subscribers8 August 2026 — 346 subscribers8 August 2026 — 347 subscribers23 August 2026 — 348 subscribers31 August 2026 — 352 subscribers9 September 2026 — 348 subscribers16 September 2026 — 347 subscribers3477 August 202616 September 2026
7 measurements spanning 40 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 345–353 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 08:16347-1
9 Sept 2026, 15:17348-4
31 Aug 2026, 13:34352+4
23 Aug 2026, 22:36348+1
8 Aug 2026, 09:01347+1
8 Aug 2026, 06:50346no change
7 Aug 2026, 10:35346first reading

Engagement

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

Reaction mix

20 reactions across 18 posts, in 2 distinct kinds. The most used accounts for 95.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1995.0%
🤯15.00%

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 18 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 20 reactions 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 9 July 2026 to 6 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.

Advertising

Ad load
5.00%
1 of 20 posts carry an ad marker
Regulatory tokens
0
none — marked by hashtag only
Median views · ads
121
over 1 measured post
Median views · rest
76.0
over 19 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.

Measured over the 20 most recent posts we hold, published 9 July 2026 to 6 August 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

6 Aug 2026, 07:15 UTC35 viewsread 8 August 2026
Forwarded from @codeby_secPhoto

POST-параметр → exec() → shell: как одна строка кода превращает админку CMS в точку входа на сервер Представьте: вы администратор CMS, нажимаете кнопку «Обновить ядро», а браузер отправляет POST-запрос с параметром php. Значение этого параметра — путь к PHP-бинарнику — без какой-либо фильтрации конкатенируется в строку и уходит прямиком в exec(). Ни escapeshellarg(), ни allowlist, ни regex. Голый пользовательский вв

4 Aug 2026, 10:38 UTC61 views1 reactionsread 8 August 2026

https://github.com/cleverg0d/bitrix-nuclei-templates

👍1

3 Aug 2026, 17:14 UTC63 views1 reactionsread 8 August 2026
Forwarded from @secure_archivePhoto

🐞 Охотник за эксплойтами - GitHub-репозиторий который автоматически находит PoC для CVE trickest/cve — это репозиторий, который автоматически собирает общедоступные Proof-of-Concept для известных уязвимостей (CVE). Вместо того чтобы вы часами искали рабочий пример эксплойта, он делает это за вас 24/7. Проект создан командой Trickest, которая специализируется на автоматизации и создании кастомных рабочих процессов в

👍1

31 Jul 2026, 04:54 UTC76 views1 reactionsread 8 August 2026

https://github.com/go-gitea/gitea/security/advisories/GHSA-rcr6-4jqh-j84m

👍1

30 Jul 2026, 12:22 UTC80 views1 reactionsread 8 August 2026
Forwarded from @code_m0dePhoto

Windows Forensics Analyst Field Guide Описание: Книга начинается с подробного описания операционных систем Windows и лежащих в их основе криминалистических артефактов, что поможет вам освоить искусство оптимизации процессов расследования. От использования инструментов с открытым исходным кодом для сбора артефактов до углублённого анализа — вы приобретёте навыки, необходимые для успешной работы в качестве опытного с

👍1

29 Jul 2026, 10:04 UTC69 views1 reactionsread 8 August 2026

https://ssd-disclosure.com/vbulletin-runtime-template-runmaths-preauth-rce/

👍1

29 Jul 2026, 07:51 UTC70 views1 reactionsread 8 August 2026
Forwarded from @thehackernewsPhoto

🚨 New Gitea RCE (CVE-2026-60004) lets repository writers plant a malicious Git hook and run shell commands as the Gitea service account. On default-configured instances, outsiders can register, create a repository, and obtain the required write access. A public PoC is available. Find details here: https://thehackernews.com/2026/07/new-gitea-rce-lets-repository-writers.html

👍1

24 Jul 2026, 11:18 UTC106 views1 reactionsread 8 August 2026

https://github.com/jhonnybonny/bitrix-nuclei-templates/

👍1

23 Jul 2026, 06:27 UTC86 views2 reactionsread 8 August 2026
Forwarded from @true_secator

Киберподполье активно задействует критическую CVE-2026-50522 в Microsoft SharePoint для кражи ключей доступа к компьютерам и сохранения доступа даже после установки обновлений на затронутые серверы. Злоумышленник, получив эти токены, способен создать действительные токены аутентификации, чтобы выдать себя за других пользователей и получить доступ к доступным ресурсам, включая сайты и документы SharePoint, с привилег

👍2

22 Jul 2026, 13:57 UTC66 views1 reactionsread 8 August 2026
Forwarded from @haxx_itPhoto

🛠 Всем привет. Я тут допилил CLI-движок для LOLCreds на Go. Называется это безобразие CredsHound. Если коротко, это такая утилита для поиска учетных данных, ключей на хосте, которая работает по концепции Nuclei. Из коробки она ищет: - Пароли и API-ключи, забытые в истории терминалов (.bash_history, .zsh_history, ConsoleHost_history.txt). - Приватные ключи SSH, конфигурации Kubernetes и токены Docker Registry. -

👍1

22 Jul 2026, 08:35 UTC66 views1 reactionsread 8 August 2026
Forwarded from @four_raysPhoto

wp2shell — разбираем от и до. Это цепочка уязвимостей, которая состоит из таких элементов: 📍 CVE-2026-63030 — уязвимость путаницы маршрутизации конечной точки пакетного REST API. CWE-436. 📍 CVE-2026-60137 — уязвимость внедрения SQL-кода (SQL-инъекция). CWE-89. wp2shell позволяет неавторизованному злоумышленнику выполнить произвольный код (RCE) в СMS Wordpress. Затронутые версии: 6.8.0–6.8.5; 6.9.0–6.9.4; 7.0.0– 7.

👍1

21 Jul 2026, 17:58 UTC61 views1 reactionsread 8 August 2026
Forwarded from @ZerodayAlertPhoto

В AnyDesk нашли уязвимость нулевого дня Уязвимость CVE-2026-15682 (5.5 Medium) связана с функцией AnyDesk, которая собирает диагностические данные для службы поддержки. Злоумышленник может использовать точку повторного разбора — специальную ссылку в файловой системе Windows — чтобы перенаправить операции записи файлов в другое место. Для эксплуатации уязвимости сначала нужно получить возможность выполнять код на ус

👍1

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

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

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

“Склад” (@cyberwarehouse), 347 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/cyberwarehouse.

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.