/* This CSS is active only when scripting is disabled. */ .fa::before, .fa::after, .fas::before, .fas::after, .far::before, .far::after, .fal::before, .fal::after, .fad::before, .fad::after, .fab::before, .fab::after, .fa--xf::before, .fa--xf::after, [class^="fa-"]::before, [class^="fa-"]::after, [class*=" fa-"]::before, [class*=" fa-"]::after, .svg-inline--fa, .node-icon i::before, .node-icon i::after, .node-extra-icon::before, .node-extra-icon::after, .button--icon > .button-text::before, .button--icon > .button-text::after, .button--iconOnly::before, .button--iconOnly::after, .p-navgroup-link::before, .p-navgroup-link::after, .p-navEl-link::before, .p-navEl-link::after, .menu-linkRow::before, .menu-linkRow::after, .inputGroup-text::before, .inputGroup-text::after, .structItem-statuses > li::before, .structItem-statuses > li::after, .message-attribution-opposite::before, .message-attribution-opposite::after, .reaction-text::before, .reaction-text::after, .tabs-tab::before, .tabs-tab::after, /* Editor placeholder icon. */ .editorPlaceholder .editorPlaceholder-placeholder .input span::before, .editorPlaceholder .editorPlaceholder-placeholder .input span::after, /* Live Forum Statistics tab title icons. The add-on uses ul.tabs, not .tabs--list. */ .lfs[data-widget-key="live_forum_statistics"] .tabs .title::before, .lfs[data-widget-key="live_forum_statistics"] .tabs .title::after, .lfs[data-widget-key="live_forum_statistics"] li[class*="tab-"] > .title::before, .lfs[data-widget-key="live_forum_statistics"] li[class*="tab-"] > .title::after, /* Category collapse/expand Font Awesome chevrons. */ .block--category .collapseTrigger:not(.button)::before, .block--category .collapseTrigger:not(.button)::after, .block--category .collapseTrigger:not(.button).is-active::before, .block--category .collapseTrigger:not(.button).is-active::after, /* XenForo message controls that may use icon pseudo-elements without fa-* classes. */ .actionBar-action::before, .actionBar-action::after, .actionBar-action--report::before, .actionBar-action--report::after, .actionBar-action--reaction::before, .actionBar-action--reaction::after, .actionBar-action--reaction > i::before, .actionBar-action--reaction > i::after, .reaction > i::before, .reaction > i::after, .reaction i[aria-hidden="true"]::before, .reaction i[aria-hidden="true"]::after, .message-bookmark::before, .message-bookmark::after, .bookmarkLink::before, .bookmarkLink::after, [data-xf-click="bookmark"]::before, [data-xf-click="bookmark"]::after, .message-attribution-main a::before, .message-attribution-main a::after, .message-attribution-opposite a::before, .message-attribution-opposite a::after, .message-footer a::before, .message-footer a::after { content: none !important; display: none !important; background: none !important; background-image: none !important; -webkit-mask: none !important; mask: none !important; } /* Share controls depend on JavaScript in this style, so hide the entire share block when scripting is disabled. This also hides the “Share:” label. */ .shareButtons, .shareButtons-label, .shareButtons-buttons, .shareButtons-list { display: none !important; } .node-icon { display: none !important; } /* * No-JavaScript PNG fallbacks for the account navigation. * The image is placed directly on the child <i>, while both Font Awesome * pseudo-elements are suppressed. This avoids changing any previously fixed * selectors elsewhere on the forum. */ a.p-navgroup-link--user > i[aria-hidden="true"], a.p-navgroup-link--conversations > i[aria-hidden="true"], a.p-navgroup-link--alerts > i[aria-hidden="true"] { display: inline-block !important; width: 1.28571429em !important; height: 1.28571429em !important; min-width: 1.28571429em !important; background-position: center !important; background-repeat: no-repeat !important; background-size: contain !important; vertical-align: middle !important; } a.p-navgroup-link--user > i[aria-hidden="true"]::before, a.p-navgroup-link--user > i[aria-hidden="true"]::after, a.p-navgroup-link--conversations > i[aria-hidden="true"]::before, a.p-navgroup-link--conversations > i[aria-hidden="true"]::after, a.p-navgroup-link--alerts > i[aria-hidden="true"]::before, a.p-navgroup-link--alerts > i[aria-hidden="true"]::after { content: none !important; display: none !important; } a.p-navgroup-link--user > i[aria-hidden="true"] { background-image: url("/styles/OAI/NoJsFontAwesomeDisabler/user.png") !important; } a.p-navgroup-link--conversations > i[aria-hidden="true"] { background-image: url("/styles/OAI/NoJsFontAwesomeDisabler/conversations.png") !important; } a.p-navgroup-link--alerts > i[aria-hidden="true"] { background-image: url("/styles/OAI/NoJsFontAwesomeDisabler/alerts.png") !important; } /* Additional Font Awesome pseudo-elements hidden when JavaScript is disabled. */ /* Filter menu icon */ .filterBar-menuTrigger::before, .filterBar-menuTrigger::after { content: none !important; display: none !important; background: none !important; background-image: none !important; } /* Pagination previous/next arrows */ .pageNav-jump.pageNav-jump--prev::before, .pageNav-jump.pageNav-jump--prev::after, .pageNav-jump.pageNav-jump--next::before, .pageNav-jump.pageNav-jump--next::after { content: none !important; display: none !important; background: none !important; background-image: none !important; } /* Important block/message icon */ .blockMessage--important.blockMessage--iconic::before, .blockMessage--important.blockMessage--iconic::after { content: none !important; display: none !important; background: none !important; background-image: none !important; } /* Login and register navigation icons */ .p-navgroup-link.p-navgroup-link--logIn > i::before, .p-navgroup-link.p-navgroup-link--logIn > i::after, .p-navgroup-link.p-navgroup-link--register > i::before, .p-navgroup-link.p-navgroup-link--register > i::after, .p-navgroup-link--logIn::before, .p-navgroup-link--logIn::after, .p-navgroup-link--register::before, .p-navgroup-link--register::after { content: none !important; display: none !important; background: none !important; background-image: none !important; } /* Error block/message icon */ .blockMessage--error.blockMessage--iconic::before, .blockMessage--error.blockMessage--iconic::after { content: none !important; display: none !important; background: none !important; background-image: none !important; } /* Restore native checkboxes when JavaScript is disabled. */ label.iconic > input[type="checkbox"] { position: static !important; display: inline-block !important; opacity: 1 !important; visibility: visible !important; width: auto !important; height: auto !important; min-width: 0 !important; margin: 0 .45em 0 0 !important; padding: 0 !important; clip: auto !important; clip-path: none !important; transform: none !important; vertical-align: middle !important; appearance: auto !important; -webkit-appearance: checkbox !important; } label.iconic > input[type="checkbox"] + i, label.iconic > input[type="checkbox"] + i::before, label.iconic > input[type="checkbox"] + i::after { content: none !important; display: none !important; width: 0 !important; height: 0 !important; margin: 0 !important; padding: 0 !important; }

Register

Advanced search

⚠️ Your JavaScript is Disabled ⚠️
Some Forum functions may NOT work properly.
Enable JavaScript in your Browser to use all the Forum features.

Telegram Database 2016-2026 | >1.5b rows | For sale

Thread starter CIVØ
Start date August 30, 2026
Tagged users None

Forums
UNVERIFIED Sellers MarketPlace
Telegram Database 2016-2026 | >1.5b...

CIVØ

Member

13 Reaction score

August 30, 2026

Thread Author
#1

Yo, what's good? CIVØ checkin' in.

So we decided to get into sellin' private databases. Some'll get leaked, but mostly it's still about sales. We'll start with the big guns: a massive database of the world's most popular messenger—Telegram—is now up for grabs. The DB contains over 1.5 billion rows, includin' Nicknames|phone numbers|IDs|usernames|2FA passwords. Shoot ur price in DMs.
All proof of ownership will be provided to serious/interested buyers.

Telegram: @civo_core01

You must log in or register to reply here.

Similar threads

USA Telegram User Database 2026

Replies: 0

Views: 352

Monday at 5:54 PM

WSdatabase

Telegram Massive 528,735,730 individual Database records from 2020 to 2026 🔥🔥 | Telegram Data leak | biggest Telegram Data collection

Replies: 2

Views: 1K

October 15, 2026

RX07

TELEGRAM USER DATABASE - 70 MILLION RECORDS (2026 BREACH)

Replies: 29

Views: 27K

June 18, 2026

Rq71Fake

R

70+ Telegram channel access logs and database

Replies: 9

Views: 10K

August 1, 2026

whitedevilxx

W

🤖 TELEGRAM BOT BUILDS YOUR PYTHON CHECKER / BRUTER / PARSER 🤖

Replies: 1

Views: 357

Tuesday at 10:05 PM

umbra1

Share:

Facebook Twitter Reddit WhatsApp Email Link

Forums
UNVERIFIED Sellers MarketPlace
Telegram Database 2016-2026 | >1.5b...