SOCLYDE logo
Current languageEN
Cybersecurity newsRansomwareFinanceData breach

Panzer claims attack on Financière d’Uzès

Panzer has claimed an attack on Financière d’Uzès. Here is what has been reported, what remains unconfirmed, and practical precautions.

Published on · Updated on

By Soclyde Team

Finance professionals reviewing files in an office

In summary

  • Panzer claimed the attack on September 8, 2026; the sources reviewed do not independently confirm an intrusion or data leak.
  • The type and volume of any affected data have not been established.
  • Verify any request for payment or documents through a channel you already know.

Explore next

Soclyde resources

Article contents

The ransomware group Panzer claimed an attack targeting Financière d’Uzès on September 8, 2026. Several threat-tracking services repeat the claim, but that does not independently confirm an intrusion or data theft. News Asset Pro says it contacted the company, which had no information to share at the time about the incident, its scale, or its impact.

What is known — and what is not

The sources reviewed establish that a claim attributed to Panzer was made and listed by threat trackers. They do not confirm that the company’s systems were compromised, that files were encrypted, or that data was published. The 70 GB figure appearing in some trackers has not been verified with a documented sample and should not be presented as an established volume.

The people potentially affected and the categories of data are therefore unknown. Avoid speculation about client files, transactions, or credentials that have not been documented.

Precautions for unexpected requests

A public claim can be used as a pretext for phishing or fake urgent requests. Do not share a code, password, or document in response to an unexpected email. Verify any sensitive or financial request with your contact using a phone number or address you already know.

Useful steps for an organization

Organizations can review access logs, identify privileged accounts, and revoke access that is no longer needed. These general precautions do not mean a specific compromise has been confirmed. If an incident is established, the relevant teams should follow their response procedures and applicable obligations.

To reduce password-reuse risk, see our secure password generator guide and our first steps after a data breach guide.

What Soclyde can help with

Soclyde does not detect intrusions and cannot confirm or resolve this incident. Its local-first encrypted vault helps people keep unique secrets instead of reusing them. Talk to Soclyde about access organization.

Frequently asked questions

Has the attack on Financière d’Uzès been confirmed?

Not by the sources reviewed: Panzer claimed it, but they do not independently confirm an intrusion or data leak.

Is the 70 GB figure verified?

No. Some threat trackers repeat it, but the sources reviewed do not document data that would verify the volume.

How should I verify a request received after this announcement?

Contact the organization or person using details already on file. Do not use links or phone numbers included in an unexpected message.

Frequently asked questions

Has the attack on Financière d’Uzès been confirmed?

Panzer has claimed the attack, but the sources reviewed do not independently confirm an intrusion or a leak. News Asset Pro reports that the company had no information to share about the incident when contacted for its article.

What data was allegedly stolen?

The sources reviewed do not confirm a dataset or specific file types. The 70 GB figure repeated by some trackers remains an allegation, not a verified volume.

What should I do if I receive a message about this incident?

Do not click unexpected links or share a code or document. Verify the request by calling your contact using a number you already have on file.

References

Sources and references

Need advice?

Design your password strategy with Soclyde

Schedule a dedicated walkthrough with the team to see how local-first security adapts to your stack.

Talk with us

Keep reading