Dark Web Roundup: Infostealer Logs, a Claimed Kazakhstan Court Database and 26.5 Million Telegram Records
SOCRadar's Dark Web Team has reported several underground posts. All of the claims below are unverified.
The first is a listing from Daxus, a vendor of infostealer logs, advertising about 2.96 million URL-login-password records through its Daxus.pro platform. Services include searchable credential logs, session cookies, private logs and email account access. The listing does not say which malware collected the data or which organisations are affected. If genuine, the records could fuel credential stuffing and account takeover, especially where passwords are reused.
A seller using the alias Brose claims to hold a 507 million-record database from Kazakhstan's Supreme Court (Sud.kz), covering 2014 to 2026 across 186 tables, for $50,000. The seller says it includes data on about 16.6 million citizens, national ID numbers, passport details, court documents, password hashes, administrative credentials, session tokens and payment information. Separately, an actor called Noiem claims access to Greece's KEF citizen-service ticketing platform, with about 5.93 million records and 1.27 million unique tax numbers. The claimed data includes social security numbers, contact details and password hashes.
An actor called SmithBrianI says it released a first batch of alleged TSMC data for free after finding no buyer, and plans a second batch priced at 5 BTC for November 18, 2026. No record count, data types or samples were given, and AMD was mentioned as a possible next target. Finally, Ghost_King is advertising about 26.5 million Telegram user records from 2020 to 2024, compiled from scraping and other sources. The listing does not establish a breach of Telegram itself, but the data could support phishing and identity fraud.
Why it matters
Infostealer logs that include session cookies can bypass passwords, so organisations relying on password changes alone may stay exposed. The Telegram and Greek claims show how scraped or compiled personal data feeds targeted phishing and impersonation even when no single vendor was breached. Security leaders should treat unverified listings as prompts to check their own exposure, not as confirmed incidents.
What to do
- Check staff and corporate email addresses against credential exposure monitoring for infostealer log leaks.
- Force password resets and revoke active sessions for any account that appears in leaked credential data.
- Enable multi-factor authentication on email and corporate services to blunt credential stuffing.
- Warn staff about phishing that uses personal details such as phone numbers and names.