Bitcoin Cash wallet Paytaca reports two cyberattacks in 48 hours
- Published
Paytaca disclosed two backend security incidents on November 17 and 18 that affected its Bitcoin Cash wallet service. The attacks let outsiders create fraudulent peer-to-peer orders and unsolicited payment requests, while private keys stayed on users’ devices.
Key claims & sources
What it means
Paytaca is a self-custodial Bitcoin Cash wallet, so its backend can handle order and payment coordination while user keys stay on the user side. That setup helps explain why a backend incident can still affect activity without exposing the wallet’s private keys. The disclosure landed in November 2024, when security incidents at crypto apps and wallets remain a live concern for users who rely on them for payments and peer-to-peer transfers.
For Paytaca users, the practical effect is that fake peer-to-peer orders and payment requests can appear inside a service they use for Bitcoin Cash transactions. Users now need to be more cautious about confirming requests and checking the source of payment instructions before acting on them. The backend attack leaves the wallet’s custodial boundary intact, but it puts more weight on users spotting suspicious activity.
The case shows the split between protecting private keys and protecting the surrounding payment rails. Self-custody can limit one kind of loss, while backend compromise can still disrupt the trust layer that makes wallet-to-wallet commerce work. Bitcoin Cash and similar payment-focused systems depend on fast, low-friction transfers, so attacks on order generation and request flows strike at the service layer rather than the key layer.
Still open is how broad the impact was across Paytaca’s backend and whether any users actually acted on the fraudulent requests. The disclosures do not say whether the attacks were contained immediately, which systems were touched, or whether any other services were affected. The next useful detail would be a fuller incident report from Paytaca describing the scope and the checks users should use going forward.
Market reaction i
Bitcoin rose 0.4% in the 4 hours after the first headline, after falling 0.1% in the 2 hours before.
25 prices, one every 30 minutes
Coverage timeline
Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.
Other recent incidents
| When | What happened | Figure |
|---|---|---|
| 1 days ago | B18 TimeBank · Unknown incident | $404.5k |
| 2 days ago | MORE Markets · Unknown incident | $308k |
| 2 days ago | Lighter · API key leakage incident | $10.4M |
| 2 days ago | Optimizely (OPTIMJACK) · Supply Chain Attack incident | $2.3k |
| 3 days ago | Luxor Commander · Unknown incident | no figure in dollars |
4330 incidents stored