Bitcoin Cash Wallet Paytaca Reports Two Cyberattacks on Consecutive Days
Paytaca says attackers exploited two backend vulnerabilities on November 17 and 18, creating fake peer-to-peer orders and unauthorized payment requests. The company says users’ private keys were not compromised. It has not said how many users were affected or whether anyone lost funds.
- One flaw affected Paytaca’s P2P Ramp; another enabled unauthorized payment requests.
- Paytaca has not released a technical breakdown or confirmed whether any requests led to payments.
- Reject unexpected requests and check transaction details before authorizing a transfer.
Two backend vulnerabilities, two types of fraudulent requests
In a security advisory published on November 18, Paytaca said the first attack exploited a vulnerability in the backend for its P2P Ramp, the company’s peer-to-peer service. Attackers used the flaw to create fraudulent orders. A separate vulnerability was exploited the following day, allowing unauthorized payment requests through another part of Paytaca’s backend.
Paytaca has not explained how either vulnerability worked or what the requests looked like to users. It has not identified the attackers or said whether the incidents were linked.
The company says its security team is investigating, fixing the vulnerabilities, strengthening safeguards, and monitoring for suspicious activity. It has not said how many fraudulent orders or requests were created, how many users were affected, or whether any requests led to completed payments.
That distinction matters. Creating a fraudulent request is a serious security failure, but it does not prove that money was stolen.
What Paytaca says about users’ keys
Paytaca says users’ private keys stay on their devices and are not stored on its backend servers. The company says the attacks did not compromise those keys. So far, it has not released an independent forensic report confirming the scope of either incident.
A private key is the cryptographic credential used to authorize a cryptocurrency transfer. With a self-custodial wallet, the user controls the key, not the service provider. Paytaca said that “moving funds requires cryptographic signatures generated using users’ private keys.”
An unauthorized payment request cannot, by itself, authorize a transfer. The wallet must approve it, usually after the user confirms the transaction. But self-custody does not protect users from deception. A compromised service can create misleading requests, and a user could still approve a transaction without noticing that the destination is wrong.
How Paytaca users can reduce risk
Paytaca advised users to ignore suspicious P2P orders and payment requests, avoid approving unfamiliar transactions, check transaction details before signing, and never disclose recovery phrases or private keys.
A recovery phrase is a set of words that can restore access to a wallet. Anyone who gets the phrase may be able to take control of the funds. Legitimate support staff should never ask users to send it.
If you receive an unexpected request, open Paytaca directly instead of following a link in a message. Before approving a transaction, check the destination address and amount on the confirmation screen. Follow Paytaca’s official channels for updates, and do not trust unsolicited messages claiming to come from support.
A separate example: malicious scripts and address substitution
The Paytaca incidents involved its backend. Another incident shows how attackers can target a different part of the payment process: the website that displays a cryptocurrency address. Crypto.news, citing StepSecurity and researcher Scott Helme, reported malicious JavaScript associated with Optimizely-hosted scripts on 186 websites. The scripts could replace cryptocurrency addresses on websites with attacker-controlled addresses and targeted eight cryptocurrencies, including Bitcoin, Ethereum, and Bitcoin Cash.
StepSecurity reportedly traced about $6, 600 in activity and holdings across four associated wallets. That figure is not a confirmed loss total from the incident. Some transactions predated the attack, and the reported holdings do not show that the funds came from victims. The Optimizely-hosted scripts were also described as capable of card skimming.
There is no evidence that this activity was connected to the Paytaca attacks. It points to a separate risk: a wallet can correctly sign a transaction that sends funds to the wrong address if malicious code changes the address a user sees or copies. A valid signature confirms that the keyholder authorized the transaction. It does not prove the recipient is legitimate.
Another crypto wallet security incident involving a Web3Auth vulnerability shows that risks can arise at different points in the wallet stack.
Key questions about the Paytaca attacks
-
What happened to Paytaca?
Paytaca said vulnerabilities exploited on November 17 and 18 enabled fraudulent P2P orders and unauthorized payment requests. The advisory account available so far does not specify the year.
-
Were users’ private keys compromised?
Paytaca says they were not and that the keys remain on users’ devices. The company has not disclosed an independent forensic report confirming the scope.
-
Are financial losses confirmed?
The available information does not show whether users lost money. Paytaca has not said how many requests were created or whether any were paid.
-
Can a payment request authorize a transfer by itself?
No. The wallet must authorize a transfer, but a user could still be tricked into approving an unexpected or deceptive request.
-
What should users do?
Reject unfamiliar requests, open the app directly, check the destination address and amount before approving a transaction, and never share recovery phrases or private keys.
-
What remains unknown?
Paytaca has not disclosed how many users were affected, whether any requests led to losses, how the flaws were exploited, or when it will publish a technical postmortem.
Paytaca’s assurance about private keys matters, but it does not answer every question about the incidents. A technical postmortem covering the scope, fixes, and remaining safeguards would help users assess the risk. Until then, treat unexpected payment requests as untrusted and verify the details before authorizing anything. For context on Bitcoin Cash price coverage, see Bitcoin Cash predictions and the BlockchainFX presale.