luxrender.net
Aug 10, 2026
Full WordPress database dump from luxrender.net, a 3D rendering software community website. The breach contains user account data including usernames, display names, hashed passwords (phpass/bcrypt), and email addresses. Also includes a separate paypal_payments.csv file and usermeta EAV records with fields for names and other profile attributes. User registrations span from 2020 to late 2023/early 2024. The actionscheduler_claims table shows a claim date of January 2026, suggesting the dump may have been taken around that time.
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.
luxrender.net__0golmw3_usermeta__eav.csv16 columns22 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 0 | skip | high | [0] header is 'email', values contain @ signs |
| 1 | firstName | high | [1] header is 'firstName', values are common given names like 'Kane', 'Mia' |
| 3 | lastName | high | [3] header is 'lastName', values are common surnames like 'Dane', 'Batum' |
| 4 | skip | medium | [4] header is 'phoneNumber', values likely phone numbers |
| 5 | address1 | medium | [5] header is 'address1', values represent street addresses |
| 6 | address2 | medium | [6] header is 'address2', values represent apartment/unit numbers |
| 7 | city | medium | [7] header is 'city', values represent city names |
| 8 | state | medium | [8] header is 'state', values represent state abbreviations or names |
| 9 | skip | high | [9] header is 'dateOfBirth', values match date format |
| 10 | zip | high | [10] header is 'zipCode', values represent ZIP codes |
| 11 | skip | medium | [11] header is 'socialSecurityNumber', values likely SSNs |
| 12 | password | high | [12] header is 'password', values represent hashed or plain-text passwords |
| 13 | username | high | [13] header is 'username', values are unique usernames |
| 14 | country | high | [14] header is 'country', values represent country names or codes |
| 15 | gender | high | [15] header is 'gender', values likely 'M'/'F' or 'Male'/'Female' |
| 17 | facebookId | high | [17] header is 'facebookId', values represent Facebook user IDs |
Notes: 19 columns total, 16 contain PII. The 'middleName' column (index 2) and 'linkedin' column (index 18) appear empty or non-PII in sample rows and are excluded.
luxrender.net__0golmw3_users.csv4 columns22 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | username | high | header "user_login" resolves to PII field "username" |
| 2 | password | high | header "user_pass" resolves to PII field "password" |
| 4 | high | header "user_email" resolves to PII field "email" | |
| 9 | fullName | high | header "display_name" resolves to PII field "fullName" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
luxrender.net__luxrender.net__0GOLMw3_actionscheduler_actions.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns are internal tracking fields (IDs, status, timestamps, schedules, attempts). No PII present — this is an actionscheduler_claims table for WordPress task scheduling, not user account data.
luxrender.net__luxrender.net__0GOLMw3_actionscheduler_claims.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a two-column CSV with headers 'claim_id' and 'date_created_gmt'. Neither column contains PII - 'claim_id' is an internal sequential ID and 'date_created_gmt' is a timestamp. No email, name, address, or other personal data is present in these rows.
luxrender.net__luxrender.net__0GOLMw3_actionscheduler_groups.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a simple CSV file with only two columns: group_id and slug. The data appears to be internal WordPress/WooCommerce plugin configuration or grouping identifiers (e.g., Action Scheduler migrations, Rocket preload, AAwP plugin). No PII is present — these are internal system identifiers for feature toggles or plugin groups. All columns are non-PII and should be skipped per rules.
luxrender.net__luxrender.net__0GOLMw3_actionscheduler_logs.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: The file is a log table from WordPress's action scheduler. It contains only action IDs, messages, and timestamps — no PII fields are present. All columns are internal system identifiers or status messages, and do not map to any PII categories.
luxrender.net__luxrender.net__0GOLMw3_commentmeta.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a metadata table from a WordPress plugin (antispam_bee). The file contains internal tracking IDs (meta_id, comment_id) and a plugin-specific reason code. No PII is present. All columns are internal identifiers or plugin metadata and should be skipped.
luxrender.net__luxrender.net__0GOLMw3_comments.csv2 columns2 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | fullName | high | [2] header 'comment_author', values are human names |
| 3 | high | [3] header 'comment_author_email', values contain '@' symbols |
Notes: This is a WordPress comment table. Only comment_author and comment_author_email contain PII. All other columns are internal IDs, timestamps, IP addresses, user agents, or content — these are excluded per rules.
luxrender.net__luxrender.net__0GOLMw3_litespeed_img_optm.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII detected in the first 50 rows. The data consists solely of image metadata (IDs, file paths, dimensions, sizes). No personal information such as names, emails, or addresses is present.
luxrender.net__luxrender.net__0GOLMw3_options.csv1,009 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
luxrender.net__luxrender.net__0GOLMw3_postmeta.csv2 columns24,051 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | username | high | [2] header 'meta_key', values are keys like '_wp_attached_file', '_menu_item_type', etc. These are metadata keys, not PII. No user identifiers detected in values. |
| 3 | password | high | [3] header 'meta_value', contains serialized PHP data structures (a:5:{...}) which are likely WordPress metadata values, not actual passwords. No password patterns detected in values. |
Notes: This appears to be a WordPress wp_postmeta table dump containing metadata associations. Most columns contain internal WordPress metadata keys and values. Only potential PII-like patterns were found in meta_value column but these appear to be serialized PHP arrays representing image metadata and menu item configurations, not actual user credentials or personal data. No clear email addresses, phone numbers, names, or other PII detected in the first 50 rows.
luxrender.net__luxrender.net__0GOLMw3_posts.csv11,638 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
luxrender.net__luxrender.net__0GOLMw3_ppress_forms.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a forms configuration table, not user data. Columns contain form metadata (names, types, dates) and do not include any PII fields. No email, phone, name, or other PII values are present in the sample rows.
luxrender.net__luxrender.net__0GOLMw3_ppress_formsmeta.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII columns present. This is a configuration/settings dump for WordPress forms and user profiles, containing only serialized JSON settings and design parameters. No actual user data or PII values appear in the sample.
luxrender.net__luxrender.net__0GOLMw3_redirection_items.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file contains no PII columns. All columns are internal IDs, URLs, status flags, and timestamps. No emails, names, addresses, or other personal data are present.
luxrender.net__luxrender.net__0GOLMw3_redirects_404.csv0 rows
File structure
Notes: This appears to be a log file of URL accesses rather than structured PII data. The columns are: id, url, ip_address, referrer, count, last_redirected. While ip_address could be considered PII, the values shown are URLs and timestamps only. No identifiable personal information (email, phone, name, address, etc.) is present in the first 50 rows. The structure is consistent with access logs tracking page views/downloads rather than user account data.
luxrender.net__luxrender.net__0GOLMw3_term_relationships.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: no·Quote: "
Notes: This file is a pure taxonomy relationship dump (object_id, term_taxonomy_id, term_order) with no PII fields or free-form text. All rows are structured relational data with numeric IDs only. No emails, names, or addresses are present.
luxrender.net__luxrender.net__0GOLMw3_term_taxonomy.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a taxonomy table from a WordPress database dump. It contains only taxonomy IDs, term IDs, taxonomy names, descriptions, parent relationships, and counts. No PII fields are present. All columns are internal taxonomy identifiers and metadata, which are not considered PII according to the exclusion rules.
luxrender.net__luxrender.net__0GOLMw3_termmeta.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a WordPress usermeta table dump (luxrender.net). All columns are internal metadata keys (wpil_*), counters, and serialized arrays. No PII is present — these are system-generated tracking fields, not user profile data. The meta_value column contains only numeric counters (0) or empty serialized arrays (a:0:{}), never personal data. This is typical WordPress metadata storage for plugin tracking, not user PII.
luxrender.net__luxrender.net__0GOLMw3_terms.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a taxonomy/term list table (term_id,name,slug,term_group). No PII present. All values are generic terms/categories related to footwear/shoes. No emails, names, addresses, or other personal data.
luxrender.net__luxrender.net__0GOLMw3_tm_taskmeta.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: The file appears to be a WordPress actionscheduler_tasks table dump containing serialized PHP data structures (task_options). All values are URLs and serialized arrays with no personal identifiable information (PII). The data consists of task metadata and URLs, not user account details. No PII fields detected in the first 50 rows.
luxrender.net__luxrender.net__0GOLMw3_tm_tasks.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a log table tracking URL preloading tasks for the WordPress site. Columns contain task IDs, user IDs, URLs, timestamps, and status flags. No PII fields are present — all URLs are generic site paths, and IDs are internal numeric identifiers. The 'user_id' field is an internal account ID (not a username or email) and should be skipped per exclusion rules.
luxrender.net__luxrender.net__0GOLMw3_usermeta.csv4 columns385 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | userId | high | numeric user identifier, mapped to skip by rule |
| 3 | username | high | column 'meta_key' contains 'nickname' and values match usernames |
| 4 | firstName | high | column 'meta_key' contains 'first_name' and values are given names |
| 5 | lastName | high | column 'meta_key' contains 'last_name' and values are surnames |
Notes: File is a WordPress usermeta table export. Only PII columns from meta_key='first_name', 'last_name', and 'nickname' are mapped. user_id is an internal numeric ID and skipped per rules. All other meta_key values represent settings or non-PII data.
luxrender.net__luxrender.net__0GOLMw3_users.csv4 columns22 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | username | high | header "user_login" resolves to PII field "username" |
| 2 | password | high | header "user_pass" resolves to PII field "password" |
| 4 | high | header "user_email" resolves to PII field "email" | |
| 9 | fullName | high | header "display_name" resolves to PII field "fullName" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
luxrender.net__luxrender.net__0GOLMw3_wpr_above_the_fold.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII found in the first 50 rows. The file appears to be a WordPress database dump containing only URLs, image metadata, and status flags. No personal information such as names, emails, or addresses is present in the visible data.
luxrender.net__luxrender.net__0GOLMw3_wpr_lazy_render_content.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file appears to be a log of page views with URLs and hashed values, but no personal identifiable information such as names, emails, or addresses is present. The values in the third column appear to be hashed identifiers, not PII.
luxrender.net__luxrender.net__0GOLMw3_wpr_preconnect_external_domains.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII fields detected in the provided rows. All columns appear to be URLs, flags, arrays of domains, and status messages — no personal data such as names, emails, addresses, etc. The rows represent website crawling or scraping activity metadata, not user account data. Per the instructions, return an empty columns object {} because there are no importable PII fields.
luxrender.net__luxrender.net__0GOLMw3_wpr_rocket_cache.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: no·Quote: "
Notes: No structured PII data detected in the provided rows. The file appears to be a list of URLs with status and timestamps, lacking any identifiable personal information fields. All entries are article URLs with status flags and timestamps, which do not contain PII according to the exclusion rules.
luxrender.net__luxrender.net__0GOLMw3_yoast_indexable.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This dataset appears to be a WordPress SEO/metadata table (rank_math_seo_score) and contains no personal identifiable information fields. All columns represent internal WordPress IDs, SEO scores, timestamps, and structured metadata values. No PII columns identified.
luxrender.net__luxrender.net__0GOLMw3_yoast_indexable_hierarchy.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: no·Quote: "
Notes: This is a pure numeric table with no headers and no identifiable information. All fields appear to be internal IDs (indexable_id, ancestor_id, depth, blog_id). No PII is present in any column.
luxrender.net__luxrender.net__0GOLMw3_yoast_primary_term.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII columns detected in this structured file. All columns appear to be internal IDs, timestamps, and taxonomy codes related to WordPress category management. No personal data (email, name, address, etc.) is present in the first 50 rows.
luxrender.net__luxrender.net__0GOLMw3_yoast_seo_links.csv3,484 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
luxrender.net__luxrender.net__0GOLMw3_yoast_seo_meta.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: no·Quote: "
Notes: This is a simple numeric table showing object IDs and link counts (internal/incoming). No PII fields present. All columns are numeric IDs and counters, which are explicitly excluded by rules (internal IDs and non-PII counters). No email, phone, name, address, or other PII values are visible.
luxrender.net__paypal_payments.csv1 column9,947 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 8 | high | unlabeled column — sampled values parse as email addresses |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance