abusewith.us
May 30, 2026
Database dump from AbuseWithUs (abusewith.us), a credential lookup/combo-list tool site that aggregated data from multiple gaming/RSPS (RuneScape Private Server) community databases. The archive contains search results from several underlying databases including WP_RuneLocus (a RuneScape fansite), ipb_Rskingdom, ipb_WAD, ipb_Zybez, ipb_parabot, and ipb_rs2006. Data includes email addresses, plaintext passwords, MD5/bcrypt hashed passwords, IP addresses, and usernames. The files are split alphabetically (aaa, aab, etc.) representing a full database lookup export.
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.
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-.nl.txt36,411 rows
File structure
Notes: This file is NOT DATA. It is instructional/descriptive prose about a breach (AbuseWithUs credential lookup tool). The opening section contains: (1) how-to instructions ('Put the name of the user...'), (2) a note about blank pages, and (3) breach context narrative describing the database aggregator and its sources. While the sample does contain structured credential records embedded below ('Found matches in dbs/...'), the file as a whole is a hybrid prose+data artifact. The data rows themselves are valid PII (emails, usernames, hashed passwords, IP addresses) but are presented here within a larger non-tabular, narrative document structure. This is a README-style breach dump, not a cleanly delimited dataset. Recommend treating as unstructured with embedded email/phone/username extraction, or request the raw credential export files directly (dbs/WP_RuneLocus.txt, dbs/ipb_Rskingdom.txt, etc.) for proper structured parsing.
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_Jam.txt32,479 rows
File structure
Notes: This file contains database export records from multiple gaming community databases (WP_RuneLocus, ipb_Rskingdom, etc.) in unstructured format. Records are presented as free-form text with inconsistent delimiters and varying row structures. Emails, passwords (plaintext and hashed), usernames, and IP addresses are embedded throughout but without consistent column boundaries. Routing to streaming email/phone/credential extractor.
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_aaa.txt43,106 rows
File structure
Notes: This is a README/description file about the AbuseWithUs breach, not a structured data file. The content describes the tool's purpose and shows sample output from credential lookups, but contains no consistent column structure. The actual data records visible are formatted as free-form database dumps (colon-delimited combo lists and SQL INSERT statements) rather than a parseable tabular format with headers. While PII is present (emails, usernames, password hashes, IP addresses), the file itself is documentation/prose with embedded examples, not a structured export ready for column mapping.
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_aab.txt33,249 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_aac.txt35,075 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_aad.txt32,693 rows
File structure
Notes: This is a data breach index/README file describing AbuseWithUs (abusewith.us), a credential lookup tool that aggregated gaming database records. The file contains instructional prose followed by raw credential dumps from multiple sources (WP_RuneLocus, ipb_Rskingdom, ipb_WAD, ipb_parabot, ipb_rs2006). While individual embedded credentials are visible (emails, usernames, hashed passwords, IP addresses), there is NO consistent columnar structure — each database section uses different delimiters and field ordering (colon-separated in some sections, space-separated in others, inconsistent field counts per row). The content mixes structured dump sections with free-form headers and formatting. This is best processed by unstructured extraction (streaming email/phone/username detection) rather than column mapping.
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_aae.txt32,970 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_aaf.txt31,724 rows
File structure
Notes: This file is a credential lookup/combo-list dump from AbuseWithUs, containing unstructured search result output from multiple gaming databases (WP_RuneLocus, ipb_Rskingdom, ipb_WAD, etc.). The content is presented as database query results and raw record exports with no consistent column delimiter or row structure. Each section has a different format: some are colon-delimited credentials, others are SQL dump tuples with embedded metadata, and others are tab/space-separated fragments. Multiple emails, usernames, password hashes, and IP addresses are visible inline throughout. This requires streaming extraction rather than column mapping.
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_aag.txt2,192 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_aah.txt1,980 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_aai.txt1,815 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_aaj.txt1,349 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_aak.txt4,323 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_aal.txt6,445 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_aam.txt3,476 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_aan.txt9,881 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_aao.txt968 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_aap.txt3,411 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_aaq.txt1,211 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_aar.txt16,364 rows
File structure
Notes: This file is a README/descriptive document about the AbuseWithUs breach database tool, followed by sample search results in unstructured text format. The file header contains instructions and context about the tool's purpose. The data section shows raw credential records from multiple gaming databases (WP_RuneLocus, ipb_Rskingdom, ipb_WAD, ipb_Zybez) with embedded emails, usernames, passwords, hashes, and IP addresses in free-form text with no consistent column delimiter or structure. Records vary wildly in format and content. Emails and passwords are embedded inline. This is suitable for streaming extraction rather than column mapping.
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_aas.txt6,493 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_aat.txt3,870 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_aau.txt1,176 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_aav.txt1,825 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_aaw.txt1,449 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_aax.txt1,120 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_aay.txt1,466 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_aaz.txt1,562 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_aba.txt37,983 rows
File structure
Notes: This file is NOT a structured data export. It contains free-form prose describing the AbuseWithUs credential lookup tool, followed by unstructured query result dumps from multiple gaming databases (WP_RuneLocus, ipb_Rskingdom, etc.). The data is presented as raw forum/database export text with embedded emails, usernames, passwords (plaintext and hashed), and IP addresses inline within semi-structured record blocks, NOT as delimited columns. No consistent delimiter or column headers exist. This should be routed to a streaming email + phone + credential extractor, not column-based import.
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_abb.txt41,460 rows
File structure
Notes: This file is NOT a structured data export. It is a README/instructional document with embedded search results from multiple gaming database dumps. The content mixes prose instructions ('How to use: Put the name...'), section headers ('Found matches in dbs/...'), and unstructured record dumps (tuples with fields separated inconsistently across multiple lines). There is no consistent delimiter, no header row, and every record has a different structure. However, it contains numerous embedded PII: email addresses ([email protected], [email protected], etc.), plaintext passwords (Lost-Exorcism, Spedkid123, etc.), usernames (ghostfire, fortuna3333, andrew111, etc.), hashed passwords (MD5 and bcrypt), IP addresses, and dates of birth (6-7-1995, 15-6-1977, etc.). This should be routed to a free-form PII extraction pipeline for streaming email, phone, password, and identity extraction.
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_abc.txt34,584 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_abd.txt37,596 rows
File structure
Notes: This file is NOT STRUCTURED DATA. It is a README/documentation file describing the AbuseWithUs credential lookup tool, followed by free-form search result dumps from multiple databases (WP_RuneLocus, ipb_Rskingdom, etc.). The results are presented as prose with embedded credentials, not in consistent delimited columns. While PII is present (emails, usernames, password hashes, IP addresses), there is no consistent column structure or delimiter pattern across rows. This should be processed as unstructured text with inline email/username extraction.
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_abe.txt53,405 rows
File structure
Notes: This file is NOT DATA. It contains prose instructions and documentation about the AbuseWithUs credential lookup tool, followed by database dumps in multiple incompatible formats (colon-delimited CSV, then parenthesized SQL INSERT statements). The file mixes instructional text ('How to use:', 'Found matches in dbs/...') with raw structured records from different sources. While PII is embedded (emails, usernames, hashed passwords, IP addresses), there is no consistent row structure or delimiter across the entire file that would allow reliable column mapping. This is a hybrid unstructured/semi-structured dump mixing documentation and heterogeneous database exports. Rows have vastly different shapes: early rows use email:username:hash:email format (colon-delimited), later rows use SQL tuples with 100+ comma-separated fields in a different schema. Recommend streaming extraction for embedded emails, usernames, and phone numbers rather than column mapping.
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_abf.txt31,944 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_abg.txt1,212 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_abh.txt2,301 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_abi.txt19,382 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_abj.txt1,111 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_abk.txt1,742 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_abl.txt0 rows
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_abm.txt1,248 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_abn.txt1,990 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_abo.txt17,599 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_abp.txt1,131 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_abq.txt751 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_abr.txt13,810 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_abs.txt6,589 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_abt.txt1,417 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_abu.txt11,703 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_abv.txt2,568 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_abw.txt981 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_abx.txt805 rows
File structure
Notes: This file is a README/search results document from the AbuseWithUs credential lookup tool, not a structured data export. It contains prose explaining the tool's purpose, followed by free-form search result dumps from multiple underlying databases (WP_RuneLocus, ipb_Zybez, ipb_rs2006, etc.). Each database section uses different delimiters and record formats (colon-separated, pipe-separated, space-separated), with no consistent column structure across or within sections. The data contains embedded emails, usernames, passwords, hashes, and IP addresses inline. This is a streaming extraction scenario: embedded PII (emails, phones, usernames, passwords) will be extracted via separate email/phone/credential pattern matching, not column mapping.
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_aby.txt17,770 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_abz.txt1,372 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_aim.txt29 columns32 rows
File structure
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 0 | skip | high | Column 'uid' is an internal auto-increment ID per EXCLUSION RULES |
| 1 | username | high | Column 'username' contains human-generated login names (e.g., 'Pompano', 'Austin01', 'wigsaw', 'Sergio Kun Agüero', 'mikeandike') |
| 2 | password | high | Column 'password' contains MD5 and bcrypt hashes (e.g., 'c84826ef0823552f7f0f8e620bf615d6', '$P$B6LZFXoHTK.94kZwnljwzbzblFjS8p0') |
| 3 | skip | high | Column 'salt' is cryptographic salt for password hashing, non-PII |
| 4 | skip | high | Column 'loginkey' is an internal session/authentication token, non-PII |
| 5 | high | Column 'email' contains email addresses (e.g., '[email protected]', '[email protected]', '[email protected]') | |
| 6 | skip | high | Column 'postnum' is a post count metric, non-PII |
| 7 | skip | high | Column 'avatar' is a file path/URL, non-PII |
| 8 | skip | high | Column 'avatardimensions' is metadata, non-PII |
| 9 | skip | high | Column 'avatartype' is metadata, non-PII |
| 10 | skip | high | Column 'usergroup' is a role/permission ID, non-PII |
| 11 | skip | high | Column 'additionalgroups' is a role/permission list, non-PII |
| 12 | skip | high | Column 'displaygroup' is a role/permission ID, non-PII |
| 13 | skip | high | Column 'usertitle' is a custom rank/honorific prefix (e.g., 'The Founder', 'The Creator'), not generational suffix |
| 14 | skip | high | Column 'regdate' is a registration timestamp per EXCLUSION RULES |
| 15 | skip | high | Column 'lastactive' is a timestamp per EXCLUSION RULES |
| 16 | skip | high | Column 'lastvisit' is a timestamp per EXCLUSION RULES |
| 17 | skip | high | Column 'lastpost' is a timestamp per EXCLUSION RULES |
| 18 | skip | high | Column 'website' is a personal URL, non-PII in this context |
| 19 | username | high | Column 'icq' contains ICQ social media handle per rules (social media handles map to username) |
| 20 | username | high | Column 'aim' contains AIM social media handle per rules (social media handles map to username) |
| 21 | username | high | Column 'yahoo' contains Yahoo social media handle per rules (social media handles map to username) |
| 22 | username | high | Column 'msn' contains MSN social media handle per rules (social media handles map to username) |
| 23 | dob | high | Column 'birthday' contains dates in format DD-M-YYYY (e.g., '28-2-1992', '21-1-1992', '27-7-1991', '5-2-1994') |
| 24 | skip | high | Column 'birthdayprivacy' is a privacy setting, non-PII |
| 25 | skip | high | Column 'signature' is user profile text content, non-PII |
| 26 | skip | high | Column 'allownotices' is a preference boolean, non-PII |
| 27 | skip | high | Column 'hideemail' is a preference boolean, non-PII |
| 28 | skip | high | Subsequent columns are various flags, settings, account metadata, and preferences — all non-PII |
Notes: SQL dump from AbuseWithUs containing gaming community forum user data (MyBB/Invision Power Board formats). Primary PII fields identified: email, username (login names and social media handles), password hashes, and DOB. Social media handles (aim, icq, yahoo, msn) classified as 'username' per rules. Timestamps and internal IDs skipped per EXCLUSION RULES. Avatar files, URL preferences, and user metadata skipped as non-PII.
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_aol.txt115,768 rows
File structure
Notes: This is NOT a delimited data file. The content is free-form prose describing a credential lookup tool (AbuseWithUs) followed by unstructured database dumps with no consistent column headers or delimiters. Lines vary wildly in structure and length. While emails, usernames, passwords, and hashes are visible inline, there is no tabular format to parse. This requires unstructured email/phone/PII extraction, not column mapping.
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_co.uk.txt131,433 rows
File structure
Notes: This is a free-form text file containing search results and usage instructions, not a structured data file. The preamble is prose (README-style instructions: 'How to use: Put the name...', 'NOTE: If the page is blank...', 'Found matches in dbs/WP_RuneLocus.txt:'). Below that are colon-delimited credential records (email:username:hash:email) from a gaming database breach. While the records themselves contain PII (emails, usernames, password hashes), they are presented as continuous prose output rather than a properly delimited or columnar dataset. The records lack consistent column headers and vary in structure (some have 4 fields, some have additional line breaks within fields). This is treated as unstructured data with embedded emails and should be processed via streaming extraction rather than column mapping.
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_com.txt4 columns1,443,659 rows
File structure
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 0 | high | All values contain @ symbol and valid email domain formats (gmail.com, hotmail.com, yahoo.com, etc.) | |
| 1 | username | high | Alphanumeric strings resembling gaming usernames/account names, often different from email local part |
| 2 | password | high | Values are either MD5 hashes (32-char hex), bcrypt hashes (starting with $P$), or plaintext passwords |
| 3 | high | Duplicate/verification field - matches column 0 email address exactly |
Notes: Standard 4-field combo format from RuneScape gaming database. Column 1 contains plaintext usernames, column 2 contains mixed plaintext and hashed passwords (MD5 and WordPress bcrypt $P$ format). Column 3 is a redundant email verification field. Some plaintext passwords contain embedded newlines/multi-line values. Data source: WP_RuneLocus and related RSPS community databases aggregated by AbuseWithUs.
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_gmail.txt4 columns379,423 rows
File structure
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 0 | high | All values contain @ symbol and are valid email addresses (gmail.com domain) | |
| 1 | username | high | Alphanumeric strings, often match or relate to usernames used on gaming sites; some contain hyphens, numbers, and gaming-related keywords |
| 2 | password | high | 32-character hexadecimal strings (MD5 hashes) or $P$ prefixed strings (phpass/WordPress bcrypt hashes); consistent with password storage formats |
| 3 | high | Duplicate of column 0; repeated email address for record verification |
Notes: Standard 4-column combo list from gaming community database aggregator. Format is email:username:password_hash:email_verification. Some password fields contain multiline values (spaces, newlines) likely due to data corruption or malformed export. Fields 0 and 3 are identical (redundant email storage). No personally identifiable information beyond email addresses present.
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_googlemail.txt10,550 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_live.txt130,125 rows
File structure
Notes: This is NOT a data breach file with structured records. The content is a README/instructional text describing how to use the AbuseWithUs credential lookup tool, followed by free-form search results output. Each result line contains colon-delimited credentials (email:username:password_hash:email) but this is presented as raw search output, not a structured export with defined columns. The file mixes prose instructions ('How to use:', 'NOTE:', 'Found matches in dbs/...') with unstructured result dumps. Processing via unstructured email/phone/credential extractor is appropriate.
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_msn.txt25 columns68 rows
File structure
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 0 | skip | high | uid - internal user ID column, auto-increment |
| 1 | username | high | column named 'username', contains human-generated login names (e.g., 'Pompano', 'williejeep', 'KiLo', 'hapy', 'dooble') |
| 2 | password | high | column named 'password', contains MD5 and bcrypt hashes |
| 3 | skip | high | salt - cryptographic salt for password hashing |
| 4 | skip | high | loginkey - session/authentication token |
| 5 | high | column named 'email', contains email addresses (e.g., '[email protected]', '[email protected]') | |
| 6 | skip | high | postnum - post count, internal metric |
| 7 | skip | high | avatar - avatar image file path |
| 8 | skip | high | avatardimensions - image dimensions metadata |
| 9 | skip | high | avatartype - avatar type flag |
| 10 | skip | high | usergroup - internal user group ID |
| 11 | skip | high | additionalgroups - internal group membership data |
| 12 | skip | high | displaygroup - internal display group setting |
| 13 | skip | high | usertitle - honorary/cosmetic title (not a name suffix) |
| 14 | skip | high | regdate - registration timestamp |
| 15 | skip | high | lastactive - last activity timestamp |
| 16 | skip | high | lastvisit - last visit timestamp |
| 17 | skip | high | lastpost - last post timestamp |
| 18 | skip | high | website - personal website URL |
| 19 | username | high | icq - ICQ handle (social media identifier, treated as username) |
| 20 | username | high | aim - AIM handle (social media identifier, treated as username) |
| 21 | username | high | yahoo - Yahoo Messenger handle (social media identifier, treated as username) |
| 22 | username | high | msn - MSN Messenger handle (social media identifier, treated as username) |
| 23 | dob | high | birthday - column named 'birthday', contains date values (e.g., '1-10-1988', '3-4-1998') |
| 24 | skip | high | birthdayprivacy - privacy setting for birthday |
Notes: SQL dump from MyBB forum software (ipb_Rskingdom.txt - actually MyBB users table). The table contains user registration data including usernames, password hashes, emails, and birthdates. Social media handles (ICQ, AIM, Yahoo, MSN) mapped to username field per instructions. The 'msn' column contains MSN Messenger handles, not email addresses, despite superficial similarity to email format in some contexts.
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_net.txt4,500 rows
File structure
Notes: This file is a free-form text dump from a credential lookup tool, NOT a structured data file. It contains search results and database excerpts with embedded emails, usernames, password hashes, and IP addresses in prose/SQL format. No consistent columnar delimiters or structure exists across rows. Rows vary wildly in format (colon-delimited credentials, SQL tuples, multi-line records). Embedded PII includes emails ([email protected], [email protected], etc.), usernames (robbie, wood1master7, etc.), plaintext and hashed passwords, and IP addresses. This should be processed by a streaming email/phone/credential extractor, not columnar mapping.
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_none.txt110,800 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_null.txt214,209 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_post.txt8,269 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_yahoo.txt426,699 rows
File structure
Notes: This file is NOT a structured data breach database. It is a README / instructional text describing how to use the AbuseWithUs credential lookup tool, followed by sample search results in free-form colon-delimited format (email:username:password_hash:email). The file mixes prose instructions ('How to use:', 'Found matches in dbs/', 'NOTE: If the page is blank...') with unstructured result lines. While individual result lines contain PII (email, username, hashed password), there is no consistent column structure, no header row, and the file serves primarily as documentation and example output rather than a queryable data export. The results are presented as raw concatenated strings, not as a delimited table. This content should be processed via a streaming credential pair extractor rather than column mapping.
AbuseWithUs_BF__data__Abusewith.us_DB_Lookup_-_ymail.txt25,118 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__pLookup_-_abusewith.us_-_.ca.txt34,186 rows
File structure
Notes: Free-form text dump from AbuseWithUs credential lookup tool. Contains embedded colon-delimited records with emails, usernames, and password hashes mixed with prose instructions and unstructured database exports. No consistent column structure across lines. Routed to streaming email/phone extractor.
AbuseWithUs_BF__data__pLookup_-_abusewith.us_-_.co.uk_.txt152,961 rows
File structure
Notes: This file is NOT DATA — it is a README/instructional page describing the AbuseWithUs credential lookup tool, followed by free-form search results in colon-delimited format with no consistent column structure. The preamble ('How to use:', 'Found matches in...') is prose documentation. The result lines are credential dumps (email:username:hash:email) with inconsistent formatting and embedded line breaks within fields. This is a credential combo-list export, not a structured database table. Route through streaming email + phone + credential extractor.
AbuseWithUs_BF__data__pLookup_-_abusewith.us_-_.nl.txt43,872 rows
File structure
Notes: This is a free-form text file (README/instructional prose followed by credential dump output). The file contains embedded emails and passwords but no consistent delimiter structure across lines. Each 'Found matches' section has different formatting: some lines are colon-delimited credential pairs, others are SQL-like tuples with commas and parentheses, and others use different separators. This is NOT a structured CSV/delimited file — it is unstructured text with embedded PII (emails, usernames, hashed passwords, plaintext passwords, IP addresses). Recommend streaming email + phone + credential extraction rather than column mapping.
AbuseWithUs_BF__data__pLookup_-_abusewith.us_-_.pt.txt1,743 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__pLookup_-_abusewith.us_-_.se.txt20,774 rows
File structure
Notes: This file is free-form prose text containing a credential lookup tool interface and search results from multiple gaming databases. It includes embedded PII (emails, usernames, passwords, IP addresses) but has NO consistent delimited structure across rows. Each result section uses different formatting (colon-delimited, SQL-like tuples, custom separators). Routing to streaming email/phone/password extractor.
AbuseWithUs_BF__data__pLookup_-_abusewith.us_-_0colon0.txt8,831 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__pLookup_-_abusewith.us_-_123.txt207,492 rows
File structure
Notes: This file is NOT DATA. It is a README/description document about the AbuseWithUs breach, containing prose instructions ('How to use:', 'Put the name of the account...', 'Found matches in pdbs/...') mixed with semi-structured credential dumps. While credential records ARE present (email:username:hash:email format), they are interspersed with explanatory text, navigation elements ('<javascript:history.go(-1)>'), and database record fragments with inconsistent structure and missing delimiters. The second section (ipb_Rskingdom.txt entries) contains raw database output with parentheses, commas, and mixed field ordering rather than consistent columnar layout. This is not a cleanly delimited file suitable for column mapping; instead, it is a hybrid document mixing documentation with embedded PII. Recommend routing through an unstructured email + phone + credential extractor.
AbuseWithUs_BF__data__pLookup_-_abusewith.us_-_3_colons.txt17,926 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__pLookup_-_abusewith.us_-_3_spaces.txt2,005 rows
File structure
Notes: This is NOT a structured data file. The content is free-form prose text containing a web interface description ('How to use', 'Found matches in pdbs/...') followed by unstructured credential dump lines. Each line varies in structure and content. While credential data is present (usernames, hashed passwords, IP addresses), there is no consistent delimiter or column header structure. This file should be processed as unstructured text with inline pattern extraction (emails, phones, hashes, IPs) rather than columnar mapping.
AbuseWithUs_BF__data__pLookup_-_abusewith.us_-_4_spaces.txt1,786 rows
File structure
Notes: Free-form text dump with embedded credentials (usernames, hashed passwords, IP addresses, plaintext passwords). No consistent delimiter or column structure. Each line has variable format. This is a credential lookup/combo-list export from AbuseWithUs aggregating gaming database breaches. Content includes usernames, MD5/bcrypt hashes, random tokens, IP addresses, and plaintext passwords separated by colons, but no structured columnar format. Routed to streaming extraction for embedded PII.
AbuseWithUs_BF__data__pLookup_-_abusewith.us_-__aol.txt120,316 rows
File structure
Notes: Free-form text with embedded PII (emails, usernames, password hashes, IP addresses). File contains search results from a credential lookup tool aggregating gaming database dumps. No consistent column delimiter or structure. Content includes raw database records with mixed formatting from multiple sources (WP_RuneLocus, ipb_Rskingdom). Email+phone extraction recommended via streaming parser.
AbuseWithUs_BF__data__pLookup_-_abusewith.us_-__gmail.txt854,630 rows
File structure
Notes: This file is NOT structured data. It contains prose text (instructions: 'How to use:', 'Put the name of the account...', 'Found matches in pdbs/WP_RuneLocus.txt:') followed by a list of colon-delimited credential records. While the credential lines themselves are delimited (email:username:hash:email), the file as a whole mixes instructional prose with data records and lacks a consistent header row or column structure. Streaming email and password extraction is recommended to capture the embedded credentials (email addresses, usernames, plaintext/hashed passwords) from this unstructured dump.
AbuseWithUs_BF__data__pLookup_-_abusewith.us_-__hotmail.txt4 columns219,150 rows
File structure
Format: CSV·Delimiter: :·Has header: no·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 0 | high | [0] All values are valid email addresses (contain @, end in .com/.co.uk/.nl/.be/.se/.fi/.ca/.nz) | |
| 1 | username | high | [1] Gaming/forum usernames: 'Abdullah', 'simonbif1', 'Escaped', 'DemonScape', 'Ripvayne', etc. Searchable identifiers used for account access |
| 2 | password | high | [2] Mix of MD5 hashes (32-char hex: '3a12372186645969eee168ce2bf6b885') and bcrypt hashes (starting with '$P$B': '$P$BuVLs2OyEhm.kfpBnpa7oruwl6FZwI.'). Standard password storage formats |
| 3 | high | [3] Duplicate of column [0] - same email addresses repeated (confirmation/verification field) |
Notes: Credential combo-list from AbuseWithUs gaming community database dump. 4 columns total: email, username, password hash (MD5/bcrypt), email confirmation. All rows contain valid PII. No header row present.
AbuseWithUs_BF__data__pLookup_-_abusewith.us_-__live.txt143,462 rows
File structure
Notes: This is a free-form text file containing search results and instructions from AbuseWithUs, a credential lookup tool. The file header includes prose instructions ('How to use:', 'Found matches in...') followed by raw credential dump lines. While individual lines contain structured data (email:username:hash:email pattern), the overall file structure is NOT a consistent delimited format — it mixes HTML navigation elements, instructional text, and credential records without uniform row structure or column headers. The content should be processed via free-form email/phone extraction rather than column mapping.
AbuseWithUs_BF__data__pLookup_-_abusewith.us_-__msn.txt48,365 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__pLookup_-_abusewith.us_-_aim.txt40,295 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__pLookup_-_abusewith.us_-_colon_space_colon.txt62 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__pLookup_-_abusewith.us_-_com.txt4 columns827,055 rows
File structure
Format: CSV·Delimiter: :·Has header: no·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 0 | high | [0] All values are valid email addresses (contain @, end in .com/.co.uk/.nl/.be/.se/.fi/.ca/.nz) | |
| 1 | username | high | [1] Gaming/forum usernames: 'Abdullah', 'simonbif1', 'Escaped', 'DemonScape', 'Ripvayne', etc. Searchable identifiers used for account access |
| 2 | password | high | [2] Mix of MD5 hashes (32-char hex: '3a12372186645969eee168ce2bf6b885') and bcrypt hashes (starting with '$P$B': '$P$BuVLs2OyEhm.kfpBnpa7oruwl6FZwI.'). Standard password storage formats |
| 3 | high | [3] Duplicate of column [0] - same email addresses repeated (confirmation/verification field) |
Notes: Credential combo-list from AbuseWithUs gaming community database dump. 4 columns total: email, username, password hash (MD5/bcrypt), email confirmation. All rows contain valid PII. No header row present.
AbuseWithUs_BF__data__pLookup_-_abusewith.us_-_googlemail.txt11,371 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__pLookup_-_abusewith.us_-_jam.txt35,985 rows
File structure
Notes: Free-form text dump from AbuseWithUs credential lookup tool. No consistent delimited structure — lines contain variable-length records with mixed formatting (colon-separated key:value pairs, comma-separated tuples, embedded prose). Contains embedded emails, passwords, hashed passwords, usernames, and IP addresses. Requires streaming email + phone + credential extractor; no column mapping applicable.
AbuseWithUs_BF__data__pLookup_-_abusewith.us_-_lol.txt1,950 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__pLookup_-_abusewith.us_-_net.txt153,312 rows
File structure
Notes: This file is NOT DATA. It is a README/description page from the AbuseWithUs credential lookup tool, containing instructions ('How to use'), search interface prose, and mixed database dumps with no consistent column structure. The content includes free-form text ('Put the name of the account...'), section headers ('Found matches in pdbs/...'), and embedded credential records from multiple underlying databases (WP_RuneLocus, ipb_Rskingdom, etc.) with inconsistent formatting (colon-delimited, comma-delimited tuples, and unstructured field ordering). This is unstructured output from a web search tool, not a tabular export. Route through streaming email/phone extractor for inline credential recovery.
AbuseWithUs_BF__data__pLookup_-_abusewith.us_-_none.txt110,978 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__pLookup_-_abusewith.us_-_null.txt241,359 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__pLookup_-_abusewith.us_-_poliwag.txt19 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__pLookup_-_abusewith.us_-_post.txt8,582 rows
File structure
Notes: This is a README/prose document describing a credential lookup tool (AbuseWithUs). It contains usage instructions, database names, and search result examples in free-form text layout. While embedded emails, usernames, IP addresses, and hashed passwords are visible in the example results, there is no consistent delimited structure or column headers. This should be routed through an unstructured email/phone/PII extractor rather than column mapping.
AbuseWithUs_BF__data__pLookup_-_abusewith.us_-_txt.txt1,120 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__pLookup_-_abusewith.us_-_www.txt8,564 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__pLookup_-_abusewith.us_-_yahoo.txt184,648 rows
File structure
Notes: Free-form text output from a credential lookup tool. No consistent delimiter or column structure. Data appears as colon-separated credential tuples (email:username:hash:email) embedded in prose, search instructions, and HTML-like navigation elements. Contains emails, usernames, MD5/bcrypt password hashes, and plaintext passwords scattered throughout unstructured text. Routed to streaming email + phone extractor for inline PII recovery.
AbuseWithUs_BF__data__pLookup_-_abusewith.us_-_ymail.txt29,511 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__pLookup_-_abusewith.us_-_zzz.txt6,414 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
AbuseWithUs_BF__data__pLookup_-_abusewith.us___.txt124 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones