Hardware Ready Ready to Bench?
On November 3, Gnosis Pay announced that it had detected unauthorized access to its computer system. The incident specifically concerns the legacy system supporting branded cards, also known as white label, issued by the company for its B2C business line. According to reports from Protos, the intrusion led to the exposure of sensitive personal and financial information belonging to customers. The company clarified that the event was limited to this specific system, while other components of the platform were not affected.
Why it matters
The incident highlights residual vulnerabilities in cryptocurrency-related payment systems, particularly when these operate on legacy infrastructure. Gnosis Pay clarified that customer funds remained safe and that the enterprise platform, intended for businesses, was not compromised. However, the exposure of data such as names, physical addresses, card numbers, and wallet addresses represents a concrete risk to end users in terms of privacy and potential phishing. The distinction between the breached B2C system and the intact enterprise system is fundamental to understanding the limited scope of the attack, which did not jeopardize corporate transactions or digital wallet balances.
The numbers
Available sources do not report the exact number of customers affected by the breach. Protos cites the event as a single announced violation. The exposed data varied depending on the user: while some had only their name, shipping address, and account reference compromised, others, as reported by Rotki founder Lefteris Karapetsas, also lost their card number and all wallet addresses linked to their account. This variability in exposed data suggests that the unauthorized access may have hit databases with different levels of informational detail for each individual customer registered on the legacy system.
What remains to be understood
At present, it has not been confirmed whether there were any further operational consequences beyond the loss of data. Gnosis Pay stated that the affected system was already scheduled for decommissioning by the end of the year, but no precise temporal details were provided regarding the closure of the legacy service relative to the incident. The company did not immediately respond to additional comment requests from the press, leaving some technical aspects of the intrusion not yet publicly clarified. Exact timelines for the complete deletion of sensitive data from servers and specific measures adopted to notify all potentially involved users uniformly remain to be defined.
Sources: Decrypt, Cointelegraph, Protos.
This article is for informational purposes only and does not constitute financial advice or an investment recommendation.
* Content created with the assistance of artificial intelligence systems.