Channel
@DBleak
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
1,595subscribers
+21 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001386860979 |
|---|---|
| Type | Channel |
| Username | @DBleak |
| Created | Between 1 March 2018 and 25 April 2020— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 27 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 27 August 2026 |
| On Telegram | t.me/DBleak |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Aug 2026, 10:43 | 1,595 | +7 |
| 24 Aug 2026, 08:28 | 1,588 | +6 |
| 20 Aug 2026, 18:37 | 1,582 | +3 |
| 17 Aug 2026, 23:02 | 1,579 | +1 |
| 14 Aug 2026, 20:38 | 1,578 | -2 |
| 11 Aug 2026, 21:33 | 1,580 | +5 |
| 9 Aug 2026, 07:52 | 1,575 | +1 |
| 6 Aug 2026, 12:33 | 1,574 | no change |
| 6 Aug 2026, 12:22 | 1,574 | first reading |
20 posts held, back to 25 April 2020 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof 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 18 February 2023. An engagement rate over an empty window would be a number about nothing.
The owner of this channel has been inactive for the last 11 months. If they remain inactive for the next 18 days, they may lose their account and admin rights in this channel. The channel will remain accessible for all users.
Selling 20K Yahoo Valids DM with price @JOD_Cracker
Fortune favours the breached: Crypto.com admits 400 users hit in hack https://www.zdnet.com/article/fortune-favours-the-breached-crypto-com-admits-400-users-hit-in-hack/#ftag=RSSbaffb68
Need a Developer for Project.. Budget - 2K $ Must have experience in building webapps.. should be familiar with techstacks HMU @JOD_Cracker
Selling private founds of Bigbasket Database Lines - 3.8 M (Untouched) These are new founds .. apart from the lines that are publicly available. Price - 1500$ Selling only one copy HMU @AccountReaper_bot
For those wondering, what this is Read up : https://www.google.com/amp/s/gadgets.ndtv.com/internet/news/aditya-birla-fashion-retail-abfrl-data-leak-hack-user-employee-details-mail-id-passwords-credit-card-shinyhunters-2709519/amp
DEHASH VERSION (200K)
DBLeaks pinned «For More Serious People Who Want to buy my Private DBs/want to work with me...!! Follow these blogs for latest info on Data Breaches and Cyber Security... 1) blog.akamai.com 2) nakedsecurity.sophos.com 3) itsecurityguru.org 4) krebsonsecurity.com Usually…»
Rapidbox.in 30M Link - https://gofile.io/d/fI6WEM Don't know what's in there .. don't care as well
1m DB Indian Dump date - 1st Jan EP, UP and NP Price - 200$ 100% Private.. DM @AccountReaper_bot Edit - Sold
Back to Work! ⏭️
Sticker, posted without a caption
Showing the 12 most recent of 20 posts we hold for @DBleak. 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.
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.
@DBleak named 1 handle 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.
References a handle that is not a live channel — we have no record it ever was one.
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 27 August 2026 — this entry's latest reading, not the date you are reading this.
“DBLeaks” (@DBleak), 1,595 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/DBleak.
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.