Back to Details

breach-data-analysis

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Breach Data Analysis

数据泄露数据分析

Breach records reveal which services a selector used, what data leaked, and sometimes reused usernames and passwords to pivot on.

泄露记录会显示某个查询对象（邮箱、用户名或手机号）曾使用过哪些服务、哪些数据遭泄露，有时还能通过重复使用的用户名和密码进行关联分析。

Check exposure

检查泄露情况

Have I Been Pwned (
```
haveibeenpwned.com
```
) — the trusted starting point. Shows which breaches an email appears in and what data classes leaked. API (keyed) enables bulk checks and the Pwned Passwords k-anonymity endpoint.
DeHashed / Snusbase / IntelX — paid, searchable across email, username, name, phone, IP; return actual records. Use within your authorization only.

Have I Been Pwned（
```
haveibeenpwned.com
```
）——值得信赖的起点。显示邮箱出现在哪些泄露事件中，以及哪些类型的数据遭泄露。带密钥的API支持批量查询，还有Pwned Passwords的k-匿名性端点。
DeHashed / Snusbase / IntelX——付费服务，可通过邮箱、用户名、姓名、手机号、IP进行搜索；返回实际泄露记录。仅在获得授权的情况下使用。

Interpret

解读分析

Service list = accounts to pivot to. An email in a forum breach reveals a handle →
```
username-osint
```
; a matching username elsewhere links identities.
Data classes — note what leaked (passwords, addresses, DOB, security questions) to gauge risk, not to exploit it.
Timeline — breach dates place the account's activity in time.

服务列表 = 可关联的账户。若某邮箱出现在论坛泄露事件中，可获取对应的用户名→
```
username-osint
```
；若其他地方出现相同用户名，则可关联身份信息。
数据类型——记录泄露的数据类型（密码、地址、出生日期、安全问题）以评估风险，而非用于攻击。
时间线——泄露事件的发生时间可定位账户的活动时段。

Hard rules

硬性规则

Never use leaked passwords to log in to anything. Credential stuffing is a crime, full stop — see ../../ETHICS.md.
Treat breach data as sensitive; store minimally and encrypted.
Corroborate — breach compilations contain errors, duplicates, and fabricated rows. A single record is a lead, not proof.

绝不能使用泄露的密码登录任何平台。凭证填充属于犯罪行为，这是底线——详见../../ETHICS.md。
将泄露数据视为敏感信息；尽量少存储并加密保存。
交叉验证——泄露数据集合可能包含错误、重复和伪造条目。单条记录仅作为线索，而非证据。

Defensive use

防御性应用

For a self-audit or client, turn findings into action: rotate exposed passwords, enable MFA, and check for reuse across the discovered services.

针对自我审计或客户需求，将分析结果转化为行动：更换已泄露的密码、启用MFA（多因素认证），并检查在已发现的服务中是否存在密码复用情况。