Channel
@defimon_alerts
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
4,633subscribers
+173 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002360854548 |
|---|---|
| Type | Channel |
| Username | @defimon_alerts |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/defimon_alerts |
Crypto & trading — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 87% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 13:59 | 4,633 | +22 |
| 11 Sept 2026, 21:16 | 4,611 | +6 |
| 7 Sept 2026, 15:35 | 4,605 | +34 |
| 2 Sept 2026, 10:26 | 4,571 | +20 |
| 30 Aug 2026, 14:24 | 4,551 | +21 |
| 27 Aug 2026, 13:54 | 4,530 | +11 |
| 24 Aug 2026, 10:28 | 4,519 | +9 |
| 20 Aug 2026, 19:05 | 4,510 | +17 |
| 17 Aug 2026, 11:34 | 4,493 | -1 |
| 14 Aug 2026, 02:05 | 4,494 | +12 |
| 10 Aug 2026, 17:21 | 4,482 | +20 |
| 7 Aug 2026, 15:52 | 4,462 | +2 |
| 6 Aug 2026, 17:30 | 4,460 | no change |
| 6 Aug 2026, 17:19 | 4,460 | first reading |
23 posts held, back to 28 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 6 pages 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 23 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
37 reactions across 13 posts, in 4 distinct kinds. The most used accounts for 37.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 14 | 37.8% | |
| 😁 | 13 | 35.1% | |
| 🤣 | 9 | 24.3% | |
| 👎 | 1 | 2.70% |
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 15 of the 23 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 37 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 23 most recent posts we hold, published 28 July 2026 to 8 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.
🚨 atomic.green - Loss ~$29,984 (2026-08-07) Network: Arbitrum Type: Flash Loan / Price Oracle Manipulation Atomic (non-custodial leveraged trading + isolated "AtomicLending" on Arbitrum) was drained via a flash-loan price manipulation. A fresh EOA (nonce 1) called an exploit contract that took an Aave V3 ARB flash loan, then manipulated the Uniswap V3 ARB/USDC.e pool (0xcda53b...dad8) used to value the protocol's …
❤1
Yesterday we reported a governance attack to PantherProtocol.io which drained 5.12M $ZKP. Attacker submitted a governance proposal named "zkp-reexploit" to upgrade each ZKP proxy to the drainer impl. Then they posted a "yes" answer with the 0.5 ETH bond. No honest party counter-bonded a "no" within the 12h timeout + 8h cooldown. The answer finalized and the module dutifully executed the drain. We do our best and al…
❤1
🚨 Arbitrary Call Injection in Unistreet.org on Ethereum - Loss ~$17750 LaunchpadFactoryAuto's launch() forwards attacker-supplied initCalldata/modifyCalldata verbatim into PositionManager.multicall() with the factory as msg.sender and no validation. The factory custodies every launch's Uniswap V4 LP position NFT, so the attacker passed modifyCalldata = setApprovalForAll(exploitContract, true), making the factory gra…
❤4
💌 Onchain message: Hello Whitehat, We've seen that you've exploited an vulnerability in us and rescued the user funds from us. We are looking forward you to send back us the funds for little bounty amount as reward. We've texted you on blockscan with the same address. Please reach out. We are looking to hear from you. 📤 From: 0x753d36150672065ce0025b64cda62be439dabe0d 📥 To: 0x2352a1fca90182509dca9c12b2cad582a38e8b…
❤1
💌 Onchain message: Hi, I am the victim of the phishing attack (wallet: 0x3a5385D8eB0d05B006edFF978BA4b95c51F70B5c). You stole approximately 500,000 USDC from me on Base. Attack transaction: 0xd2324b49161b53218651eae2852f8684fa68015cfcada94e5c0ad14030fc62ba I have identified relevant information and collected on-chain and device-related evidence. A police report has already been filed, and the legal authorities are …
😁3
💌 Onchain message: Hi, I am an ordinary DeFi user. Earlier today, one of my wallets was phished and suffered a loss of approximately 500,000 USDC on Base. Attack transaction:0xd2324b49161b53218651eae2852f8684fa68015cfcada94e5c0ad14030fc62ba The attacker swapped all the stolen USDC for only about 67 WETH (resulting in a loss of roughly 370,000 USDC) on a Uniswap V4 WETH/USDC pool due to the absence of slippage prote…
🚨 Governance Takeover of Strongblock.com - Loss $72K Token: $STRONG Network: Ethereum The attacker exploited StrongBlock's abandoned on-chain Governor. Holding a majority of the now near-worthless STRONG vote token, they pushed a proposal calling setPendingAdmin(attacker) on the Governor's Upgrader, voted it through, queued and executed it - seizing admin control of the Governor proxy. They then upgraded the proxy…
❤3
🚨 Nereus Finance (Shapeshifters Market) - Loss $23.76K (2026-08-04) Network: Ethereum Type: Private Key Compromise (malicious proxy upgrade) The NereusShapeshiftersMarket NFT marketplace (TransparentUpgradeableProxy 0x6de0…6d73) was drained via a malicious implementation upgrade. The proxy's admin key (0x863b…4076, an EIP-7702-delegated EOA holding ProxyAdmin ownership) was used to call ProxyAdmin.upgradeAndCall, …
🚨 NEX (on PancakeSwap) - Loss ~$19K (2026-08-03) Token: $NEX Network: BNB Chain Type: Logic Error (double-spend in token _transfer) The NEX token's _transfer has a fall-through bug: the router branch calls super._transfer(from,to,amount) and then execution continues to a second unconditional super._transfer(from,to,amount), so any transfer to/from the PancakeSwap router moves tokens TWICE. The attacker flash-borro…
🚨 LpdFi - Loss ~$690K (2026-08-02) Token: $LPD Network: BNB Chain Type: Oracle / Price Manipulation (flash-loan) LpdFi's Lpd.price() derives the LPD price straight from the spot reserves of the PancakeSwap LPD/USDC pair, with no TWAP or manipulation guard. The attacker flash-borrowed USDC, skewed the pair reserves (donate + sync), which let an order's uAmount value the "interest" far above what its LPD collateral …
❤1
💌 Onchain message: This wallet drained funds on Jul 21, 2026 via a phishing site and its activity is being tracked by blockchain forensics firms and has been reported to FBI IC3, Chainalysis, and every major exchange compliance team. Any attempt to move, swap, or cash out these funds will be flagged and frozen at the exchange or bridge level. You have 48 hours to return 80% of the funds to this address. Keep 20% and…
🚨 Private MEV/Arb Bot (0xa317…c170) - Loss ~$31.7K (2026-07-30) Token: $WETH @ $1904.74 Network: Base Type: Access Control (unprotected arbitrary-call function) A Uniswap V3 arbitrage bot (deployed & owned by EOA 0x3862…3f53) exposes function 0x42be3129 with NO access control — it executes a caller-supplied target+calldata and forwards the output to msg.sender. Only 0x23a69e75 is onlyOwner-gated. The attacker depl…
😁10
Showing the 12 most recent of 23 posts we hold for @defimon_alerts. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 3 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.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“Defimon Alerts” (@defimon_alerts), 4,633 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/defimon_alerts.
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.