Channel
@QuillMonitor
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
223subscribers
-1 since we began measuring on 31 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003067855823 |
|---|---|
| Type | Channel |
| Username | @QuillMonitor |
| Created | Between 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 31 August 2026 |
| Last confirmed live | 31 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 31 August 2026 |
| On Telegram | t.me/QuillMonitor |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 31 Aug 2026, 15:25 | 223 | -1 |
| 31 Aug 2026, 03:34 | 224 | first reading |
20 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 1 page of Telegram’s post history, 20 posts per page.
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. It is computed over the 4 of 13 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 30 August 2026 |
|---|---|
| Posts held | 20 (28 July 2026 – 30 August 2026) |
| Views total | 1,844 |
| Reactions total | 5 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 31 Aug 2026, 03:34 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.
8 reactions across 6 posts, in 2 distinct kinds. The most used accounts for 87.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 7 | 87.5% | |
| 👍 | 1 | 12.5% |
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 6 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 8 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 28 July 2026 to 30 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.
🚨 Hack Alert! Target: TectonicFi What happened: An exploit was detected on Tectonic Finance on the Cronos blockchain involving price manipulation. Approximately $75 million has been moved to three addresses, with transaction details available for further scrutiny. Users are advised not to interact with these addresses until it is confirmed safe to do so. Stay vigilant and monitor the situation closely. 🔗Tweet UR…
❤1
🚨 Hack Alert! Target: avici What happened: 🚨 @avici is currently experiencing an exploit that has resulted in a significant loss of approximately $1.02 million. The alarming report highlights a serious security incident affecting the project, indicating that funds were successfully stolen during this attack. 🔗Tweet URL: View Tweet
❤2
🚨 Hack Alert! Target: CashCowCoin What happened: 🚨 SlowMist TI Alert CashCowCoin suffered a loss of approximately $117.4K due to a flaw in the unverified trading router implementation. The flawed sell() flow allowed an attacker to exploit the system. After executing a swap from CCC to WBNB via PancakeSwap, the proxy incorrectly transferred the entire newly obtained CCC to a dead address. This process resulted in b…
🚨 Hack Alert! Target: MoonwellDeFi What happened: 🚨 An exploit has occurred at the @MoonwellDeFi lending market on Base. The attacker manipulated the collateral price of relatively illiquid MAMO to borrow real cbBTC. Approximately $8.7 million has been aggregated from this exploit. For more details, you can check the provided links. 🔗Tweet URL: View Tweet
🚨 Hack Alert! Target: Arrakis Finance What happened: 🚨 EXPLOIT ALERT | Ethereum The Arrakis V1 / G-UNI ENS–WETH liquidity-manager vault was drained via a Uniswap V3 spot-price manipulation. The root cause was identified as the vault's mint() and burn() valuing its Uniswap V3 position based on the instantaneous pool.slot0() spot price, with NO TWAP or deviation guard on the user deposit/withdraw path. While the vau…
🚨 Hack Alert! Target: termlabs *What happened:* 🚨 A governance attack targeted @termlabs, resulting in a significant loss of approximately $8.5 million. The incident involved a theft of 2,843 ETH and around $1.6 million in DAI, which are currently traceable at the address 0xD5183d8BfC65a50863C62aF2538198A8288FFc13. It serves as a reminder for users to stay vigilant in the face of emerging threats. 🔗Tweet URL: Vie…
🚨 Hack Alert! Target: TheSandboxGame What happened: 🚨 Blockaid has detected an ongoing exploit affecting @TheSandboxGame SAND OFT on Base. Attackers have hijacked LayerZero delegate permissions using the approveAndCall method and have minted unbacked SAND tokens. So far, approximately $49 billion face-value SAND has been minted across more than 400 transactions, and the attack is still ongoing. More details are a…
🚨 Hack Alert! Target: Flashstake V2 What happened: A hack alert was issued regarding Flashstake V2, where a total loss of 0.55 WETH (approximately $886) occurred on August 20, 2026. The hack exploited an economic design flaw within the platform's reward pool structure. The attack leveraged the instant upfront reward mechanism, where the protocol calculated minted FLASH solely based on token deposits, lock duration,…
🚨 Hack Alert! Target: Maya Protocol What happened: A significant exploit has occurred on Maya Protocol, resulting in a loss of approximately $1.7 million. The attacker manipulated the system by inflating the accounting with a false subsidy. This allowed them to add and remove liquidity, ultimately enabling the extraction of around 48.87 million CACAO tokens and 98.82 LINK tokens from shared liquidity. This incident …
❤1
🚨 Hack Alert! Target: ColdCard What happened: The ColdCard wallet incident is currently active, marking it as the largest hardware-wallet exploit recorded, with losses of around $130M and continuing to rise. The exploit involves at least 15 attackers who are taking advantage of a seed-generation bug. Affected seeds can be brute-forced offline without the need for physical access to the devices. For more informatio…
🚨 Hack Alert! Target: harmonyprotocol What happened: An exploit has occurred on Harmony Protocol where billions of $ONE tokens were falsely minted to several addresses. The affected team is taking proactive measures to freeze these funds. Users are advised to stay vigilant to protect against potential losses. 🔗Tweet URL: View Tweet
👍1
🚨 Hack Alert! Target: USM What happened: 🚨 SlowMist TI Alert 💸 Loss: ~70.83 ETH 🔍 Root Cause: A pricing logic flaw in ethFromDefund() of USM's defund() function has been exploited. The function used arithmetic mean of current and estimated final FUM sell prices for single redemptions but lacked "split invariance." This issue, combined with per-redemption state contraction (adjShrinkFactor) and integer rounding, al…
Showing the 12 most recent of 20 posts we hold for @QuillMonitor. 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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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 31 August 2026 — this entry's latest reading, not the date you are reading this.
“QuillMonitor : Web3 Hacks and Alerts” (@QuillMonitor), 223 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/QuillMonitor.
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.