Sistema de cartões para consumidores da Gnosis… · Breach

[Single source] Gnosis Pay confirms customer data exposure in card system

Nov 09, 2026 · 1 min read

Gnosis Pay confirmed customer-data exposure in its consumer-card system. The company says funds and its enterprise platform were unaffected; the case was detected on November 3 and affected users have been emailed. Customers should watch for targeted phishing.

By HIFY Radar newsroom Updated 11/09/2026 10:43 AM Get this every day →← Back to the feed 1 source

MediumBreachNo software to update

In 30 seconds

Observed

Gnosis Pay has confirmed a customer-data exposure in its consumer-card system, according to a disclosure published on the company's official blog on November 9, 2026. The blog post, identified by its URL as concerning a data breach in a legacy system for Gnosis Pay-branded cards, is the primary source for the incident.

Alleged

Per the company's statements as summarized publicly, user funds and the enterprise platform were unaffected. The incident was detected on November 3, 2026, affected users have been notified by email, and the company warns of possible targeted phishing following the breach.

What happened

Observed

Gnosis Pay published a disclosure on its official blog (URL slug: "data-breach-legacy-system-gnosis-pay-branded-cards") confirming a data breach. The URL indicates the incident involves a legacy system tied to Gnosis Pay-branded cards.

Observed

A same-day summary by the security account DailyDarkWeb states: the customer-data exposure affects Gnosis Pay's consumer-card system; the company says funds and its enterprise platform were unaffected; the incident was detected on November 3 and disclosed on the day of the post (November 9, 2026, per the publication timestamps); affected users have been emailed; and users are advised to beware targeted phishing.

Why it matters

Inferred

Personal data exposed in a card-system breach can be used to craft convincing follow-up attacks. Gnosis Pay itself warned users to beware targeted phishing, which indicates the company treats post-breach social engineering against affected customers as a realistic risk.

Inferred

Gnosis Pay operates at the intersection of crypto wallets and consumer payment cards, so even a breach limited to a legacy card system can erode user trust in crypto-linked payment products and pressure the company to clarify what data was exposed and to whom.

What to do

Observed

Gnosis Pay says affected users have been contacted by email, and it explicitly warns users to beware targeted phishing attempts referencing the breach.

Inferred

Based on the company's phishing warning, users of Gnosis Pay cards should be skeptical of unsolicited messages about the breach, verify that any notification genuinely originates from Gnosis Pay's official channels, and never share card details, account credentials, or wallet secrets in response to such messages.

Confirmed and still uncertain

Observed

Known at this point: the breach affects the consumer-card system (a legacy system for Gnosis Pay-branded cards per the blog URL); detection occurred on November 3, 2026; public disclosure followed on November 9, 2026; the company claims funds and the enterprise platform were unaffected; affected users were notified by email; and a phishing risk was flagged.

Inferred

Not yet established in this evidence batch: the number of affected customers, which specific data fields were exposed, how the exposure occurred, and whether any data was actually exfiltrated or misused. The full text of Gnosis Pay's blog post was not included in the batch, so these details remain unverified pending the primary disclosure or follow-up reporting.

What people are saying

Observed

DailyDarkWeb, a security-focused account on X, amplified the disclosure and summarized the company's key claims: consumer-card data exposure, funds and enterprise platform reportedly unaffected, detection on November 3, email notifications to affected users, and a warning about targeted phishing. The post links to Gnosis Pay's official blog and is tagged #DataBreach.

Observed

The authoritative statement so far comes from Gnosis Pay itself, via its official blog post. In the current evidence batch, there are no statements from regulators, law enforcement, independent researchers, or affected customers, and no third-party corroboration beyond the DailyDarkWeb summary.

Evolution

Observed

Timeline as disclosed: the incident was detected on November 3, 2026; Gnosis Pay publicly disclosed it on November 9, 2026 via a blog post on its official site; and the same day the news was summarized and circulated on X by DailyDarkWeb. The gap between detection and disclosure is roughly six days.

Inferred

The story is at an early stage: only the initial disclosure and one social summary are in evidence. Expect potential follow-ups such as clarification of the exposed data types, incident-cause details, and any regulator or customer reactions, none of which are present yet in this batch.

Reach

Observed

1 independent groups, 1 updates, and 0 engagements.

Technical detail

Observed

The URL of Gnosis Pay's disclosure post identifies the affected component in its slug as a "legacy system" for "Gnosis Pay branded cards": the only technical characterization available directly from the primary source in this batch.

Inferred

Taken together, the "legacy system" framing and the company's statement that its enterprise platform was unaffected suggest the exposure is confined to older infrastructure supporting the consumer branded-card program, rather than Gnosis Pay's current enterprise systems or customer funds. The full blog text, which would normally specify affected data types and technical root cause, was not retrievable in this batch.

Sources and evidence

Observed

Primary source: Gnosis Pay's official blog post at gnosispay.com/blog/data-breach-legacy-system-gnosis-pay-branded-cards, published November 9, 2026. Note that the post's body text was not captured in this evidence batch, so its contents are known only through the URL and the secondary summary.

Observed

Secondary source: a post on X by DailyDarkWeb (November 9, 2026) summarizing the disclosure: customer-data exposure in the consumer-card system, claims that funds and the enterprise platform were unaffected, detection on November 3, email notifications to affected users, and a warning about targeted phishing. Claims about fund safety originate from the company and are not independently verified in this batch.