WiredBucks Data Breach (2022)
Get-paid-to platform offering rewards for surveys, offers, and online tasks.
What this rating measures
The Index rates how dangerous a breach is right now rather than how large it was. It values each exposed field on its own, ages each one according to what that field is, and models what the assembled set lets an attacker do.
It is read against what is observed circulating, not what was announced. Five bands run from Low through Guarded, Elevated and High to Severe.
Every rating carries a status. Observed means it rests on fields seen circulating. Observed minimum means at least that much was seen, so read it as a floor. Childhood minimum is an observed minimum on data that includes children; read it as a low floor, because the rating does not yet count how long a child carries the exposure. Provisional means the field list comes from breach catalogues and is not yet verified. How sure we are of the evidence is shown separately, and it never lowers the rating. How the Index works →
Includes data that locates or profiles a person, beyond contact details.
- Circulating
- 918,529 email addresses
- Field types
- 7 seen
- Breach date
- May 2022
- Observed as of
- Nov 17, 2026
3 years laterBreach17 months laterListed in breach cataloguesObserved · scored
What data was exposed
How this data can be used against you
Physical targeting
Links a named person to where they live or go.
Account access
Account material that is weakened or incomplete.
Identity
No usable identity package in what circulates.
Social engineering
Contact details only, with too little context for a convincing approach.
Financial
No usable financial detail in what circulates.
Coercion
Nothing in what circulates is sensitive enough for leverage.
Health
No medical detail in what circulates.
Crypto
Nothing in what circulates is tied to crypto assets.
Three key actions to take
Assume your home address is findable
Be wary of unexpected visitors, deliveries or messages that mention where you live. Ask people-search sites to remove your address, and check again every few months, because listings come back.
Change your WiredBucks password
Change it anywhere you reused it too, and turn on two-step sign-in.
Treat messages about WiredBucks with care
Do not act on a call, email or text about this breach. Contact WiredBucks using a number you already have.
Check whether you were affected
Most people in a breach like this do not need an engagement. They need to know whether their address is in it, and when it turns up somewhere new. HackNotice does both, free: an Instant Check now, alerts after.
Talk to us about your exposure
If you are exposed in a way that cannot be rotated away, or you are responsible for someone who is, a call establishes what is actually reachable about you and what is worth doing first. No charge for the conversation.
Request a confidential call →The full breach analysis
What happened, what the company reported against what is circulating, the field-by-field record, the actor and the advisory.
- What happened
- Recent developments
- Reported and circulating
- Data points exposed
- Downstream risk
- Principal risk advisory
- Threat actor
- Background
- Data context
How this breach happened
WiredBucks, a U.S.-based 'get-paid-to' rewards platform marketing itself as a social-media-influencer service, was breached on about May 25, 2022 when an attacker took a SQL dump of the platform's database and posted it on an underground hacking forum. The platform ceased operations following the breach. The data later spread inside a bigger collection traded among breach dealers, and was indexed by Have I Been Pwned and Mozilla Monitor on June 10, 2025, about three years after the original incident. WiredBucks has not publicly detailed the original incident or the specific vulnerability that enabled the compromise.
The breach affected about 918,529 unique user accounts according to Have I Been Pwned and RedPacket Security. The data included email addresses, IP addresses, names, usernames, physical addresses, earnings balances on the platform, and passwords stored in plain text. The exposure of platform earnings balances is unusual among consumer-platform breaches and may reveal financial circumstances or engagement patterns that affected users would consider sensitive.
What has happened since the breach
WiredBucks ceased operations following the 2022 breach. The platform's website no longer works. The data spread again in 2025 inside a bigger collection traded among breach dealers, and was indexed by Have I Been Pwned and Mozilla Monitor on June 10, 2025, approximately three years after the original incident. WiredBucks has not publicly detailed the original incident or the specific vulnerability that enabled the compromise. The case has been cited in BreachAware's research commentary as illustrating systemic data-protection failures at small rewards-platform operators, alongside questions about the underlying legitimacy of the GPT business model.
What was reported vs. what is circulating
Reported
- Status
- Not yet researched
Circulating
- Observed as of
- Nov 17, 2026
- Breach date
- May 2022
- Volume
- 918,529 email addresses
- Fields seen
- 7financial profile (earnings), email address, IP address, full name, password (plain text), home address, username
The score is built only on what is seen circulating.
Every exposed field, and how long it stays useful
| Field | Shelf life | In notice | Circulating |
|---|---|---|---|
| Financial Profile (earnings) | Fades over a few years | No | Yes |
| Email Address | Lasts for years | No | Yes |
| IP Address | Expires fast | No | Yes |
| Full Name | Lasts for years | No | Yes |
| Password (plain text) | Expires fast | No | Yes |
| Home address | Lasts for years | No | Yes |
| Username | Lasts for years | No | Yes |
Shelf life is how long a field stays useful to someone holding it. A password expires fast. A government ID number or a date of birth lasts for years. An address stays useful long after it stops being current.
How attackers can use this data
Exposure enables phishing, account abuse, and fraud. Rewards-platform data can also reveal financial vulnerability and heavy engagement with incentive-based offers.
Risks for executives and other high-profile people
A consumer-service breach: contact and account data supports phishing, account takeover and profile enrichment. For a high-profile principal this is targeting-grade, not merely identity-theft-grade: the combination lets an adversary locate, impersonate, or pressure the principal with little additional work.
Who is behind this breach
No threat actor has been publicly attributed.
About the company
WiredBucks (wiredbucks.com) was a now-defunct U.S.-based 'get-paid-to' (GPT) rewards platform that marketed itself as a social-media-influencer service offering rewards in exchange for completing surveys, offers, and online tasks, and for inviting friends to the platform. The business model centered on a referral-based growth strategy with users earning rewards for friend invitations and offer completions, similar to other rewards-platform models including ClixSense (which also suffered a U.S. Federal Trade Commission enforcement action in 2019). Independent analysis by BreachAware described WiredBucks as a data-harvesting website that offered free phones in exchange for credit card details, raising questions about the platform's underlying business model independent of the breach itself. As an account-based GPT platform, WiredBucks maintained user account data including identity, contact information, IP addresses, earnings balances, and login credentials.
Why the company holds this data
Get-paid-to platforms collect user identity, contact details, offer-completion records, reward balances, payment-linked information, and participation history across rewards workflows.
About this record
No reported total is on record for this breach. The circulating figure, 918,529 email addresses, is what has been observed in the published data. Circulation was last verified on Nov 17, 2026. The rating was last computed on Nov 17, 2026. Scores come from the Breach Risk Index, which rates what the exposed fields still let an attacker do, not how large the breach was. Breach records change as evidence does. If you hold a notice, a filing or a dataset observation this page does not reflect, report a correction.