0x3778c5983778…3778c595
Paytaca Wallet Hit by Backend Exploits Creating Fake P2P Orders
Paytaca says Nov. 17-18 backend exploits created fake P2P orders and unsolicited payment requests, while user private keys stayed safe on devices.

Outputs
Paytaca reported backend exploits on Nov. 17 and Nov. 18, 2024-era incidents creating fake P2P orders and unsolicited payment requests.
The Nov. 17 attack exploited a vulnerability in the P2P Ramp backend to generate fake orders.
The Nov. 18 attack abused a separate backend flaw to produce payment requests users never initiated.
Private keys were not directly involved; they are stored on users' devices, not Paytaca's servers.
Paytaca is investigating and fixing the vulnerabilities and warns users not to sign transactions they did not initiate.
Self-custody Bitcoin Cash (BCH) wallet Paytaca reported two backend exploits on Nov. 17 and 18 that generated fake peer-to-peer trading orders and unsolicited payment requests across its platform. The company confirmed both incidents targeted its backend infrastructure, not user-held private keys, which remain stored on customers' devices rather than Paytaca's servers.
The first attack came on Nov. 17, when a vulnerability in Paytaca's P2P Ramp backend was exploited to create fraudulent orders. A day later, on Nov. 18, attackers abused a separate backend flaw to push payment requests that users had never initiated.
The operational failure sits in the wallet's trading and onboarding rails, not its custody architecture. Because Paytaca is a self-custody product, the attackers could not directly access private keys — the cryptographic credentials that control funds. Instead, the exploits manipulated the order and request layers that sit between users and counterparties, creating records that appear legitimate inside the app's interface.
What should users do now?
Paytaca urged users to treat any P2P order or payment request they did not initiate as suspicious. The company's core security guidance is blunt: do not sign transactions you did not start. A digital signature is the act that moves funds in a self-custody wallet, so a user who approves a crafted request — even one injected by a compromised backend — authorizes the transfer from their own device.
The warning highlights a structural risk in wallet design that extends beyond Paytaca. Self-custody removes the server-side honeypot of custodied keys, but the backend that feeds a wallet's interface can still shape what users see and are asked to approve. In this case, that surface was the P2P Ramp service and the payment-request channel.
What is the company doing about it?
Paytaca said it is investigating both exploits and working to fix the vulnerabilities. The company has not disclosed how many accounts received fake orders or payment requests, whether any users signed the fraudulent requests, or whether funds were lost as a result. It also did not state whether the two vulnerabilities were related or exploited by the same actor.
The timeline leaves several operational questions open. Paytaca has not said when the flaws were introduced, how long they existed before the Nov. 17 exploitation, or what remediation steps — such as patches, order invalidation or credential rotation — are already in place.
For users, the immediate exposure is narrower than a key compromise but still real: a signed transaction is irreversible on-chain. The practical defense until Paytaca confirms full remediation is behavioral, verifying every order and request before signing, and treating any unexpected prompt as hostile.
The company's next communication, including a fix confirmation or an incident report with scope figures, will determine whether this remains a spoofing incident or escalates into a confirmed loss event.
via tokenpost.com (Source)
More from Tom Whitfield
Show full bio
News editor covering technology and product news in crypto and web3 industry at Mempool Brief.
1,374 articles