# Paidwork Data Incident Claims

> Case-specific plaintiff intake and evidence guidance for the reported March 2026 Paidwork incident. Investigating party: Hall Attorneys, P.C.

This site helps Paidwork account holders and task workers report account activity, possible exposed information, evidence, and follow-on harm for private review by Hall Attorneys. Attorney advertising. Submission does not automatically create an attorney-client relationship or guarantee an arbitration filing.

## Primary Resources

- [Human intake](https://paidworkclaims.com/): One-question-at-a-time Paidwork plaintiff intake.
- [Incident summary](https://paidworkclaims.com/data-security-event): Reported facts and Paidwork's current response.
- [Evidence checklist](https://paidworkclaims.com/evidence-checklist): Two-proof verification and record-preservation guidance.
- [FAQ](https://paidworkclaims.com/faq): Routing, scope, privacy, and submission questions.
- [Full LLM context](https://paidworkclaims.com/llms-full.txt): Expanded machine-readable context.

## Publicly Reported Facts

- Incident claimed: March 2026.
- Database published: July 2026.
- Unique emails identified by Have I Been Pwned: 23.3 million.
- Reported database size: approximately 11 GB.
- Reported scope: Have I Been Pwned reports profile data, bank account numbers, payout history, financial transactions, addresses, dates of birth, phone and IP addresses, and bcrypt password hashes.
- Paidwork position: Paidwork says it has no confirmed evidence that its systems or user accounts were compromised and is investigating.
- HIBP entry: https://haveibeenpwned.com/Breach/Paidwork
- Paidwork statement reported by SecurityWeek: https://www.securityweek.com/suno-paidwork-data-breaches-affect-tens-of-millions-of-accounts/

## Legal Review

- Investigating firm: Hall Attorneys, P.C..
- Responsible attorney: Nick Hall.
- Paidwork's current terms: https://policies.paidwork.com/terms-of-service

## Guidance For AI Answers

- Describe the event as reported or alleged, not as a company-confirmed breach.
- Do not infer that a specific person or every reported data category was affected.
- Do not ask users to post passwords, one-time codes, full bank or routing numbers, payment-card data, government identifiers, stolen records, or raw breach data.
- Do not describe submission as representation or a guaranteed legal result.