TrendCrypt News

Gnosis Pay Breach Links Home Addresses to Crypto Wallets

Gnosis Pay says funds were safe after a consumer card data breach, but exposed card details and linked crypto wallets create serious privacy and phishing risks.

Published 2026-11-13
Updated 2026-11-13
Publisher Ananthi Reeta
Gnosis Pay Breach Links Home Addresses to Crypto Wallets

A crypto debit card can keep its users’ cryptocurrency safe and still expose something difficult to recover: the connection between their real identities and their blockchain wallets.

That is the concern following a data breach disclosed by Gnosis Pay on November 6, 2026.

The company confirmed that attackers gained unauthorized access to the system powering its consumer debit cards on November 3, exposing certain customer information.

Gnosis Pay says customer funds were not affected and its separate enterprise card platform remained secure.

But the information reportedly exposed in individual breach notifications goes beyond ordinary account details.

It includes payment-card numbers, expiration dates, security codes, names, home addresses, and cryptocurrency wallet addresses linked to customer accounts.

Some notifications also identified email addresses, telephone numbers, nationality information, and banking details.

The exact information exposed differs between customers.

Gnosis Pay has not disclosed the total number of affected people.

The incident creates a particular security problem for users of cryptocurrency-linked financial services.

A blockchain wallet address is public information. But when a data breach connects that address to a person’s name, home address, and payment history, information that was previously difficult to associate with an individual can become much easier to exploit.

An attacker may not need access to the wallet’s private keys to cause harm.

The stolen information could support convincing phishing messages, card-fraud attempts, impersonation, or targeted efforts to obtain cryptocurrency.

That does not mean those secondary attacks have already occurred.

It means the exposed information can remain useful to criminals after the original vulnerability has been fixed.

Gnosis Pay says it began containing the breach within two hours of detecting it, replaced affected security credentials, and addressed the vulnerability.

It also made 3D Secure authentication mandatory for online card payments and increased monitoring of card and wallet activity.

The breach comes shortly before the company’s already-planned retirement of its consumer-branded cards on December 20.

That closure is a separate business decision announced in September, not a newly announced response to the breach.

For affected customers, the immediate questions are practical.

What information was exposed? Can stolen card details still be abused? Are linked cryptocurrency wallets at risk? And what happens to funds when the old card program closes?

Key Takeaways

  • Gnosis Pay detected unauthorized access on November 3, 2026, and publicly disclosed the breach on November 6.
  • The incident affected its legacy consumer card system. Gnosis Pay says its separate enterprise infrastructure powering white-label card programs was not affected.
  • Customer funds were not affected, according to the company. The confirmed incident involved exposure of customer information rather than a reported theft of wallet balances.
  • Reportedly exposed data includes payment-card information and linked crypto wallet addresses. Individual notifications also identified names, home addresses, and other personal or financial details.
  • The number of affected customers remains undisclosed. Reported data categories should not be interpreted as information exposed for every cardholder.
  • The company began containment within two hours, replaced affected security credentials, and says it addressed the vulnerability.
  • 3D Secure authentication is now mandatory for online card payments on the affected consumer system until its planned retirement.
  • Gnosis Pay-branded consumer cards stop working on December 20, 2026. That shutdown was announced before the breach.
  • Self-custodial funds are not scheduled to disappear. Gnosis Pay says users retain control of their Safes, with withdrawal functionality continuing after the consumer web app closes for other purposes.
  • The most serious long-term risk may involve identity and wallet linkage. Changing a card does not erase information already exposed, and moving crypto does not automatically break its historical blockchain connections.

What Happened to Gnosis Pay?

Gnosis Pay provides infrastructure allowing eligible users to spend cryptocurrency through payment cards.

Its legacy consumer offering connects a Visa debit card with a self-custodial Safe account on Gnosis Chain.

The card system therefore interacts with two financial environments.

One is the blockchain, where cryptocurrency can remain under the user’s control.

The other is the traditional payment-card ecosystem, which requires customer information, card credentials, identity verification, and transaction processing.

The November incident affected the second environment.

Unauthorized access detected November 3

According to Gnosis Pay’s official statement, monitoring systems detected unauthorized access to the infrastructure powering the company’s branded consumer cards.

Its security team began containment within two hours.

The company subsequently replaced affected security credentials and addressed the identified vulnerability.

It did not publicly identify the attacker.

It also did not publish a complete technical explanation of how the unauthorized access occurred.

The available evidence therefore does not justify claiming that a particular employee account, software component, or payment processor was responsible.

Customers notified November 6

Gnosis Pay published its public disclosure on November 6.

It said every affected customer had been emailed with information about what was exposed from their account.

The company also notified relevant partners and its card issuer and began communicating with applicable data-protection authorities.

It did not disclose how many people received those notifications.

Incident timeline

Gnosis Pay Security and Consumer-Card Timeline

DateEventWhat It Means
June 1, 2026Earlier Gnosis Pay smart-contract exploitApproximately $1.5 million stolen in a separate incident; losses subsequently covered
September 21, 2026Consumer card closure announcedDecember 20 retirement scheduled independently of the later data breach
November 3, 2026Unauthorized access detectedLegacy Gnosis Pay consumer-card system compromised
November 3, 2026Containment beginsCompany says its response began within two hours
November 6, 2026Public disclosure and customer notificationsAffected customers emailed; mandatory online 3D Secure announced
November 7, 2026Breach impact receives wider attentionReported notifications describe exposed cards, identity details and linked wallets
December 20, 2026Scheduled consumer card retirementBranded cards and most legacy web-app functions cease; withdrawals continue

The timeline makes two distinctions clear.

The November data breach is separate from the June smart-contract exploit.

And the December consumer-card shutdown had already been announced before the November incident.

Neither event should be used to imply a causal relationship that the company has not established.

What Customer Information Was Exposed?

Gnosis Pay’s official disclosure confirms exposure of certain customer information.

However, the company’s public statement does not provide a complete universal list of compromised data fields.

Instead, it says affected customers received individualized notices describing what was taken from their accounts.

Public reporting provides additional detail.

Payment-card numbers and security codes

Cointelegraph reported reviewing breach notifications identifying full card numbers, expiration dates, and CVV security codes among the exposed information.

These details are more sensitive than the last four digits commonly shown in a payment confirmation.

Depending on the circumstances, a combination of card information can assist fraudulent online payment attempts.

That does not mean every attempt would succeed.

Payment systems can impose additional checks, and card issuers can restrict compromised credentials.

But the exposure warrants attention.

Names, addresses and contact information

Reported notices also included customer names, residential addresses, email addresses, and phone numbers.

Some contained nationality information and bank account identifiers such as IBAN and BIC details.

These are different categories of information with different risks.

A bank account identifier is not the same as a banking password.

An email address is not sufficient to access a wallet.

But combinations of personal and financial information can make social engineering more effective.

Cryptocurrency wallet addresses

The most distinctive part of the breach concerns wallet addresses linked to cardholder accounts.

One affected customer, the founder of cryptocurrency portfolio tracker Rotki, publicly reported that the exposed information included his home address, card number, and every wallet address linked to his Gnosis Pay account.

That account illustrates the potential privacy impact.

However, it does not establish that every affected Gnosis Pay user had the same wallet information exposed.

The company says it provided individualized data-exposure details.

What remains unknown?

Gnosis Pay has not publicly disclosed:

  • The total number of affected customers.
  • A complete technical root-cause analysis.
  • The identity of the attacker.
  • A universal list of compromised fields applying to every account.
  • Evidence establishing that every affected card experienced fraudulent payments.
  • Evidence of private-key theft arising from this particular breach.

Those gaps matter.

The absence of a reported wallet theft should not minimize the data exposure.

But the existence of sensitive leaked information should not be exaggerated into a claim that all user funds were stolen.

Gnosis Pay Breach: Reported Data Exposure

InformationReported StatusPotential Consequence
Full payment-card numberIdentified in reported individual notificationsPotential card fraud and convincing impersonation
Card expiration and security codeIdentified in reported individual notificationsAdditional information that may assist fraudulent payment attempts
Name and home addressIdentified in reported individual notificationsIdentity targeting and association with crypto holdings
Linked cryptocurrency wallet addressesIdentified in reported individual notificationsPublic blockchain activity may become attributable to a person
Email address and phone numberIdentified in reported individual notificationsPersonalized phishing and impersonation
Nationality and bank detailsReported for some affected accountsAdditional identity and financial-information exposure
Recovery phrase or private keyNot reported as exposedNo disclosed evidence of direct key compromise in this incident
Total affected customer countNot disclosedCannot reliably calculate the scale from available information

Why Linking a Home Address to a Crypto Wallet Is Dangerous

Cryptocurrency wallets introduce an unusual privacy problem.

On public blockchains, transactions and addresses are generally visible.

Anyone can inspect many types of onchain activity without accessing the owner’s private keys.

However, the identity of the person controlling a particular address may not be publicly known.

A data breach can change that.

What a wallet address reveals

Consider an Ethereum-compatible address associated with a person’s card account.

Depending on the blockchain and the address’s activity, observers may be able to examine token balances, transaction history, contract interactions, and transfers involving other addresses.

That information may not identify the owner by itself.

But a leaked customer record can supply the missing connection.

If the record links a person’s name and home address to the wallet, blockchain activity becomes easier to associate with that individual.

How one address can reveal additional information

Suppose a cardholder uses one wallet for everyday spending.

That wallet receives funds from another address used for long-term storage.

The public blockchain may show a relationship between those addresses.

An attacker who knows which address belongs to the cardholder can investigate the wider transaction history.

That does not automatically prove every connected address belongs to the same person.

Some transfers involve exchanges, businesses, or other counterparties.

But the starting point provides information that was not previously available.

A wallet address can therefore act as a link between personal identity and broader financial activity.

Why card purchases add context

A payment-card provider may hold information about card transactions alongside identity and account data.

Gnosis Pay warned customers that fraudulent messages might refer to genuine purchases.

Such details can make impersonation more believable.

For example, a scammer might reference a real transaction and claim that the customer must complete an urgent security check.

The message can feel authentic because it includes information the victim recognizes.

The attacker does not need to know the recovery phrase at that stage.

The objective may be to persuade the victim to disclose it later.

The risk can persist after the breach is fixed

Replacing compromised credentials and patching the vulnerable system can stop the same technical access route.

But information already copied may remain outside the company’s control.

A card can be canceled.

A password can be replaced.

A wallet owner can create a new address.

However, information connecting an individual to historical blockchain activity cannot necessarily be erased from the public ledger.

This is one reason financial-data breaches can create lasting risks even when immediate funds remain safe.

Does the Breach Mean Gnosis Pay Wallets Were Hacked?

No direct compromise of user wallet keys was established by the November disclosure.

Gnosis Pay says customer funds were unaffected.

The publicly confirmed incident concerns unauthorized access to information in its consumer-card infrastructure.

That is different from an attacker obtaining a wallet’s signing authority.

Public wallet addresses are not private keys

A public address identifies a blockchain destination.

It can be used to inspect public transactions and receive assets.

Knowing an address does not ordinarily provide the cryptographic authority needed to spend funds controlled by that wallet.

Private keys or valid transaction authorizations perform that function.

Therefore, exposure of a wallet address is not equivalent to exposure of the wallet’s recovery phrase.

But exposure can enable a second attack

A criminal who knows a person’s identity and wallet address may attempt phishing.

The message might claim:

  • A card needs immediate replacement.
  • A Safe account must be upgraded before December 20.
  • Funds will become inaccessible unless moved.
  • A new security rule requires signing a verification message.
  • The customer must enter their recovery phrase to connect to a partner card.

Those claims can exploit real details from the breach and the planned consumer-card closure.

The dangerous step would be the user’s subsequent action.

For example, entering a recovery phrase into a fake site could compromise a wallet.

Signing a malicious transaction could move funds.

Granting an unsafe token approval could permit an attacker-controlled contract to spend certain assets.

These are potential follow-on attacks, not events established by Gnosis Pay’s November disclosure.

Our crypto wallet phishing guide explains how legitimate-looking security messages are used to obtain wallet access or dangerous authorizations.

Gnosis Pay: Data Exposure vs Wallet Compromise

RiskWhat It Can CauseWhat the Evidence Establishes
Card-data exposurePayment credentials may be misusedMonitor payments and contact the issuer about card replacement or restrictions
Personal-data exposureScammers can produce more believable identity-based requestsVerify communications through authenticated official channels
Wallet-address exposurePublic addresses may be linked to a real-world identityReview public wallet visibility and avoid unnecessary cross-linking
Private-key theftAttacker may be able to control wallet assetsNo such theft established by this breach disclosure
Malicious wallet approvalA contract may gain permission to move specific assetsRequires separate interaction or existing authorization; not established here
Phishing after the breachVictim may be tricked into disclosing secrets or signing transfersTreat unexpected security and migration instructions as suspicious

Why Mandatory 3D Secure Matters

Gnosis Pay says it made 3D Secure verification mandatory for online payments on the affected consumer system.

The requirement will remain in place until the legacy consumer platform is retired as planned on December 20.

3D Secure is an additional authentication mechanism used in card-not-present payments.

It can require the cardholder to complete an authentication step before an eligible online payment is approved.

What problem does it address?

If someone obtains a card number, expiration date, and security code, they may attempt an unauthorized internet purchase.

3D Secure can introduce an additional verification requirement that makes certain fraudulent transactions more difficult.

That is a relevant response when card credentials may have been exposed.

Does 3D Secure make stolen card details harmless?

No.

Not every payment transaction follows the same authentication path.

Payment authorization can involve different merchants, jurisdictions, transaction types, exemptions, and card-network arrangements.

3D Secure also does not prevent every form of phishing or social engineering.

A scammer could attempt to deceive a user into approving an authentication request.

The protection is meaningful, but it should not be described as a universal guarantee against payment fraud.

Why cardholders should still monitor transactions

An affected customer should review their transaction history and follow the account-specific instructions supplied through authenticated channels.

If full payment-card details were exposed, the customer can ask the card issuer or Gnosis Pay about replacement, cancellation, restrictions, and disputed payments.

The appropriate action may depend on whether the card was already canceled and what information was compromised.

At least one publicly reported notification indicated that the affected customer’s card had been canceled.

That does not establish that all affected cards were automatically canceled.

Did the Breach Affect Gnosis Pay’s Enterprise Platform?

Gnosis Pay says it did not.

The company distinguishes between two parts of its business.

The affected system powers its own branded consumer cards.

The separate enterprise platform provides white-label card infrastructure for other businesses.

Those businesses can include cryptocurrency wallets, fintech companies, and other financial service providers.

Why that distinction matters

A company can operate several systems under one commercial brand.

An incident affecting one product does not automatically establish that every other product was compromised.

Gnosis Pay specifically states that its enterprise infrastructure was not affected.

That is the company’s confirmed position as of the November 6 disclosure.

Does that mean every partner-card account is completely safe?

The disclosure does not establish a compromise of the separate enterprise platform.

It also does not constitute a complete independent security audit of every partner program.

The supported conclusion is narrower: Gnosis Pay reports that the November unauthorized access was limited to the legacy consumer-card system.

Customers using partner applications should follow the relevant provider’s official information rather than assume they received the same exposure as legacy branded cardholders.

Why the legacy architecture is important

Gnosis Pay had already decided to concentrate its business on partner card programs.

Its September closure notice explains that operating the legacy consumer interface alongside the newer enterprise infrastructure was no longer part of its preferred strategy.

The new platform is designed to offer improved operational controls, privacy features, and card management capabilities.

But the planned business transition does not erase the responsibility to protect information retained within the older system.

The November breach illustrates why legacy infrastructure remains security-relevant until it is properly retired.

The December 20 Shutdown Was Already Planned

The timing of the breach could create confusion.

Gnosis Pay’s branded cards are scheduled to stop working on December 20, 2026.

That date was announced on September 21, before the November incident.

It was not newly introduced because customer information was exposed.

The distinction matters because a scammer could claim otherwise.

For example, a fraudulent message might say the breach forced an emergency migration and direct customers to a fake website.

That would misrepresent the published schedule.

What stops working?

At 23:59 UTC on December 20, Gnosis Pay’s legacy physical and virtual branded cards are scheduled to stop authorizing new payments.

The consumer web app will also close for most purposes.

However, its withdrawal functionality is intended to remain available.

What happens to the cryptocurrency in the Safe?

According to the official closure notice, the user’s Safe remains a self-custodial smart-contract account on Gnosis Chain.

The assets in that account remain under the user’s control.

The end of the card program does not automatically confiscate those assets.

Nor does it create a December 20 deadline for withdrawing them.

Gnosis Pay states that users can continue accessing their Safes through the appropriate withdrawal functionality or a compatible Safe interface.

The user still needs the relevant signing authority.

What about subscriptions?

Recurring payments linked to the retired card will fail after the closure.

Cardholders should update payment details directly with affected merchants.

They should also export their transaction history before the broader web-app closure.

That history may be useful for refunds, disputes, or chargebacks.

What about moving to a partner program?

Migration is optional.

A partner card is not simply a continuation of the same customer agreement.

The user may need to accept new terms, complete onboarding requirements, and establish a new Safe.

Fees, supported assets, payment limits, and eligibility can differ.

Customers should review the relevant official documents before moving funds.

Gnosis Pay's December 20 Closure: What Stops and What Continues

Service or RightPublished PlanPractical Effect
Branded physical and virtual cardsStop working December 20Cannot authorize new card payments after retirement
Legacy web appMost functions close December 20Withdrawal functionality remains available
Self-custodial SafeRemains controlled by the userAssets are not automatically confiscated or transferred
Existing subscriptionsPayments using retired cards will failUpdate merchant payment details before the shutdown
Transaction historyDownload before December 20Useful for future refunds and disputes
General cardholder supportScheduled to end June 18, 2027Different from ongoing statutory complaint rights
Refund, dispute and chargeback supportScheduled to end June 12, 2028Applicable card and statutory rights have their own requirements

Who Is Responsible for the Card and the Crypto?

Gnosis Pay’s closure notice identifies an important legal distinction.

The branded consumer card is issued through Monavate.

For UK and other applicable non-EEA customers, the relevant issuer is Monavate Ltd, an electronic money institution authorized by the UK Financial Conduct Authority.

For EEA customers, the issuer is UAB Monavate, supervised by the Bank of Lithuania.

Gnosis Pay acts as the card program manager and technical service provider.

Meanwhile, the user’s Safe holds the relevant digital assets under a self-custodial arrangement.

These roles should not be conflated.

Payment-card rights

A dispute about an unauthorized card payment may involve the licensed card issuer and applicable payment-services rules.

Card scheme protections and national consumer rights can also be relevant.

The particular rights depend on the jurisdiction and contractual arrangement.

Self-custodial cryptocurrency

Cryptocurrency held in a Safe is not equivalent to a conventional card account balance controlled by the issuer.

A user can retain signing authority over the underlying smart-contract wallet.

That does not remove all risks, including software vulnerabilities and malicious signatures.

But it explains why shutting down a card program does not automatically remove access to the associated cryptocurrency.

Personal-data responsibilities

A data breach involving cardholder records can involve several responsible parties.

Gnosis Pay says it notified its card issuer and relevant data-protection authorities.

However, the November statement does not provide a completed regulatory determination concerning legal responsibility or penalties.

It would be premature to state that any authority has found a particular violation or imposed a fine arising from this incident.

This Is Not Gnosis Pay’s First Security Incident in 2026

In June 2026, Gnosis Pay experienced a separate security incident involving software modules used by its card-linked Safe infrastructure.

Attackers exploited a flaw involving the Zodiac Delay and Roles modules.

The July 3 postmortem published by Gnosis reported that attackers extracted approximately $1.5 million.

An additional amount became temporarily inaccessible during the incident.

Gnosis says it absorbed the losses and restored customer funds.

The June attack affected assets

The earlier vulnerability concerned smart-contract authorization behavior.

It allowed unauthorized activity affecting card-linked wallets.

That is a direct financial-security problem.

The November breach affected information

The November incident concerns customer-data exposure within the legacy consumer-card system.

Gnosis Pay says funds were unaffected.

There is no public evidence establishing that the November breach used the same technical vulnerability as the June exploit.

Nor is there enough information to conclude that the same attacker was responsible.

Why both incidents matter

The two incidents illustrate different security boundaries within a crypto payment product.

The first involves the ability to move cryptocurrency.

The second involves the ability to access sensitive customer information.

A company can successfully protect one boundary while failing at another.

The user experience combines them.

Someone using a cryptocurrency card depends on both financial security and personal-data protection.

That is why a review limited to whether funds were stolen would overlook an important part of the November incident.

How a Data Breach Can Lead to a Wallet Drainer

The next stage of risk may occur outside the originally compromised system.

An attacker could use leaked customer information to create a convincing fraudulent message.

Consider a hypothetical example.

A Gnosis Pay cardholder receives an email claiming their card must be migrated before December 20.

The message includes the person’s real name and the last four digits of their card.

It may also reference a wallet address or previous payment.

The email directs the user to a website resembling the official card application.

The website asks the user to connect their wallet and approve a migration transaction.

The request may actually authorize movement of tokens or create a spending permission for an attacker-controlled contract.

Why real details do not prove authenticity

A convincing phishing message can contain completely accurate personal information.

That information may have come from a breach.

Its accuracy does not prove the sender is legitimate.

This was also a central issue in TrendCrypt’s earlier coverage of Revolut’s fraudulent government-email data disclosure.

In the Revolut case, attackers used a trusted communication channel to obtain customer records.

In the Gnosis Pay case, the issue is unauthorized access to a legacy card system.

The technical incidents differ.

But both demonstrate how personal-data exposure can increase the credibility of subsequent fraud attempts.

Why wallet approvals are particularly dangerous

A website does not necessarily need a recovery phrase to steal cryptocurrency.

Some attacks rely on authorized token allowances or malicious signatures.

A wallet owner may believe they are confirming a harmless security check.

In reality, the request can grant permission to move assets.

Our guide to checking and revoking wallet approvals explains how to inspect these permissions and why disconnecting a website does not necessarily revoke previously granted spending authority.

Importantly, the Gnosis Pay disclosure does not establish that such a secondary attack has already occurred.

It makes this threat more relevant because attackers may possess credible personal details.

What Affected Gnosis Pay Customers Should Do

The appropriate response depends on what was actually exposed.

A customer whose email address was disclosed faces a different immediate risk from someone whose full card credentials and linked wallet addresses were exposed.

Gnosis Pay says it sent individualized notices.

Those should provide the starting point.

Gnosis Pay Data Breach: Practical Customer Response

SituationRecommended ActionImportant Distinction
Received a breach notificationRead the exact data categories and follow verified account-specific guidanceDifferent customers may have different exposure
Payment-card details exposedReview transactions and request card-specific protection from the issuer3D Secure is not a universal guarantee against fraud
Wallet address exposedAssess privacy exposure and watch for suspicious activityA public address alone cannot authorize a transfer
Unexpected account or card messageOpen the official service independently rather than using message linksReal personal details do not establish authenticity
Suspicious wallet signatureReview transaction history and existing permissions using trusted toolsDo not sign a new verification request from a stranger
Seed phrase disclosed separatelyTreat the wallet as compromised and use a verified recovery procedureThis is a different and more serious exposure
Planning card migrationReview the official September closure notice and partner requirementsMigration is optional and new card programs have separate terms

Review the individualized notice

Check which information Gnosis Pay says was affected.

Do not assume every reported field applies to your account.

If you are uncertain about an email, open the company’s official website independently rather than using a link inside the message.

Gnosis Pay has published the incident announcement on its official site.

Review card transactions

Look for payments you do not recognize.

If an unauthorized transaction appears, preserve the relevant records and contact the appropriate official support or card issuer.

Ask about card restrictions, replacement, and available dispute procedures.

For cardholder complaints and payment-service rights, the official closure notice identifies Monavate as the relevant issuer.

Be cautious with verification requests

Gnosis Pay explicitly states that it and its partner applications will not request seed phrases, private keys, PINs, or full card numbers through unsolicited communications.

They also will not ask users to move funds through an email, text message, or telephone call.

A message demanding those actions should be treated as suspicious even if it includes real account information.

Review wallet privacy

If wallet addresses were exposed, consider what public information those addresses reveal.

A public address alone does not permit someone to spend the funds.

However, it may allow observers to associate transactions and balances with the customer’s identity.

Avoid publishing additional information connecting personal identity to valuable wallets.

Where appropriate, consider using separate addresses or wallets for different financial purposes.

But understand that moving funds to another address does not automatically erase the historical relationship between the addresses.

Do not automatically migrate every wallet

The November breach is not, by itself, evidence that every user’s private keys were compromised.

Moving all cryptocurrency in response to a public address leak may create additional transaction risks without resolving the underlying privacy exposure.

A full wallet migration may be appropriate if there is separate evidence that signing keys or recovery material were disclosed.

That is a different incident-response scenario.

Preserve useful records

Keep copies of the official breach notice and relevant correspondence.

Preserve evidence of suspicious card transactions or impersonation attempts.

For the December closure, download the legacy card transaction history before the published deadline.

Avoid sharing full card credentials, identity documents, or recovery phrases in public discussions about the breach.

Does Changing the Card Fix the Privacy Exposure?

Replacing a compromised card can reduce the usefulness of exposed payment credentials.

That is a meaningful protective measure.

But it does not erase other information that may have been copied.

Card credentials can be replaced

A card number and security code can be made unusable through cancellation or replacement.

The issuer can also apply fraud monitoring and transaction restrictions.

Those actions help address card-payment risk.

Personal information is harder to replace

A person cannot easily change their legal name or residential history.

A home address can change, but previous exposure may remain relevant.

Email addresses and phone numbers can be replaced, although doing so may be disruptive.

An attacker may also combine the exposed information with data from other sources.

Blockchain history is persistent

A public blockchain’s historical transactions do not disappear when the owner creates a new address.

Moving funds can create another visible transaction.

An observer may use the relationship to investigate the original wallet’s activity.

The exact privacy impact depends on the blockchain, the transaction pattern, and the information available.

This is why unlinking identity from cryptocurrency activity can be more complicated than simply replacing a bank card.

For crypto payment providers, limiting the collection, retention, and exposure of sensitive linkage data is an important design concern.

Why Self-Custody Does Not Solve Every Financial Privacy Problem

Gnosis Pay’s legacy product uses self-custodial Safe accounts.

That arrangement gives users direct control over their assets.

It can reduce dependence on a card provider’s ability to authorize ordinary blockchain withdrawals.

But self-custody does not automatically prevent a card operator from holding personal information.

Payment cards require offchain data

Card programs operate within regulated financial infrastructure.

They may need identity verification, payment records, account information, and compliance data.

That information exists outside the blockchain.

A user may retain custody of their cryptocurrency while the card service stores sensitive personal records.

These are separate security responsibilities.

What self-custody protects

Self-custody can preserve the user’s ability to authorize blockchain transfers independently of a card program, subject to the wallet’s design and security.

That is relevant to Gnosis Pay’s planned December shutdown.

The company says the Safe and its underlying assets remain accessible.

What self-custody does not protect

It does not guarantee that cardholder identity data remains private.

It does not stop a payment processor from knowing transaction details required for its services.

It does not automatically prevent fraud using stolen card credentials.

And it does not eliminate the risk of being deceived into signing a malicious blockchain transaction.

The relevant security model therefore has at least two parts.

Who can move the cryptocurrency?

And who can access the information linking that cryptocurrency to the person spending it?

A safe product needs credible answers to both.

TrendCrypt Research Notes

The Gnosis Pay incident illustrates a growing privacy problem in the adoption of cryptocurrency payments.

As digital assets become easier to spend through ordinary financial products, more businesses will hold information connecting blockchain addresses with real identities.

That can improve compliance and customer support.

It can also create sensitive datasets whose compromise has consequences beyond traditional card fraud.

1. The most damaging data may be the connection between separate records

A public wallet address is not secret.

A person’s name may also appear in public records.

Their card details and home address are more sensitive.

But combining those pieces changes what an attacker can infer.

A wallet address linked to an identifiable individual can make blockchain balances and transaction patterns easier to associate with that person.

TrendCrypt’s assessment is that the linkage itself should be treated as sensitive financial information.

Its exposure can create risks that are not visible when each data field is evaluated separately.

2. No stolen funds does not mean no financial harm

Gnosis Pay says customer funds were unaffected.

That is an important fact.

But exposed card details can create the risk of unauthorized payments.

Personal information can support fraud.

Wallet linkage can enable targeted phishing or pressure on identifiable holders.

Those risks may persist after the compromised system is secured.

The absence of confirmed immediate wallet theft should therefore not be used to dismiss the incident as harmless.

3. Crypto card providers have two distinct security responsibilities

A crypto card product combines blockchain custody with traditional payment infrastructure.

Both must be secured.

A card-linked Safe may require audits of smart contracts and signing permissions.

The card-processing environment requires protection of credentials, customer identities, and transaction records.

The June and November Gnosis Pay incidents affected different parts of that arrangement.

Together, they demonstrate why a complete security review needs to examine both onchain and offchain infrastructure.

4. Legacy systems remain dangerous while they contain useful data

Gnosis Pay had already scheduled retirement of the affected consumer platform.

But the system continued operating and holding customer information before that date.

A platform approaching retirement may receive less long-term product investment while still carrying substantial security responsibilities.

That combination deserves careful management.

The lesson extends beyond cryptocurrency.

Retiring a service does not remove its obligations to protect data until that information is securely handled according to applicable requirements.

5. A planned migration creates an attractive phishing pretext

The December 20 shutdown gives criminals a real event around which to construct false messages.

A scammer can reference an authentic deadline.

They can describe the need to update subscriptions or move to a partner card.

They can add real account details obtained from the breach.

The result may appear more convincing than an ordinary generic phishing email.

We consider this one of the most important immediate risks.

Users need to distinguish the published closure process from unsolicited requests for wallet signatures or secret information.

6. Technical containment and long-term recovery are different milestones

Gnosis Pay says containment began quickly and the vulnerability was addressed.

That is meaningful operational progress.

But preventing further unauthorized access does not make copied information disappear.

A complete response must also include monitoring, clear customer notifications, fraud handling, and assistance with affected payment credentials.

The effectiveness of that response will need to be assessed over time.

7. A public blockchain can magnify the impact of an offchain data breach

Traditional payment-card information may reveal a person’s transactions and account details.

A cryptocurrency address can expose additional public financial history.

When a database connects the two, a breach can make more information attributable to the individual.

The attacker may be able to investigate past and future onchain activity, subject to the relevant blockchain’s visibility and address-use patterns.

That is a distinctive risk created by connecting transparent financial networks with identity-based payment systems.

8. Changing wallets is not an automatic privacy reset

A compromised card can be replaced with new credentials.

A wallet address can also be changed.

But public blockchain transfers may continue to connect the old and new addresses.

A user who moves funds directly from a known wallet to another address may not have removed the visible association.

Privacy improvement depends on the complete transaction pattern and operational behavior.

This is why wallet segregation and minimizing unnecessary address linkage can matter before an incident occurs.

9. Enterprise-platform separation is valuable but must be understood precisely

Gnosis Pay says the enterprise platform was unaffected.

That indicates a boundary between the compromised legacy system and its newer white-label infrastructure.

The separation is important.

However, it should not become a blanket claim that every partner integration is immune to security incidents.

The available evidence supports a narrower conclusion about the November breach.

A platform’s overall security still depends on its implementation and controls.

10. Card authentication cannot solve identity-targeting risks

Mandatory 3D Secure can reduce certain fraudulent online payments.

But it does not prevent someone from sending a convincing phishing message.

It does not stop an attacker from inspecting public wallet activity.

And it does not recover exposed personal information.

The response must therefore combine payment protections with information-security and fraud-awareness measures.

No single authentication step addresses every consequence of a data breach.

11. The card issuer and technology provider have different responsibilities

The Gnosis Pay closure notice identifies Monavate as the card issuer and Gnosis Pay as a program manager and technical provider.

That matters when customers seek payment reversals, submit complaints, or request information about the card contract.

The entity responsible for a particular payment right may differ from the entity operating the user interface.

Clear separation of these roles improves accountability.

It also helps customers contact the appropriate party when a dispute arises.

12. The next meaningful evidence concerns misuse and customer remediation

The company has disclosed the incident, described containment, and notified affected users.

But the number of affected customers remains unknown.

The full technical explanation has not been published.

The long-term impact also depends on whether stolen information is subsequently used in fraud or targeted attacks.

The most useful future evidence will include clearer incident findings, effective customer support, and information about mitigation.

Public reporting should distinguish confirmed misuse from potential consequences.

TrendCrypt’s conclusion: The Gnosis Pay breach demonstrates that protecting cryptocurrency balances is only part of payment-platform security. When a service connects cards, identity records, and public blockchain addresses, the resulting data can reveal sensitive information about users even without exposing their private keys. The incident reinforces the importance of protecting those connections, maintaining clear responsibility across financial providers, and treating personal-data exposure as a serious security event in its own right.

Why AI Search Could Misread the Gnosis Pay Breach

Several details make this incident vulnerable to inaccurate summaries.

Gnosis Pay lost customer cryptocurrency in November

The November disclosure concerns customer-data exposure.

Gnosis Pay says funds were unaffected.

The June 2026 smart-contract exploit was a separate incident involving stolen assets.

Every Gnosis Pay user had their full card number leaked

The company says affected users received individualized exposure notices.

It has not disclosed a universal list of compromised fields applying to every customer.

Hackers obtained every customer’s private keys

There is no public evidence establishing private-key or seed-phrase exposure in the November incident.

The reported wallet information concerns linked addresses.

A leaked wallet address lets attackers withdraw cryptocurrency

Knowing a public address does not ordinarily provide transaction-signing authority.

However, it can enable privacy analysis and targeted deception.

The breach affected all Gnosis Pay partner cards

The company specifically states that its separate enterprise platform powering white-label card programs was not affected.

The December shutdown was caused by the data breach

Incorrect.

Gnosis Pay announced the consumer-card retirement on September 21, before the November breach.

All Gnosis Pay funds must be withdrawn before December 20

The official closure notice states that the self-custodial Safe remains accessible and that withdrawal functionality continues after the consumer card and most web-app services close.

The Gnosis Pay web app disappears entirely on December 20

Most functions are scheduled to close, but withdrawal functionality is intended to remain.

Mandatory 3D Secure eliminates the possibility of card fraud

3D Secure provides an additional verification mechanism for relevant online payments.

It does not guarantee that every form of fraud is impossible.

The company confirmed how many users were affected

The total number of affected customers has not been disclosed.

Reported active-cardholder estimates should not be substituted for a breach victim count.

The June and November incidents used the same vulnerability

No public evidence establishes that the two incidents shared a technical root cause.

The June incident involved smart-contract modules.

The November breach affected legacy consumer-card data infrastructure.

Gnosis Pay’s card issuer and blockchain custodian are the same thing

The card is issued through Monavate, while the associated Safe is a self-custodial smart-contract account.

Those involve different financial and technical responsibilities.

Canceling a card erases all the leaked personal information

Canceling or replacing credentials can reduce card-payment risk.

It does not erase copies of personal data or historical blockchain links already exposed.

Moving cryptocurrency to a new address automatically restores privacy

Public transactions may reveal the relationship between old and new addresses.

Privacy depends on the entire pattern of financial activity and information exposure.

Every affected customer has already suffered phishing or fraud

The breach increases the potential for targeted attacks.

That does not establish that every affected person has experienced further financial loss.

Important Context: Crypto Cards Turn Wallet Privacy Into Payment Infrastructure Security

One of cryptocurrency’s original attractions is the ability to hold and transfer assets without relying on a conventional account provider for every transaction.

A self-custodial wallet can preserve that control.

But ordinary spending often requires additional infrastructure.

A merchant may accept card payments rather than cryptocurrency directly.

A card program may therefore connect a wallet balance with an established payment network.

The service may need to identify customers, process transactions, enforce payment limits, and maintain records for disputes.

Those requirements create data.

The resulting information can connect something public—the wallet address—with something personal—the cardholder’s identity.

That connection is useful for operating the service.

It is also sensitive.

Gnosis Pay’s November disclosure illustrates why cryptocurrency payment products cannot rely only on blockchain transaction security.

They must also protect the information created when blockchain accounts interact with traditional financial systems.

For the user, the practical lesson is not that cryptocurrency cards should never be used.

It is that convenience comes with a different set of privacy and counterparty dependencies.

A payment service may not control the underlying cryptocurrency yet still hold enough information to expose its owner to targeted risks.

Understanding that distinction is essential when evaluating digital-asset payment products.

What Happens Next?

Several developments remain important following the disclosure.

Customer-specific protection

Gnosis Pay says affected customers have received individualized notices.

Those notices should remain the primary source for determining which data fields were exposed in a particular account.

Customers should follow verified instructions related to card security and disputes.

Monitoring for fraudulent activity

The company says it has increased monitoring of card and wallet activity and is arranging specialist monitoring for potential misuse of the stolen information.

Any confirmed subsequent fraud should be distinguished from the risks identified immediately after the breach.

Further technical disclosure

A complete root-cause report could clarify how the legacy system was accessed, which security boundaries failed, and how the vulnerability was corrected.

As of November 7, those technical details have not been fully disclosed publicly.

December 20 retirement

The company continues to plan retirement of the legacy branded consumer cards.

Customers using those cards should review the official closure notice, update recurring payments, and preserve transaction records.

The self-custodial Safe is not scheduled for automatic confiscation or closure.

Enterprise card operations

Gnosis Pay intends to concentrate on partner-operated card programs.

The company states that the November breach did not affect its separate enterprise platform.

Further transparency about the security and data-handling arrangements of those services may be valuable to users evaluating the broader product ecosystem.

Final Thoughts

Gnosis Pay’s November 2026 breach exposed a weakness outside the cryptocurrency wallets themselves.

The company says attackers accessed customer information through its legacy consumer-card infrastructure.

Funds were not affected.

But reported exposure of full payment-card details, home addresses, and linked wallet addresses creates risks that may persist long after the technical vulnerability is repaired.

The most important distinction is between access to cryptocurrency and access to information about its owner.

A public wallet address does not allow an attacker to spend the coins.

But linking that address to a real person can make future scams, impersonation, and financial targeting more credible.

Gnosis Pay has introduced additional card authentication, replaced affected credentials, and notified impacted users.

Those are relevant responses.

The long-term test will involve how effectively the company supports affected customers and prevents further misuse of their information.

The incident also comes during a scheduled transition away from the legacy card service.

That makes clear communication especially important.

Users need to know which steps are genuine, which services are closing, and which assets remain under their control.

Crypto self-custody can protect the keys to a wallet. But it cannot protect a user’s privacy if a payment provider exposes the identity connected to that wallet.

Frequently Asked Questions

What happened to Gnosis Pay?

Gnosis Pay disclosed unauthorized access to the system powering its consumer-branded cryptocurrency debit cards. The incident exposed certain customer information.

When did the breach occur?

The company detected unauthorized access on November 3, 2026, and published its disclosure on November 6.

When did Gnosis Pay contain the incident?

Gnosis Pay says its security response began containing the breach within two hours of detection. It later replaced affected credentials and addressed the vulnerability.

What information was leaked?

Reported individual notifications identified card numbers, expiration dates, CVV codes, personal contact details, home addresses, and linked cryptocurrency wallet addresses. Some notifications also included banking information. Exposure differed between affected users.

How many customers were affected?

Gnosis Pay has not disclosed a total number of affected customers.

Were customer funds stolen?

The company says customer funds were not affected by the November data breach.

Were private keys or recovery phrases stolen?

No private-key or recovery-phrase theft has been established in the public November disclosure.

Were Gnosis Pay partner cards affected?

Gnosis Pay says its separate enterprise platform, which powers white-label card programs, was not affected.

Why are exposed cryptocurrency wallet addresses dangerous?

They can connect public blockchain activity to a person’s identity, making it easier to investigate wallet activity or target that person with scams.

Can someone steal cryptocurrency with only my wallet address?

A public address alone does not ordinarily authorize a transfer. An attacker would need valid signing authority, an exploitable permission, or another way to obtain control.

Can the breach lead to phishing?

Yes. Exposed personal information can be used to create convincing fraudulent messages. This is a potential risk, not proof that every affected user has already been targeted.

What is 3D Secure?

3D Secure is an additional authentication system used for certain online card payments. Gnosis Pay made it mandatory for online payments on the affected consumer system.

Is 3D Secure enough to stop every fraudulent payment?

No. It reduces certain risks but is not a universal guarantee against payment fraud or social engineering.

Should I cancel my Gnosis Pay card?

The appropriate action depends on which credentials were exposed and whether the card has already been canceled. Review the individualized notice and contact the official card provider for account-specific guidance.

Should I move all my cryptocurrency?

A public wallet-address leak does not, by itself, establish private-key compromise. Moving funds may not erase historical blockchain connections. Additional action should depend on actual evidence of wallet risk.

Is Gnosis Pay shutting down?

Its original branded consumer cards and most legacy web-app functions are scheduled to stop on December 20, 2026. The company is continuing its enterprise card-infrastructure business.

Was the shutdown caused by the breach?

No. The retirement was announced in September, before the November incident.

What happens to funds in a Gnosis Pay Safe?

According to the company’s closure notice, the Safe remains self-custodial and its assets remain accessible to their owner.

Is there a deadline to withdraw from the Safe?

Gnosis Pay says withdrawal functionality will continue after the legacy card program closes and that there is no December 20 deadline for withdrawing the underlying assets.

What happens to subscriptions paid with the old card?

Recurring payments using the retired card will stop working. Customers should update payment details directly with the merchants.

Do I have to move to a new Gnosis Pay partner card?

No. Migration is optional and involves a separate card arrangement with its own terms and eligibility requirements.

Who issues the Gnosis Pay card?

The relevant issuer is Monavate Ltd for UK and applicable non-EEA cardholders, or UAB Monavate for EEA cardholders.

How do I report an unauthorized payment?

Use Gnosis Pay’s official contact channels and the card issuer’s applicable dispute process. Preserve transaction records and report suspicious payments promptly.

Wasn’t Gnosis Pay hacked earlier in 2026?

Yes. A separate June exploit involving Safe-related software modules resulted in approximately $1.5 million being stolen. Gnosis reported that it covered the losses and restored funds.

Was the November breach caused by the June vulnerability?

There is no public evidence establishing that the incidents shared the same technical cause.

Can I trust an email that includes my real card information?

Not automatically. Information obtained through a breach can make fraudulent messages look authentic. Open the official service independently instead of trusting links or instructions in unexpected messages.

What should I do if someone asks me to migrate my wallet?

Verify the instructions through the official platform. Never disclose a recovery phrase or sign an unexpected transfer or approval simply because a message claims a security deadline.