traedex.com
Dec 1, 2025
Database breach of Traedex (traedex.com), a Brazilian binary options / auto-trading platform. The dump contains user authentication credentials (email, hashed passwords, salts), KYC verification records, deposit and withdrawal transaction data, auto-trading robot configurations (including martingale settings, risk parameters), trading history, referral partner and payout data, premium subscription orders, Facebook Pixel event logs with hashed PII (email, name), push notification subscriptions, and session data. User records appear to be primarily Brazilian (pt-BR locale, BRL currency, Brazilian phone numbers). Data timestamps range from approximately July 2025 through early 2026, suggesting the breach captured a live database snapshot in late 2025.
Data found in this dataset
Source files
Expand any file to inspect its column headers and the LLM's field-mapping reasoning, recorded during ingestion.
traedex.com__auth_robo__records.csv1 column65,545 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | high | header "email" resolves to PII field "email" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
traedex.com__config_robo__records.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. All columns are internal system identifiers, configuration flags, numeric parameters, timestamps, and UUIDs. No email, phone, name, address, DOB, SSN, password, or username fields are present.
traedex.com__daily_withdrawal_limits__records.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be internal IDs, timestamps, and counters. The sample shows UUID-like identifiers and ISO 8601 timestamps, typical of database logs or transaction records without direct PII exposure.
traedex.com__facebook_pixel_events__records.csv4 columns2,572 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 17 | high | [17] header 'event_data.user_data.em' — Facebook Pixel standard field 'em' for hashed email; values are SHA-256 hex hashes of email addresses | |
| 18 | firstName | high | [18] header 'event_data.user_data.fn' — Facebook Pixel standard field 'fn' for hashed first name; values are SHA-256 hex hashes |
| 19 | lastName | high | [19] header 'event_data.user_data.ln' — Facebook Pixel standard field 'ln' for hashed last name; values are SHA-256 hex hashes |
| 43 | high | [43] header 'event_data.data.0.user_data.em.0' — duplicate Facebook Pixel CAPI path for hashed email; same 'em' field pattern |
Notes: Facebook Pixel event log table (58 columns). All PII fields are SHA-256 hashed per Facebook's Conversions API spec: em=email, fn=firstName, ln=lastName. Columns [0],[1],[10],[22],[45] are UUID internal/external identifiers (skip). Columns [23],[46] are IP addresses (skip). Columns [24],[47] are user-agent strings (skip). Remaining columns are event metadata, transaction amounts, timestamps, and pixel tracking tokens — all non-PII.
traedex.com__historico_robo__records.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file appears to be a structured CSV with transaction records. However, there are no identifiable PII fields (such as email, phone, name, address, etc.) present in the visible data. All columns appear to contain transactional data (IDs, operation types, amounts, descriptions, timestamps) and security log messages referencing email addresses indirectly (in the description field). Since these emails are embedded within descriptive text rather than as dedicated columns, and no other PII is present, no columns map to PII fields. The 'descricao' column contains phrases like 'Depósito de R$1000.00' and security messages referencing emails, but these are not structured PII columns.
traedex.com__operacoes_robo__records.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns found. All columns are internal identifiers, trading parameters, timestamps, status flags, or system metadata. The breach context mentions user authentication credentials and KYC records, but this particular file appears to be the trading strategy execution logs, not the user database dump.
traedex.com__premium_orders__records.csv1 column29,422 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 18 | high | unlabeled column — sampled values parse as email addresses |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
traedex.com__premium_webhook_logs__records.csv4 columns11,249 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 10 | high | unlabeled column — sampled values parse as email addresses | |
| 16 | high | unlabeled column — sampled values parse as email addresses | |
| 46 | high | unlabeled column — sampled values parse as email addresses | |
| 64 | high | unlabeled column — sampled values parse as email addresses |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
traedex.com__push_message_templates__records.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file is unstructured prose with no consistent column structure. It contains messages/notifications rather than structured user records. No PII fields are present in a columnar format. The content appears to be system notifications or marketing messages in Portuguese, with no identifiable user data in structured columns.
traedex.com__push_notifications_log__records.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a notification log file with no PII fields. Columns contain notification IDs, titles, bodies, URLs, categories, target counts, status, and timestamps. No personal identifiable information is present in the first 50 rows.
traedex.com__push_scheduled_notifications__records.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file is NOT structured PII data. It appears to be notification/push-message logs with columns like id, title, body, category, URL, timestamps, status, and result details. No actual personal identifiers (email, phone, name, address, etc.) are present in the visible columns. The values are system messages, URLs, and timestamps. Per rules, no columns map to PII fields.
traedex.com__push_subscriptions__records.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified in this file. The data appears to be push notification endpoint information and authentication keys for web push services (Apple, Google, Mozilla, Windows). These are not personal identifiable information fields but rather technical identifiers for push notification services. All columns contain UUIDs, URLs, tokens, and user-agent strings which are not mapped to any PII fields in the available field types.
traedex.com__referral_partners__records.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in the provided rows. The file appears to contain only UUIDs and timestamps, which are internal identifiers and not considered PII according to the provided rules.
traedex.com__referral_payouts__records.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal transaction identifiers and timestamps. Columns include UUIDs (id, referral_id), numeric amounts, status flags, and ISO 8601 timestamps (paid_at, created_at, updated_at). No PII fields are present. All columns are marked as skip per exclusion rules for internal IDs and timestamps.
traedex.com__referral_visits__records.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, IP addresses, user agents, Facebook Pixel parameters, UTM tracking parameters, or timestamps. No PII is present in this dataset.
traedex.com__referrals__records.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII detected in the provided rows. The data appears to be referral or transaction logs containing only UUIDs, status codes, and timestamps. No personal identifiable information (email, phone, name, address, etc.) is present in the visible columns.
traedex.com__sessions_robo__records.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns appear to be internal identifiers, tokens, and timestamps. No PII fields detected in the provided rows.
traedex.com__sinais_robo__records.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns relate to trading robot configurations, market indicators, and execution metadata. Columns like 'id' are internal UUIDs, and timestamps are non-DOB. No emails, names, addresses, or credentials present in the first 50 rows.
traedex.com__sistema_auto_trading__records.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a system log or administrative report, not a user data dump. Columns contain internal IDs, flags, timestamps, and counters — no PII fields are present. Columns 'id', 'is_active', 'last_execution', 'total_users_checked', 'total_operations_executed', 'created_at', and 'updated_at' are all internal system metadata or timestamps, which must be skipped per exclusion rules.
traedex.com__user_plans__records.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, subscription status flags, timestamps, and trading parameters. No emails, names, addresses, phones, DOB, SSN, passwords, or usernames present in the sample.
traedex.com__user_roles__records.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be an internal administrative table, not user PII. Columns are internal IDs (UUIDs) and system metadata (timestamps). No PII fields are present. The 'role' column shows 'admin' and the timestamps are ISO format. All columns are excluded per rules for internal IDs and timestamps.
traedex.com__user_turnover__records.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal identifiers and transaction metadata. No PII fields are present. Columns include internal UUIDs (id, user_id), account type, financial totals (total_deposited, total_traded, withdrawable_amount), and timestamps (created_at, updated_at). All columns are marked as skip per exclusion rules (internal IDs, financial/transactional data, timestamps).
traedex.com__user_utm_tracking__records.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains marketing/tracking data (UTM parameters, Facebook click IDs, landing pages, session timestamps). Column [1] 'user_id' is an internal identifier (skip). Columns [2-9] (utm_source, utm_medium, utm_campaign, fbclid, fbc, fbp, landing_page, created_at) are marketing tracking and timestamps (skip). No PII fields are present in this data sample.
traedex.com__usuarios_robo__records.csv1 column44,209 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | high | unlabeled column — sampled values parse as email addresses |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
traedex.com__utm_reengagement_visits__records.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, tracking parameters, or timestamps. No PII fields are present in the provided sample. Columns like fbclid, fbc, and fbp are Facebook Pixel identifiers and tracking tokens, not PII. The file appears to contain only marketing/attribution data and session timestamps, with no email, name, address, phone, DOB, or other personal data.