์Šคํ‚ฌ what-leaked-about-you
๐Ÿ“ฆ

what-leaked-about-you

์ฝ˜ํ…์ธ  ๋ฆฌ๋น„์ „ r1 ๋†’์€ ์œ„ํ—˜ โš™๏ธ ์™ธ๋ถ€ ๋ช…๋ น์–ด๐Ÿ“ ํŒŒ์ผ ์‹œ์Šคํ…œ ์ ‘๊ทผ๐Ÿ”‘ ํ™˜๊ฒฝ ๋ณ€์ˆ˜

Assess Your Data Breach Exposure

Breach results are difficult to verify, interpret, and handle without exposing sensitive data. This skill provides a structured workflow for authorized analysis and reporting.

์ง€์›: Claude Codex Code(CC)
Maintain this Skill? Claim it โš ๏ธ 38 ๋‚˜์จ

๋‚ด ์—์ด์ „ํŠธ๋กœ ์„ค์น˜

์ด ์š”์ฒญ์„ ์—์ด์ „ํŠธ์— ๋ณต์‚ฌํ•˜์„ธ์š”. ๊ณต์‹ Skill ํŽ˜์ด์ง€์™€ ๋งค๋‹ˆํŽ˜์ŠคํŠธ๊ฐ€ ํฌํ•จ๋˜์–ด ์žˆ์Šต๋‹ˆ๋‹ค.

์—์ด์ „ํŠธ ์š”์ฒญ
Review the Skillstore skill "what-leaked-about-you" from https://skillstore.io/skills/useosint-what-leaked-about-you.md and its manifest at https://skillstore.io/api/skills/useosint-what-leaked-about-you/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

์—์ด์ „ํŠธ๋Š” ๊ณ„์†ํ•ด์„œ ๊ณ„ํš์„ ํ‘œ์‹œํ•˜๊ณ  ๋ณด์•ˆ ์ •์ฑ…์—์„œ ์š”๊ตฌํ•˜๋Š” ํ™•์ธ์„ ์š”์ฒญํ•ด์•ผ ํ•ฉ๋‹ˆ๋‹ค.

์—์ด์ „ํŠธ๊ฐ€ ์ฝ๊ธฐ ์‰ฌ์šด ๋ฆฌ์†Œ์Šค

AI ์—์ด์ „ํŠธ, ํฌ๋กค๋Ÿฌ, ์Šคํฌ๋ฆฝํŠธ๊ฐ€ ์ „์ฒด ํŽ˜์ด์ง€ ๋Œ€์‹  ์ •๋ฆฌ๋œ ์ปจํ…์ŠคํŠธ๋งŒ ํ•„์š”ํ•  ๋•Œ ์ด ๋งํฌ๋ฅผ ์‚ฌ์šฉํ•˜์„ธ์š”.

ํ…Œ์ŠคํŠธํ•ด ๋ณด๊ธฐ

"what-leaked-about-you" ์‚ฌ์šฉ ์ค‘์ž…๋‹ˆ๋‹ค. HIBP reports a verified forum breach containing email addresses, usernames, IP addresses, and password hashes.

์˜ˆ์ƒ ๊ฒฐ๊ณผ:

Confirmed exposure to the named forum. Change any reused password, enable multifactor authentication, review the recovered username, and never attempt login with leaked credentials.

"what-leaked-about-you" ์‚ฌ์šฉ ์ค‘์ž…๋‹ˆ๋‹ค. A commercial corpus shows one unattributed email and password pair with no source date.

์˜ˆ์ƒ ๊ฒฐ๊ณผ:

Unconfirmed exposure. Record the vendor and retrieval date, exclude the credential value, and do not attribute the record to any service.

"what-leaked-about-you" ์‚ฌ์šฉ ์ค‘์ž…๋‹ˆ๋‹ค. A client asks whether an existing password appears in known breach data.

์˜ˆ์ƒ ๊ฒฐ๊ณผ:

Use the Pwned Passwords range method locally. Send only the five-character SHA-1 prefix, compare suffixes locally, and do not log the password.

๋ณด์•ˆ ๊ฐ์‚ฌ

๋†’์€ ์œ„ํ—˜

All 25 static findings are false positives caused by Markdown links, inline code, and explanatory security terminology. No executable command, environment access, path traversal, or cryptographic implementation appears in the reviewed files. However, the skill encourages sensitive breach-record retrieval and pre-employment screening, creating substantial privacy and misuse risks.

3
์Šค์บ”๋œ ํŒŒ์ผ
459
๋ถ„์„๋œ ์ค„ ์ˆ˜
0
๊ฒ€ํ†  ํ•ญ๋ชฉ
0
์˜คํƒ ๋ฌด์‹œ๋จ

ํ™•์ธ๋œ ๋ณด์•ˆ ์šฐ๋ ค ์‚ฌํ•ญ (2)

๋†’์Œ
Sensitive Breach-Record Retrieval and Identity Profiling
The skill recommends services that return leaked field values, then uses those records to map identities and memberships across services.
The instructions explicitly describe retrieving record-level values and using usernames, phones, IP addresses, names, and passwords as cross-service identity signals.
๋†’์Œ
Employment Screening With Breached Personal Data
The declared scope includes pre-employment screening, although source licenses may prohibit employment decisions and breach records contain sensitive personal data.
The front matter names pre-employment screening, while the source guidance explicitly warns that licenses may prohibit employment use.

์œ„ํ—˜ ์š”์ธ

โš™๏ธ ์™ธ๋ถ€ ๋ช…๋ น์–ด (15)
๐Ÿ“ ํŒŒ์ผ ์‹œ์Šคํ…œ ์ ‘๊ทผ (1)
๐Ÿ”‘ ํ™˜๊ฒฝ ๋ณ€์ˆ˜ (1)
๊ฐ์‚ฌ์ž: codex
์ด ๋ณด๊ณ ์„œ ๊ณต์œ  ๋ฐ ์ธ์šฉ

๋ฒ„์ „์ด ์ง€์ •๋œ ํ‰๊ฐ€ ๋ณด๊ณ ์„œ, ์ค‘๋ฆฝ ๋ฐฐ์ง€, ์ž„๋ฒ ๋“œ ์นด๋“œ ๋ฐ ์ธ์šฉ์„ ๊ณต์œ ํ•˜์„ธ์š”. Skillstore๋Š” ๊ทผ๊ฑฐ๋ฅผ ๋ณด๊ณ ํ•˜์ง€๋งŒ ์ด Skill์˜ ์•ˆ์ „ ์—ฌ๋ถ€๋ฅผ ํŒ๋‹จํ•˜์ง€ ์•Š์Šต๋‹ˆ๋‹ค.

๋ฒ„์ „๋ณ„ ๋ณด๊ณ ์„œ ์—ด๊ธฐ
๋ณด์•ˆ ํ‰๊ฐ€

๋ณด๊ณ ์„œ ๋งํฌ ๋ณต์‚ฌ

https://skillstore.io/skills/useosint-what-leaked-about-you/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown ๋ฐฐ์ง€

[![Skillstore security assessment](https://skillstore.io/badges/skills/useosint-what-leaked-about-you/security.svg)](https://skillstore.io/skills/useosint-what-leaked-about-you?utm_source=security_passport_badge)

HTML ๋ฐฐ์ง€

<a href="https://skillstore.io/skills/useosint-what-leaked-about-you?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/useosint-what-leaked-about-you/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

์ž„๋ฒ ๋“œ ์นด๋“œ

<iframe src="https://skillstore.io/embed/skills/useosint-what-leaked-about-you.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
ํ•™์ˆ  ์ธ์šฉ (APA ยท BibTeX ยท CFF)

APA ์ธ์šฉ

useosint. (2026). what-leaked-about-you security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/useosint-what-leaked-about-you/audits/1

BibTeX ์ธ์šฉ

@techreport{useosint-useosint-what-leaked-about-you-2026, author = {useosint}, title = {what-leaked-about-you security audit report (audit version 1)}, institution = {Skillstore}, year = {2026}, number = {1}, url = {https://skillstore.io/skills/useosint-what-leaked-about-you/audits/1}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "what-leaked-about-you security audit report (audit version 1)" version: "unspecified" type: report authors: - name: "useosint" date-released: "2026-08-03" url: "https://skillstore.io/skills/useosint-what-leaked-about-you/audits/1" identifiers: - type: other value: "skillstore:useosint-what-leaked-about-you:audit:1" description: "Skillstore immutable audit report identifier"

Skillstore ์ ์ˆ˜

์ด ์ ์ˆ˜์˜ ์ด์œ  ์ฆ๊ฑฐ ์‹ ๋ขฐ๋„: ์ค‘๊ฐ„
55
์•„ํ‚คํ…์ฒ˜
85
์œ ์ง€๋ณด์ˆ˜์„ฑ
87
์ฝ˜ํ…์ธ 
65
์ปค๋ฎค๋‹ˆํ‹ฐ
83
์‚ฌ์–‘ ์ค€์ˆ˜

๋งŒ๋“ค ์ˆ˜ ์žˆ๋Š” ๊ฒƒ

Review Personal Exposure

Plan a self-audit that identifies exposed services, minimizes retained data, and prioritizes password changes without testing leaked credentials.

Triage an Account Compromise

Interpret authorized breach results, assess source confidence, and prepare remediation steps during an incident response investigation.

Protect an Authorized Client

Evaluate a client's exposure under written authority, document provenance, and report only findings relevant to the agreed objective.

์ด ํ”„๋กฌํ”„ํŠธ๋ฅผ ์‚ฌ์šฉํ•ด ๋ณด์„ธ์š”

Plan a Personal Breach Check
Create a privacy-preserving plan to check my own email address for breach exposure. Do not request or reproduce any password.
Interpret a Breach Summary
Interpret this authorized breach summary: [summary]. Separate confirmed facts, uncertain claims, affected data classes, and recommended account actions.
Assess Record Credibility
Assess these authorized records: [record descriptions]. Compare attribution, field structure, dates, provenance, duplication, and independent corroboration without retaining credential values.
Design a Controlled Investigation
Design an authorized breach-exposure investigation for [objective]. Define lawful scope, allowed selectors, source order, confidence rules, retention limits, and reporting boundaries.

๋ชจ๋ฒ” ์‚ฌ๋ก€

  • Obtain explicit authority and define the investigative objective before querying any identifier.
  • Start with curated membership-only sources and retrieve record-level fields only when necessary.
  • Exclude credentials, minimize personal data, encrypt evidence, log access, and delete records on schedule.

ํ”ผํ•˜๊ธฐ

  • Never authenticate, reset an account, or test password reuse with leaked credentials.
  • Do not treat combolists, duplicate vendor results, or public scrapes as independently verified breaches.
  • Do not expand identity pivots beyond the documented scope or use breach data for employment decisions.

์ž์ฃผ ๋ฌป๋Š” ์งˆ๋ฌธ

Does this skill search breach databases automatically?
No. It provides source-selection, interpretation, confidence, handling, and reporting guidance.
Can I check another person's email address?
Only with a valid lawful basis and appropriate authority. Self-audits and documented client investigations provide the clearest scope.
Does a missing result prove that no breach occurred?
No. A breach may be unpublished, unindexed, restricted, or absent from the selected source.
Can I test a leaked password on an account?
No. Never authenticate, request a reset, or test reuse with leaked credentials.
How should I check a password I already control?
Use the Pwned Passwords range method locally, avoid logs, and discard the plaintext immediately.
How should uncertain records be reported?
State the source, retrieval date, attribution limits, corroboration status, and confidence grade. Do not present uncertain records as confirmed facts.

๊ฐœ๋ฐœ์ž ์„ธ๋ถ€ ์ •๋ณด

์ž‘์„ฑ์ž

useosint

๋ผ์ด์„ ์Šค

MIT

Skillstore ๋ฆฌ๋น„์ „

r1

๋ฒ„์ „ ์•ˆ๋‚ด

์ž‘์„ฑ์ž๊ฐ€ ๋ฒ„์ „์„ ์„ ์–ธํ•˜์ง€ ์•Š์•˜์Šต๋‹ˆ๋‹ค.

์ฐธ์กฐ

76c3621ba67d9236f7e0674bbf2a2ecc2696e20c

์œ ์ง€๋ณด์ˆ˜ ์ตœ์‹ ์„ฑ

2026. 8. 3.

์‚ฌ์šฉ๋Ÿ‰

0 ๋‹ค์šด๋กœ๋“œ ยท 0 ์กฐํšŒ

ํŒŒ์ผ ๊ตฌ์กฐ

๐Ÿ“ reference/

๐Ÿ“„ record-fields.md

๐Ÿ“„ source-catalogue.md

๐Ÿ“„ SKILL.md

useosint์˜ ๋‹ค๋ฅธ ์Šคํ‚ฌ

์ „์ฒด ๋ณด๊ธฐ
์ „์ฒด ๋ณด๊ธฐ
๐Ÿ“ฆ

security-engineering

81

๋ณด์•ˆ ์—”์ง€๋‹ˆ์–ด๋ง ์˜์‚ฌ๊ฒฐ์ • ๊ฐ•ํ™”

์ž‘์„ฑ์ž 89jobrien

๋ณด์•ˆ ์—…๋ฌด๋Š” ์•„ํ‚คํ…์ฒ˜, ์•„์ด๋ดํ‹ฐํ‹ฐ, ์ปดํ”Œ๋ผ์ด์–ธ์Šค, ํ…Œ์ŠคํŠธ, ๋Œ€์‘ ๊ณ„ํš์— ๊ฑธ์ณ ์žˆ๋Š” ๊ฒฝ์šฐ๊ฐ€ ๋งŽ์Šต๋‹ˆ๋‹ค. ์ด ์Šคํ‚ฌ์€ Claude, Codex, Claude Code์— ๊ตฌ์กฐํ™”๋œ ๋ณด์•ˆ ์—”์ง€๋‹ˆ์–ด๋ง ์ง€์นจ์„ ์ œ๊ณตํ•ฉ๋‹ˆ๋‹ค.

๋ณด์•ˆ ๋ฐ ์ปดํ”Œ๋ผ์ด์–ธ์Šค ๋ณด๊ธฐ
๐Ÿ“ฆ

malware-analyst

78

๋ฉ€์›จ์–ด๋ฅผ ์•ˆ์ „ํ•˜๊ฒŒ ๋ถ„์„ํ•˜๊ธฐ

์ž‘์„ฑ์ž sickn33

๋ฉ€์›จ์–ด ์กฐ์‚ฌ๋Š” ํ”„๋กœ๋•์…˜ ์‹œ์Šคํ…œ์„ ๋…ธ์ถœํ•˜์ง€ ์•Š์œผ๋ฉด์„œ ๋ฐ˜๋ณต ๊ฐ€๋Šฅํ•œ ๋ถ„๋ฅ˜๊ฐ€ ํ•„์š”ํ•ฉ๋‹ˆ๋‹ค. ์ด ์Šคํ‚ฌ์€ ์Šน์ธ๋œ ๋ถ„์„๊ฐ€๊ฐ€ ์•ˆ์ „ํ•œ ๋ถ„์„, IOC ์ถ”์ถœ, ๋ณด๊ณ ๋ฅผ ์ˆ˜ํ–‰ํ•˜๋„๋ก ์•ˆ๋‚ดํ•ฉ๋‹ˆ๋‹ค.

๋ณด์•ˆ ๋ฐ ์ปดํ”Œ๋ผ์ด์–ธ์Šค ๋ณด๊ธฐ
๐Ÿ“ฆ

incident-runbook-templates

78

์ธ์‹œ๋˜ํŠธ ๋Ÿฐ๋ถ ์ž‘์„ฑ

์ž‘์„ฑ์ž wshobson

์ธ์‹œ๋˜ํŠธ ํŒ€์€ ์žฅ์• ๊ฐ€ ์‹œ์ž‘๋˜๊ธฐ ์ „์— ๋ช…ํ™•ํ•œ ๋Œ€์‘ ๋‹จ๊ณ„๊ฐ€ ํ•„์š”ํ•ฉ๋‹ˆ๋‹ค. ์ด ์Šคํ‚ฌ์€ Claude, Codex, Claude Code๊ฐ€ ๋ถ„๋ฅ˜, ์™„ํ™”, ์—์Šค์ปฌ๋ ˆ์ด์…˜, ์ปค๋ฎค๋‹ˆ์ผ€์ด์…˜ ์„น์…˜์„ ๊ฐ–์ถ˜ ๊ตฌ์กฐํ™”๋œ ๋Ÿฐ๋ถ ์ดˆ์•ˆ์„ ์ž‘์„ฑํ•˜๋„๋ก ๋•์Šต๋‹ˆ๋‹ค.

๋ณด์•ˆ ๋ฐ ์ปดํ”Œ๋ผ์ด์–ธ์Šค ๋ณด๊ธฐ
๐Ÿ“ฆ

incident-response-incident-response

78

ํ”„๋กœ๋•์…˜ ์ธ์‹œ๋˜ํŠธ ๋Œ€์‘ ์กฐ์œจ

์ž‘์„ฑ์ž sickn33

ํ”„๋กœ๋•์…˜ ์ธ์‹œ๋˜ํŠธ์—๋Š” ์••๋ฐ• ์†์—์„œ๋„ ๋น ๋ฅธ ๋ถ„๋ฅ˜, ๋ช…ํ™•ํ•œ ์†Œ์œ ๊ถŒ, ์‹ ๋ขฐํ•  ์ˆ˜ ์žˆ๋Š” ์ปค๋ฎค๋‹ˆ์ผ€์ด์…˜์ด ํ•„์š”ํ•ฉ๋‹ˆ๋‹ค. ์ด ์Šคํ‚ฌ์€ ์‹ฌ๊ฐ๋„ ๋ถ„๋ฅ˜, ๊ด€์ธก ๊ฐ€๋Šฅ์„ฑ ๊ฒ€ํ† , ์™„ํ™”, ๋ฐฐํฌ, ์ดํ•ด๊ด€๊ณ„์ž ์—…๋ฐ์ดํŠธ, ํฌ์ŠคํŠธ๋ชจํ…œ ์ „๋ฐ˜์— ๊ฑธ์ณ ๋Œ€์‘์„ ์ฒด๊ณ„ํ™”ํ•ฉ๋‹ˆ๋‹ค.

๋ณด์•ˆ ๋ฐ ์ปดํ”Œ๋ผ์ด์–ธ์Šค ๋ณด๊ธฐ
๐Ÿ“ฆ

incident-responder

78

ํ”„๋กœ๋•์…˜ ์ธ์‹œ๋˜ํŠธ๋ฅผ ๋” ๋น ๋ฅด๊ฒŒ ํ•ด๊ฒฐ

์ž‘์„ฑ์ž sickn33

ํ”„๋กœ๋•์…˜ ์ธ์‹œ๋˜ํŠธ์—๋Š” ๋น ๋ฅธ ๋ถ„๋ฅ˜, ๋ช…ํ™•ํ•œ ์—ญํ• , ์ •ํ™•ํ•œ ์ปค๋ฎค๋‹ˆ์ผ€์ด์…˜์ด ํ•„์š”ํ•ฉ๋‹ˆ๋‹ค. ์ด ์Šคํ‚ฌ์€ SRE ํŒ€์— ๊ตฌ์กฐํ™”๋œ ๋Œ€์‘ ๋‹จ๊ณ„, ๋ณต๊ตฌ ์ ๊ฒ€, ์ธ์‹œ๋˜ํŠธ ์ดํ›„ ๊ฐœ์„  ์ง€์นจ์„ ์ œ๊ณตํ•ฉ๋‹ˆ๋‹ค.

๋ณด์•ˆ ๋ฐ ์ปดํ”Œ๋ผ์ด์–ธ์Šค ๋ณด๊ธฐ
๐Ÿ“ฆ

debugging

84

์˜ค๋ฅ˜์™€ ๊ทผ๋ณธ ์›์ธ ๋””๋ฒ„๊ทธ

์ž‘์„ฑ์ž 89jobrien

์ฆ๊ฑฐ๊ฐ€ ๋กœ๊ทธ, ์Šคํƒ ํŠธ๋ ˆ์ด์Šค, ์„œ๋น„์Šค ์ „๋ฐ˜์— ํฉ์–ด์ ธ ์žˆ์œผ๋ฉด ์˜ค๋ฅ˜์™€ ์ธ์‹œ๋˜ํŠธ๋ฅผ ๋ถ„๋ฅ˜ํ•˜๊ธฐ ์–ด๋ ต์Šต๋‹ˆ๋‹ค. ์ด ์Šคํ‚ฌ์€ ์ง„๋‹จ์„ ๊ตฌ์กฐํ™”ํ•˜๊ณ , ๋กœ๊ทธ๋ฅผ ํŒŒ์‹ฑํ•˜๋ฉฐ, ํŒจํ„ด์„ ์‹๋ณ„ํ•˜๊ณ , ์ตœ์†Œํ•œ์˜ ์ˆ˜์ •์œผ๋กœ ์•ˆ๋‚ดํ•ฉ๋‹ˆ๋‹ค.

์ฝ”๋”ฉ ๋ฐ ๊ฐœ๋ฐœ ๋ณด๊ธฐ