The February 2026 official record
On February 26, 2026, the US Attorney's Office for the Southern District of New York announced that Yurii Nazarenko had pleaded guilty to a conspiracy involving identification-document fraud in connection with operating OnlyFake. The announcement describes the sale of digital counterfeit identification and activity from approximately 2021 through 2024. This is an attributed account of the announced case, not a FakeKit product test. US DOJ: OnlyFake guilty-plea announcement, February 26, 2026
That dated announcement does not establish who controls every domain using the OnlyFake name today. We do not infer a current operator, operational status or later sentencing outcome from a past announcement or a similarly named site.
The published material we inspected
A PDF titled OnlyFake Service Offer identifies itself as service rules associated with the OnlyFake name and lists service addresses. That is evidence of what the document states, not independent proof of who controls a website today or how its product behaves. OnlyFake: published service-offer document (PDF)
A separately published privacy PDF discusses registration information and website request information. A written policy is not a retention audit: it does not establish what any particular submission receives, stores or deletes in practice. OnlyFake: published privacy document (PDF)
The source URLs were inspected for this research note on October 2, 2026. We have not independently authenticated their publisher identity, confirmed that these are the latest operative terms, or verified the operator of another domain using a similar name.
| Question | Available evidence | Unresolved |
|---|---|---|
| Was an OnlyFake-related prosecution announced? | DOJ guilty-plea announcement dated February 26, 2026 | Current control of similarly named services and later case outcomes |
| Does published material use the OnlyFake name? | The linked offer and privacy documents do | Current control of every similarly named domain |
| What does the provider state about its service? | Its own written terms | Whether the delivered behavior matches those statements |
| What happens to submitted information? | A published privacy description | Observed retention, deletion and recipient behavior |
| Does an output pass a verification system? | No FakeKit test was conducted | Any acceptance rate or compatibility claim |
An alternative depends on the job
| Your task | FakeKit option | Scope limit |
|---|---|---|
| Exercise form errors | Fictional JSON records with missing-field and date scenarios | No identity proofing |
| Check an export parser | Marked JSON and common-field CSV fixtures | No issuer-specific document schema |
| Test OCR reading order | Original abstract sheets with expected text | No government-layout coverage benchmark |
| Inspect check-digit arithmetic | Single-field calculator and explicit collision cases | No full MRZ or authenticity verdict |
These are functional alternatives for bounded testing, not claims that FakeKit reproduces another service's products. If the task requires proving a real identity, use a suitable authorized process instead of any fictional output.
For real customer onboarding
FakeKit also offers identity verification services through an API and review dashboard. Those services use an agreed production workflow; the fictional utilities above do not perform them. This commercial offering is separate from the source review in this note.
Review the verification service
Define identity, business and screening requirements for your operation.
Explore resourceCheck rates and monthly minimums
Compare the published plans before requesting service access.
Explore resourceWhat a responsible review would need
- An identified operator and a working contact channel.
- Permission to test within a defined, lawful sandbox.
- A precise output specification and permanent non-valid labeling.
- An observed data-handling method, with collection kept to the minimum required.
- Reproducible steps, observed results and explicit failures, rather than selected screenshots.
We do not infer product safety from a disclaimer alone. Nor do we publish unsupported allegations about a provider. If better primary evidence becomes available, the research note should change with the evidence.