⚠️ JUST IN: Daniel Xan (formerly @devil on telegram) has been exposed after hosting parties with known rappers to launder stolen crypto A new telegram channel came out of no where and exposed Daniel Xan (formerly @devil), accusing him of stealing millions in crypto to fund a lavish lifestyle. The channel claims a $4.5M theft funded the $1M @devil username, with more evidence coming. @FEEONE PROTECTING THE COM

Channel
FeeOne
@FEEONE
On this record: Topic · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
13,072subscribers
-2,044 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1003848999193 |
|---|---|
| Type | Channel |
| Username | @FEEONE |
| Created | Between 1 February 2026 and 1 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 31 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/FEEONE |
Topic
Hacking & security — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 52% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 19:58 | 13,072 | -67 |
| 15 Sept 2026, 13:41 | 13,139 | -36 |
| 13 Sept 2026, 22:00 | 13,175 | -76 |
| 12 Sept 2026, 04:37 | 13,251 | -130 |
| 9 Sept 2026, 19:56 | 13,381 | -164 |
| 6 Sept 2026, 10:20 | 13,545 | -95 |
| 4 Sept 2026, 01:58 | 13,640 | -56 |
| 2 Sept 2026, 15:34 | 13,696 | -111 |
| 1 Sept 2026, 14:12 | 13,807 | -37 |
| 31 Aug 2026, 16:49 | 13,844 | -32 |
| 30 Aug 2026, 19:34 | 13,876 | -54 |
| 29 Aug 2026, 19:38 | 13,930 | -31 |
| 28 Aug 2026, 18:32 | 13,961 | -14 |
| 27 Aug 2026, 21:54 | 13,975 | -10 |
| 26 Aug 2026, 22:35 | 13,985 | -46 |
| 26 Aug 2026, 00:04 | 14,031 | -49 |
| 24 Aug 2026, 20:55 | 14,080 | -40 |
| 23 Aug 2026, 09:33 | 14,120 | -97 |
| 21 Aug 2026, 18:08 | 14,217 | -81 |
| 20 Aug 2026, 12:13 | 14,298 | first reading |
Engagement
20 posts held, back to 1 June 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 50 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 5.99%
- avg views ÷ 13,072 subscribers
- Avg views / post
- 783
- 2 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 2
- 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.
| Window | Rolling 30 days · latest post in window 24 August 2026 |
|---|---|
| Posts held | 20 (1 June 2026 – 24 August 2026) |
| Views total | 1,565 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Sept 2026, 19: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.
Recent posts
⚠️JUST IN: ZachXBT is launching a site to assist victims ZachXBT confirmed the service will not support victims from Canada, the UK, India, and several other countries due to law enforcement rarely making arrests in these cases. 🌐 : @feeone
⚠️ UPDATE; Apple confirms the removal of telegram. They state that it is now "only available to MacOS users." @feeone ⚠️
⚠️JUST IN: Telegram has been removed from the iOS App Store worldwide. The reason remains unknown, and as of now, neither Telegram nor the App Store has issued an official statement regarding the removal. @feeone 🌎
⚠️ JUST IN: Plush Pepe Lost to Screen-Sharing Scam A Plush Pepe worth $7,000 was sold for just $1 after the owner fell victim to a screen-sharing scam. During a phone call, a scammer convinced the user to enable screen sharing, then viewed a Telegram confirmation code as it was sent to the account. Using the code, the scammer logged in and sold the Pepe to themselves for Stars. Never enable screen sharing with stra…
⚠️JUST IN: Allbridge Core on Solana has been exploited for $1.6M+. The attacker took out a fake loan, successfully swapped $3K USDC for $2.2M USDT, and withdrew the funds immediately after @feeone
⚠️JUST IN: Over $80M was stolen through phishing and exploits throughout June. There were 67 recorded incidents in June, making it the highest monthly number of thefts so far in 2026. @feeone
⚠️JUST IN: A victim lost $700K+ after connecting their wallet to a 1:1 fake Polymarket phishing site. The cloned website was designed to look identical to the real platform, leading the victim to connect their wallet. Shortly after, all funds were drained from their account. @feeone 🥂
⚠️ JUST IN: Famous MEV bot “jaredfromsubway.eth” was drained for $7.5M. The victim was social engineered into signing a bait phishing approval, which compromised their wallet and resulted in $7M+ being stolen. @feeone 🔥
⚠️JUST IN: The FBI just sent a message to crypto fraudsters targeting Americans investors “No more. This FBI will find you, and we will bring you to justice.” @feeone 🚨
⚠️ Just In: Username @gram Has Just Been Transferred to Pavel Durov Pavel Durov has just received the NFT username @gram in his wallet following the rebranding of TON. The wallet that originally acquired the username has been inactive since November 2022, making this its first transaction in over 3 years. The username was originally acquired in November 2022 for 313,000 TON (~$519,580 at the time). @feeone
⚠️ JUST IN: Famous Singer Oliver Tree had been killed by a Helicopter. @feeone 🕊️
Showing the 12 most recent of 20 posts we hold for @FEEONE. 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
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.
Mentions
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.
Handles this channel named that no longer answer
- Dead references
- 2
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 2
- vacant every time we have ever looked
@FEEONE named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 2 posts, 26 August 2026 – 27 August 2026
named in 2 posts, 9 August 2026 – 10 August 2026
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“FeeOne” (@FEEONE), 13,072 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/FEEONE.
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.