0x140f0a6e140f…140f0a71

ConfirmedSecurity538 vB158 sat/vB3 min decode

Paytaca Discloses Two Backend Breaches in 48 Hours

Bitcoin Cash wallet Paytaca disclosed backend breaches on Nov 17-18 that generated fraudulent P2P orders and payment requests, while insisting user private keys stayed on devices.

Bitcoin Cash wallet Paytaca reports two cyberattacks in 48 hours
WitnessBitcoin Cash wallet Paytaca reports two cyberattacks in 48 hoursPexels / pixabay

Outputs

  1. Paytaca disclosed two backend breaches on November 17 and 18

  2. Attackers generated fraudulent P2P orders and unsolicited payment requests

  3. Private keys were never stored on Paytaca servers and were not compromised

  4. No confirmed losses or affected-user count has been disclosed

  5. Related incidents: $6M+ traced across 44,000 Keplr wallets; 27,000 Trezor orders exposed

Bitcoin Cash wallet Paytaca disclosed two separate backend breaches on November 17 and 18, which let attackers generate fraudulent peer-to-peer orders and unsolicited payment requests. In a November 18 security advisory, the self-custodial wallet and payments platform said the first incident involved a vulnerability in its P2P Ramp backend that attackers exploited to create fake orders.

A second vulnerability was exploited the following day, allowing unauthorized payment requests through another part of Paytaca's backend systems. The company's security team is investigating both incidents and implementing fixes. It has not identified the attackers, detailed how either flaw was exploited, or said whether the two incidents were connected.

Were user funds exposed?

Paytaca said the attacks stayed confined to its backend infrastructure and did not touch the private keys that control customers' cryptocurrency holdings. Under its self-custodial model, keys are stored on users' own devices and never on Paytaca servers, so backend access alone cannot produce the signatures needed to move funds.

"Moving funds requires cryptographic signatures generated using users' private keys," the company explained. The distinction matters for the second incident: an attacker could create an unsolicited request through the compromised backend, but completing a transfer still required authorization from the wallet holding the funds.

Paytaca has not disclosed how many fraudulent orders or payment requests the attackers generated, the number of affected users, or any confirmed financial losses. It instructed customers to ignore suspicious P2P orders, avoid approving transactions they did not initiate, review transaction details before signing, and never share recovery phrases or private keys.

How does this fit the wider pattern?

The disclosure lands amid a cluster of wallet-related security incidents targeting different layers of the stack. On November 17, crypto.news reported that malicious Optimizely scripts had affected 186 websites, including properties associated with Ledger and Coinpass. Security researchers found the injected JavaScript could swap legitimate wallet addresses for attacker-controlled ones, potentially redirecting payments across eight cryptocurrencies, including Bitcoin Cash, Ethereum and Bitcoin.

StepSecurity traced roughly $6,600 in activity and holdings across four associated wallets, though some transactions predated the attack and could not be counted as confirmed losses.

A separate incident hit Keplr wallet users who signed in through Google and Apple logins. Keplr suspended those methods after a breach at authentication provider Web3Auth exposed private keys tied to certain accounts. Blockchain investigators traced more than $6 million in transfers involving over 44,000 wallets. That breach struck the authentication layer — unlike Paytaca's case, where the advisory states keys remained on user devices.

Hardware wallet maker Trezor disclosed its own incident on November 16: a data breach at shipping partner Skladon exposed information tied to roughly 27,000 orders, including names, addresses, contact details and purchase records. Trezor said wallet devices and recovery backups were not compromised, though some customers later reported scam calls.

What happens next?

Paytaca said it is strengthening security measures and monitoring its systems for suspicious activity. It has not announced a timeline for completing the investigation or a date for publishing a technical breakdown of the two vulnerabilities. Until that post-mortem arrives, users face an open-ended window in which unsolicited payment requests remain the primary attack vector.

via crypto.news (Source)

More from Tom Whitfield

Tom Whitfield

Show full bio

News editor covering technology and product news in crypto and web3 industry at Mempool Brief.

1,374 articles