Channel
@cryptooffensive
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,209subscribers
-6 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001175038100 |
|---|---|
| Type | Channel |
| Username | @cryptooffensive |
| Created | 11 September 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 7 August 2026 |
| Last confirmed live | 26 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 26 August 2026 |
| On Telegram | t.me/cryptooffensive |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Aug 2026, 08:11 | 1,209 | -1 |
| 22 Aug 2026, 23:57 | 1,210 | -2 |
| 19 Aug 2026, 07:46 | 1,212 | -2 |
| 16 Aug 2026, 15:12 | 1,214 | +1 |
| 13 Aug 2026, 06:55 | 1,213 | +1 |
| 9 Aug 2026, 23:37 | 1,212 | -3 |
| 7 Aug 2026, 03:52 | 1,215 | no change |
| 7 Aug 2026, 02:00 | 1,215 | first reading |
20 posts held, back to 29 December 2021 — 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 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 6 August 2022. An engagement rate over an empty window would be a number about nothing.
28 reactions across 7 posts, in 3 distinct kinds. The most used accounts for 67.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 19 | 67.9% | |
| ❤ | 5 | 17.9% | |
| 🔥 | 4 | 14.3% |
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 7 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 28reactions 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 29 December 2021 to 6 August 2022, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
#hack #GenomesDAO Взломан GenomesDAO - https://genomes.io/ - DAO сервиса монетизации генетических данных в сети Polygon. Сумма ущерба - около 25.5 ETH (использовался Wrapped ETH на Polygon). Уязвимость нашлась в контракте стейкинга LP-токенов (токенов поставщиков ликвидности). Функция инициализации "initialize" вызывала функцию "initialized", которая оказалась публичной и позволила взломщику подменить адрес токена…
👍14🔥3
#hack #fegtoken И ещё пара разборов того же инцидента: https://twitter.com/IvoElenchev/status/1526116700810362881 https://twitter.com/electricd1ckdev/status/1525965414878134278
👍1
https://twitter.com/smartstatetech/status/1526610831986683904?s=21 - разбор
❤5
#hack #fegtoken Взломаны смарт-контракты экосистемы FEG (FegToken) - https://fegtoken.com/ - в сетях Ethereum и BNB (BSC). Ущерб: 143 ETH ($305 тыс.) + 3277 BNB ($1 млн.) Контракты взломщика: ETH - https://etherscan.io/address/0x9a843bb125a3c03f496cb44653741f2cef82f445 BNB - https://bscscan.com/address/0x9a843bb125a3c03f496cb44653741f2cef82f445 Подробности взлома выясняются.
👍1
#hack #saddle #fuse Два крупных взлома за день: 1) Saddle Finance взломан на $10 миллионов: https://etherscan.io/tx/0x2b023d65485c4bb68d781960c2196588d03b871dc9eb1c054f596b7ca6f7da56 Также $3.8 миллиона были спасены белыми хакерами из BlockSecTeam: https://etherscan.io/tx/0x9549c0cb48ec5a5a2c4703cbbbbea5638028b2d8c8adc103220ef1c7fe5e99a3 2) $80 миллионов выведено из пулов Fuse в протоколе Fei, который в декабре 2…
#hack #deusdao #defi Взломан сервис DeFi-деривативов DeusDao. Атака осуществлена в сети Fantom путем манипуляции значениями от ценового оракула, с использованием flash-займа. Выгода для взломщика оценивается в $13.4 миллиона. Краткий разбор от PeckShield: https://twitter.com/peckshield/status/1519530463337250817
#AkuDreams #vulnerability #lostfunds Более 11500 ETH (около $ 35 миллионов) оказались навсегда заблокироваными на смарт-контракте AkuAuction проекта AkuDreams. https://etherscan.io/address/0xf42c318dbfbaab0eee040279c6a2588fa01a961d Драматичная история развернулась в несколько этапов. Вначале команда проекта была оповещена о том, что возврат избыточных сумм ставок аукциона может быть заблокирован совершением ставк…
👍2
#hack #TecraCoin #TCR Взлом на 640 тысяч долларов из-за порядка параметров, пострадали поставщики ликвидности на Uniswap. Разработчики токена TecraCoin (TCR) ошиблись с порядком параметров _allowances в burnFrom(). В результате - кто угодно мог сжечь токены с любого адреса, предварительно разрешив этому адресу трату своих токенов. Действия контракта, использованного при атаке: * приобрести TCR на небольшую сумму *…
#hack Взломан мост Wormhole между Ethereum и Solana, ущерб $321M. Кто-то сминтил себе 120К врапнутых ETH: https://solscan.io/tx/2zCz2GgSoSS68eNJENWrYB48dMM1zmH8SZkgYneVDv2G4gRsVfwu5rNXtK5BKFxn7fSqX9BvrBc1rdPAeBEcD6Es Взломщику удалось убедить мост со стороны Solana, что он залил 120К эфира на другой конец моста. Для доказательства используются подписи релееров, но программа для верификации подписей передается в вид…
🔥1
#hack #crosswise DeFi-сервис Crosswise - crosswise.finance - взломан из-за публичной доступности функции контракта, через которую можно было открыть себе доступ к совершению действий от имени других адресов. Ущерб оценивается в $879 000. https://twitter.com/peckshield/status/1483340900398895105
👍1
#vulnerability #anyswap #multichain #approve Пользователям сервиса AnySwap - anyswap.exchange, также известного под новым названием Multichain - multichain.org, во избежание финансовых потерь необходимо отозвать аппрувы (разрешения) на токены WETH, PERI, OMT, WBNB, MATIC, AVAX. https://medium.com/multichainorg/action-required-critical-vulnerability-for-six-tokens-6b3cbd22bfc0
#guide Еще один перечень типов уязвимостей в смарт-контрактах Solidity с описанием и примерами https://github.com/sigp/solidity-security-blog
Showing the 12 most recent of 20 posts we hold for @cryptooffensive. 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 — 506,236 of 1,604,598entries 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 1 registered channel — 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“Crypto Offensive” (@cryptooffensive), 1,209 subscribers as measured 26 August 2026. Telegram Register, tgregister.com/channel/cryptooffensive.
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.