Skip to content
Menu

Anonymised typical cases

Understanding real situations, without exposing the victims.

These examples are deliberately simplified, combined or generalised. The aim is not to be sensational: it is to show the method, assess the facts, preserve the evidence, secure access, document the actions, and say honestly what remains out of reach.

No case contains a name, a bank or a date: confidentiality preserved.

My incident file in Galyct Perso: situation, evidence and pre-filled letters, ready to send.
Confidentiality preserved Generalised typical cases No result guaranteed Method demonstrated
01 · HOW TO READ THEM

Each case is presented with the same logic

The value is not in the sensational. It lies in the ability to rebuild a clear, usable and careful file.

01Initial situationWhat is reported, observed or only suspected at the start.
02Main riskWhat can keep causing harm: access, payment, account.
03Useful evidenceWhat must be kept before anything is deleted or changed.
04Actions takenThe checks, fixes and security measures.
05DeliverableWhat can be handed over or used for your formal steps.
06LimitsWhat cannot be stated without usable evidence.
02 · EXAMPLE SITUATIONS

Six typical cases seen after a hack or fraud

These examples are not guarantees of results. They help to identify more quickly what needs to be preserved, checked and documented.

Bank fraud

Fake adviser and approval under pressure

The victim receives a convincing call. The caller talks about fraud in progress and pushes them to approve a transaction or hand over information, on the pretext of protecting them.

To preserve
  • Call and text history.
  • Bank notifications.
  • Exchanges with the bank.
  • Timeline of approvals.
What was done
  • Reconstructing the timeline.
  • Checking the exposed accounts.
  • Securing email and bank.
  • A summary that can be used for a claim.

Honest outcome: the report does not guarantee a refund; it clarifies the case and makes it usable.

Fake support

Remote access after a fake alert

A frightening alert shows a number to call. A third party gets a remote control tool installed and can access accounts, browsers or payment methods.

To preserve
  • Name of the tool installed.
  • Time of the call.
  • Invoices or payments requested.
  • Screenshots of the alert if available.
What was done
  • Removing the unwanted tools.
  • Checking browsers and sessions.
  • Securing the accounts used.
  • Checking for useful traces.

Honest outcome: the presence of a tool does not, on its own, prove every action the scammer took.

Hacked account

Email changed by a third party

The mailbox shows signs of compromise: unknown sessions, changed recovery details, forwarding rules, filters, or messages sent without your knowledge.

To preserve
  • Security alerts.
  • Unknown sessions and devices.
  • Forwarding rules.
  • Suspicious messages sent or received.
What was done
  • Signing out of sessions.
  • Changing the recovery options.
  • Turning MFA on or restoring it.
  • Checking linked accounts.

Honest outcome: regaining the account is not always enough to know how the access happened.

Impersonation

Identity used to deceive family and friends

An account or an identity is used to contact other people, ask for money, spread messages or create confusion about who is really behind them.

To preserve
  • Timestamped screenshots.
  • Links to the profiles or accounts.
  • Messages received by family and friends.
  • Recovery requests to the platform.
What was done
  • Checking the source account.
  • Preparing the reports.
  • Securing email and phone.
  • A warning message to contacts if needed.

Honest outcome: the intervention helps document and secure access, not identify the culprit for legal purposes.

Blackmail

Extortion message after a data leak

The person receives a threatening message claiming a device has been compromised. Some details often come from old data leaks rather than an active infection.

To preserve
  • Full message, and headers if it is an email.
  • Sender address.
  • Wallet or link requested.
  • References to old leaks if known.
What was done
  • Checking critical accounts.
  • Looking for signs of compromise.
  • Strengthening passwords and MFA.
  • Careful wording of the conclusions.

Honest outcome: data exposure does not automatically mean the device is infected.

Phone

Suspected phone surveillance or exposed account

The victim notices worrying behaviour: calls, notifications, unknown sign-ins, suspicious apps or a feeling of being followed online.

To preserve
  • Timestamped screenshots.
  • List of apps.
  • iCloud, Google or WhatsApp sessions.
  • Specific events observed.
What was done
  • Checking linked devices.
  • Checking cloud accounts.
  • Recovery settings and MFA.
  • Separating facts, assumptions and limits.

Honest outcome: not every unusual behaviour proves active surveillance.

WHAT THESE CASES DON’T PROMISE

Typical cases, not promises

A case similar to yours does not mean the same conclusion: each case depends on the evidence available, the accounts involved and the decisions of third parties (banks, platforms, insurers, authorities). We check, secure, document and advise, but we promise no refund, no recovery of funds and no identification of the culprit. And we will never ask for your codes. Your data stays in France.

CONFIDENTIALITY

Why the cases are deliberately generic

The publication principle

Remove anything that could re-identify someone

A case that is too precise can become identifiable by cross-checking: date, place, bank, amount, operator, age or family description. So we remove unnecessary details and keep only what helps to understand the method.

  • The facts are reworded.
  • Sensitive details are removed.
  • Amounts are left out or generalised.
  • The conclusions remain cautious.
The limits

What this page does not do

This caution protects victims and avoids sensationalist communication. To stay credible, we show the steps, the useful evidence, the deliverables and the limits, nothing more.

  • It does not identify anyone involved.
  • It promises no banking or legal outcome.
  • It does not replace the analysis of a real case.
  • It does not turn an assumption into evidence.
METHOD DEMONSTRATED

What these typical cases should make clear

Effective intervention is not just about “cleaning” a device. It means acting in the right order: preserving what is useful, regaining access, reducing the risks, then producing a clear summary.

Before deleting

Identify what must be kept so as not to lose items that are useful to the case.

Before making a claim

Pin down the timeline to avoid an incomplete or contradictory account in front of a third party.

Before concluding

Separate observed facts, statements, assumptions and limits, without mixing them up.

FREQUENTLY ASKED QUESTIONS

Anonymised cases: what you need to understand

These examples are useful to see where you stand, but the diagnosis is still needed to assess a real incident.

Are the cases exact client files?

No. They are anonymised, simplified, combined or generalised to protect the people involved. They illustrate typical scenarios and a method of intervention, not identifying testimonials.

Why not give the amounts or the banks?

These details could allow someone to be re-identified by cross-checking. They are not needed to understand the right reflexes and the method.

Does a case similar to mine mean the same conclusion?

No. Two similar situations can involve very different evidence, risks and limits. The conclusion depends on what is actually available.

When should I ask for a report?

When you need to send a clear file to a bank, an insurer, a platform, an ombudsman, a lawyer or an authority, without claiming more than can be verified.

Does your situation look like one of these cases?

Start by assessing the facts. The free diagnosis identifies the immediate risks, the evidence to keep and the right level of support, with no commitment.

Free diagnosisCall