
Paytaca, the self-custodial Bitcoin Cash (BCH) wallet and payments platform, disclosed two separate cyberattacks on its backend systems that occurred on November 17 and 18. In a November 18 security advisory, the company said attackers exploited distinct vulnerabilities to generate fraudulent peer-to-peer (P2P) orders and unsolicited payment requests.
What happened
- November 17: An issue in Paytaca’s P2P Ramp backend was exploited to create fake P2P orders.
- November 18: A second, separate vulnerability was used to create unauthorized payment requests through another backend component.
Paytaca’s response
- The company said its security team began investigating both incidents immediately and implemented fixes while monitoring systems for suspicious activity.
- It warned users not to interact with unfamiliar payment requests or approve transactions they did not initiate.
- Paytaca has not disclosed how many fraudulent orders or requests were generated, nor confirmed any financial losses. It also has not identified the attacker(s) or published technical details about the exploits, and it did not say whether the two incidents were related.
Why user funds were not directly compromised
Paytaca emphasized that these attacks were limited to backend infrastructure and did not involve customers’ private keys. Because Paytaca is self-custodial, users keep their private keys on their own devices; the keys are never stored on Paytaca’s backend servers. “Moving funds requires cryptographic signatures generated using users’ private keys,” the company noted—meaning a backend compromise alone cannot generate valid signatures to move funds without the wallet owner’s approval.
User guidance
Paytaca urged users to:
- Carefully review transaction details before signing or approving anything.
- Ignore suspicious P2P orders and unsolicited payment requests.
- Never disclose recovery phrases or private keys.
Broader context: more wallet-related incidents this month
Paytaca’s disclosure follows several other security events affecting wallet services and related vendors in mid-November:
- Optimizely script injections: Security researchers reported malicious Optimizely JavaScript injected into about 186 sites, including pages tied to Ledger and Coinpass. The script could replace genuine wallet addresses with attacker-controlled addresses, targeting eight cryptocurrencies (including BCH, ETH, BTC). StepSecurity traced roughly $6,600 in activity across related wallets, though some transactions predated the campaign.
- Keplr/Web3Auth breach: Keplr suspended Google and Apple login methods after an authentication provider (Web3Auth) breach exposed private keys for some accounts. Investigators traced more than $6 million in transfers across over 44,000 wallets.
- Trezor customer data leak: Hardware-wallet maker Trezor disclosed a customer data exposure on November 16 affecting about 27,000 orders handled by shipping partner Skladon. Personal and order data were exposed, though Trezor said device and recovery backups were not compromised.
What’s next
Paytaca said it is strengthening security measures and monitoring for further suspicious activity but has not provided a timeline for completing its investigation or publishing a technical breakdown of the vulnerabilities. For now, the company asks customers to stay vigilant while fixes and additional safeguards are put in place.
What happened
- November 17: An issue in Paytaca’s P2P Ramp backend was exploited to create fake P2P orders.
- November 18: A second, separate vulnerability was used to create unauthorized payment requests through another backend component.
Paytaca’s response
- The company said its security team began investigating both incidents immediately and implemented fixes while monitoring systems for suspicious activity.
- It warned users not to interact with unfamiliar payment requests or approve transactions they did not initiate.
- Paytaca has not disclosed how many fraudulent orders or requests were generated, nor confirmed any financial losses. It also has not identified the attacker(s) or published technical details about the exploits, and it did not say whether the two incidents were related.
Why user funds were not directly compromised
Paytaca emphasized that these attacks were limited to backend infrastructure and did not involve customers’ private keys. Because Paytaca is self-custodial, users keep their private keys on their own devices; the keys are never stored on Paytaca’s backend servers. “Moving funds requires cryptographic signatures generated using users’ private keys,” the company noted—meaning a backend compromise alone cannot generate valid signatures to move funds without the wallet owner’s approval.
User guidance
Paytaca urged users to:
- Carefully review transaction details before signing or approving anything.
- Ignore suspicious P2P orders and unsolicited payment requests.
- Never disclose recovery phrases or private keys.
Broader context: more wallet-related incidents this month
Paytaca’s disclosure follows several other security events affecting wallet services and related vendors in mid-November:
- Optimizely script injections: Security researchers reported malicious Optimizely JavaScript injected into about 186 sites, including pages tied to Ledger and Coinpass. The script could replace genuine wallet addresses with attacker-controlled addresses, targeting eight cryptocurrencies (including BCH, ETH, BTC). StepSecurity traced roughly $6,600 in activity across related wallets, though some transactions predated the campaign.
- Keplr/Web3Auth breach: Keplr suspended Google and Apple login methods after an authentication provider (Web3Auth) breach exposed private keys for some accounts. Investigators traced more than $6 million in transfers across over 44,000 wallets.
- Trezor customer data leak: Hardware-wallet maker Trezor disclosed a customer data exposure on November 16 affecting about 27,000 orders handled by shipping partner Skladon. Personal and order data were exposed, though Trezor said device and recovery backups were not compromised.
What’s next
Paytaca said it is strengthening security measures and monitoring for further suspicious activity but has not provided a timeline for completing its investigation or publishing a technical breakdown of the vulnerabilities. For now, the company asks customers to stay vigilant while fixes and additional safeguards are put in place.



