On October 30th, Aqua Wallet, an application that allows you to store and manage Bitcoin (BTC), suffered a distributed denial of service (DDoS) attack.
This fact was reported by Samson Mo, executive director of Jan3, the company that develops Aqua Wallet, through his social network X (formerly Twitter) account.
“We suffered a DDoS attack,” Mo said. backend “The Dolphin Card was discontinued earlier today,” but added that “Aqua’s core business was not affected.”
Dolphin Card is a rechargeable virtual card created by the Aqua Wallet team and tested by CriptoNoicias.
Mow then provided further details on the status of Aqua’s services, including the suspension of new Dolphin card production.
Card service was restored shortly thereafter. New card creation has been temporarily disabled and will be reinstated later today. Creating new cards will remain disabled for a while. To counter current attacks, more sophistication must be implemented. Existing Dolphin cards will work correctly.
Samson Mow, Jan3 CEO
This allows executives to You can continue using your card without any problemsMeanwhile, the Aqua team is developing additional countermeasures to strengthen the system’s resistance to similar attacks.
What is a “DDoS” attack and what impact did it have? backend Aqua card?
DDoS attacks occur when multiple computer systems are present. Send large numbers of requests at the same time Send to server for
This type of attack is not aimed at compromising data or accessing funds; Suspend the operation of online services.
he backend The “Dolphin Card” Mow was referring to refers to the technical infrastructure that handles the operations of the Dolphin Card, an Aqua Wallet card that allows users to make payments with Bitcoin.
Samson Mo does not elaborate on how it happened, but from his description it is possible to deduce how it happened.
One possibility is that the attacker Sent thousands of fake orders to create new cardstemporarily blocking that functionality.
Another option is causing excessive consumption of server resources (memory, processing power, etc.) until the system stops responding.
That might have been too Network traffic saturation This affected communication with the server.
Finally, it is possible that If you abuse the card creation processforcing repeated operations that overload the system. In all cases, the objective was the same. That means disrupting service, not stealing funds or compromising user data in wallets.