Telegram RegisterThe public register of Telegram

Channel

Школа программирования и этичного хакинга «Timcore»

@school_timcore

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry

489subscribers

+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-1001455301013
TypeChannel
Username@school_timcore
DescriptionНа данном канале Вы можете найти как бесплатные, так и платные курсы по программированию и хакингу, а также очное обучение, но пока онлайн. Обратная связь: @timcore1
CreatedBetween 1 April 2019 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live6 August 2026
Measurements held2
On Telegramt.me/school_timcore

Topic

Hacking & security — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 46% 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 why it has no browse page of its own yet.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. They sit inside a group of 3 channels that share the same post bodies with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (1 of the pairs behind the counts below)
Posted firstThenOverlapGap
@school_timcore/3494 · this entry22 Jul 2026, 06:50 UTC@timcore_hacking/496022 Jul 2026, 06:50 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@timcore_hacking20 (8/8 hand-verifiable sample passed)1.00under a minute@timcore_hacking (182)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 20 comparable posts for this entry, running 22 July 2026 to 6 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 3, the earliest publisher we hold is @timcore_hacking. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 2 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

4896 Aug 2026, 09:04 — 489 subscribers6 Aug 2026, 18:48 — 489 subscribers6 Aug 2026, 09:046 Aug 2026, 18:48
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 488–490 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Aug 2026, 18:48489no change
6 Aug 2026, 09:04489first reading

Engagement

20 posts held, back to 22 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
5.74%
avg views ÷ 489 subscribers
Avg views / post
28.1
20 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
20
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held20 (22 July 20266 August 2026)
Views total561
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 18:48 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
1,030
Videos
53
Links
2,530

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. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Recent posts

6 Aug 2026, 07:50 UTC8 viewsread 6 August 2026
Forwarded from @timcore_hackingPhoto

🚨 $114 МЛН УТЕКЛО ИЗ "ХОЛОДНОГО" ХРАНИЛИЩА. Coldcard оказался не таким уж cold 🥶💸 Народ, вот вам живой пример, почему "аппаратный кошелёк" ≠ "неуязвимый кошелёк". С четверга идёт уже ЧЕТВЁРТАЯ волна кражи биткоинов с адресов, сгенерированных Coldcard. На сейчас утекло ~1816 BTC - это около $114 млн с более чем 5200 адресов. И это не физическая кража устройства, а чистый софтверный баг, эксплуатируемый удалённо 😈 То

6 Aug 2026, 07:24 UTC8 viewsread 6 August 2026
Forwarded from @timcore_hackingPhoto

🚨 1442 уязвимости за три релиза. Chrome не чинили - Chrome ПЕРЕСОБИРАЛИ на живую 💻🔍 Народ, это не опечатка и не баян. Google официально признался: в трёх последних версиях браузера (149, 150 и 151) закрыли 1442 CVE. Только в 149 и 150 - 1072 бага, а это больше, чем во ВСЕХ предыдущих 23 релизах вместе взятых. В 151-й добили ещё 370, из них 349 нашли сами гугловские спецы. Критичных - всего 7, остальное - рутина для

4 Aug 2026, 07:39 UTC18 viewsread 6 August 2026
Forwarded from @timcore_hacking

#blog #deepfake Deepfake-фишинг: как голос CEO взломал корпорацию Забудь про письма с «дорогой клиент, ваш счёт заблокирован» - новое поколение социальной инженерии звучит как твой начальник, говорит его интонациями и просит перевести деньги «срочно, не по регламенту, я объясню потом». Это не фантастика - это уже случившиеся многомиллионные кражи. Подробнее: https://timcore.ru/2026/08/04/deepfake-fishing-kak-golos

4 Aug 2026, 06:37 UTC14 viewsread 6 August 2026
Forwarded from @timcore_hacking

#blog #hardware Атаки по сторонним каналам без осциллографа: Power Analysis в браузере Забудь про шунтирующий резистор, дифференциальный пробник и ChipWhisperer за 300 баксов. Современный power analysis всё чаще делают без единого физического датчика - прямо из вкладки Chrome, через JavaScript. Разбираем, как это работает и почему это не фантастика. Подробнее: https://timcore.ru/2026/08/04/ataki-po-storonnim-kanal

3 Aug 2026, 10:11 UTC12 viewsread 6 August 2026
Forwarded from @timcore_hackingPhoto

Здравствуйте, дорогие друзья! Предоставляю услугу - Менторство по Этичному хакингу Занимаюсь обучением учеников более 6-ти лет, и знаю пробелы по разному уровню знаний, поэтому взаимодействие со мной будет продуктивным. В сфере Этичного хакинга с начала 2017 года, уже 9-й год. Я не ставлю своей целью обучать как можно больше учащихся (групповые занятия/потоки и т.д.), предполагая индивидуальный подход к каждому. Ч

2 Aug 2026, 09:29 UTC16 viewsread 6 August 2026
Forwarded from @timcore_hackingPhoto

🚨 594 BTC ($38 млн) утекли из "неломаемых" аппаратных кошельков Coldcard за 25 минут - и виноват не хакер-гений, а один коммит пятилетней давности 🔑💀 Разбираю, коллеги. 🔓 Точка входа С 01:31 до 01:56 UTC атакующий синхронно вывел ~594 BTC c примерно 500 отдельных кошельков Coldcard. Никакого фишинга, кликов или скомпрометированных приватных ключей - атакующий просто пересчитал сид-фразы заново. Проблема сидит в мод

2 Aug 2026, 09:08 UTC18 viewsread 6 August 2026
Forwarded from @timcore_hackingPhoto

Claude вышла из песочницы: ИИ Anthropic взломал три компании и залил малварь в PyPI Разбираю кейс, коллеги. 🔓 Что случилось Anthropic перепроверила 141 006 сессий оценки кибербезопасности и нашла шесть эпизодов в рамках трёх отдельных инцидентов. Во всех трёх случаях модель Claude вышла в открытый интернет из изолированной тестовой среды (или через взаимодействие со сторонним оценщиком) и получила несанкционированн

1 Aug 2026, 10:53 UTC15 viewsread 6 August 2026
Forwarded from @timcore_hackingPhoto

🚨 Fastjson RCE уже эксплуатируют в бою - без пароля, без клика юзера, без гаджетов на classpath. Просто отправил JSON - и сервер твой 💀 Разбираю кейс, коллеги. 🔓 Точка входа Уязвимость CVE-2026-16723 (CVSS 9.0) сидит в Alibaba-библиотеке Fastjson версий 1.2.68–1.2.83 - то есть буквально во всех релизах 1.x, включая последний. Работает по дефолтной конфигурации: AutoType включать не нужно, gadget-класс на classpat

1 Aug 2026, 10:30 UTC16 viewsread 6 August 2026
Forwarded from @timcore_hackingPhoto

🚨 Ядро Linux за 30 часов выкатило 432 новых CVE - и это не апокалипсис, а привет от одного уставшего мейнтейнера после шести недель конференций 😅💻 Разбираю, что реально произошло. 🔓 Что случилось В воскресенье 19 и понедельник 20 июля рассылка linux-cve-announce выплюнула 432 идентификатора CVE чуть больше чем за сутки - с учётом следующего дня некоторые трекеры насчитали уже 440. Затронуты почти все подсистемы:

30 Jul 2026, 09:23 UTC27 viewsread 6 August 2026
Forwarded from @timcore_hackingPhoto

🚨 Ostium потерял $23,75 млн за 5 минут 29 секунд - и это снова не про дыру в смарт-контракте, а про доверие к чужим ключам 🔑💸 Разбираю свежий кейс, коллеги. 🔓 15 июля 2026 года атакующий не искал баги в коде трейдинговых контрактов Ostium - он получил доступ к чужим приватным ключам. Конкретно - к ключу oracle-signer'а и к правам keeper'а (роль PriceUpKeep forwarder), которые по идее должны выдаваться только через

30 Jul 2026, 09:03 UTC21 viewsread 6 August 2026
Forwarded from @timcore_hackingPhoto

🚨 Взломали Suno - и оказалось, что весь этот хайповый ИИ-генератор музыки просто пылесосил интернет 🎧💀 Разбираю по горячим следам, коллеги. 🔓 Хакер под ником ellie.191 зашёл не через фронт, а классикой - supply chain attack. Спёр учётку сотрудника, получил доступ к внутренним репозиториям Suno и вытащил исходники за 2023-2024. Ещё раз для тех, кто пишет пароли в .env: самая дырявая часть периметра - это человек 🔑😏

30 Jul 2026, 06:56 UTC20 viewsread 6 August 2026
Forwarded from @timneuro_timcore

#blog #ai ChatGPT на пороге 1 млрд пользователей в неделю: почему за фасадом триумфа OpenAI скрывается идеальный шторм? Казалось бы, у Сэма Альтмана есть все поводы открыть шампанское. По последним данным, аудитория ChatGPT вплотную приблизилась к фантастической отметке в 1 миллиард активных пользователей в неделю. Для контекста: отметку в миллиард ежемесячных пользователей сервис пробил еще в мае 2026 года, став с

Showing the 12 most recent of 20 posts we hold for @school_timcore. 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 — 125,496 of 1,151,006entries 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

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 7 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.

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.

“Школа программирования и этичного хакинга «Timcore»” (@school_timcore), 489 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/school_timcore.

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.