Products Lemma APIProof issuance & verification platformTrust402Delegate to agents, and transactSealSign-in for the agent era — no keys handed over
Use cases Manufacturing & Critical InfraInspection Record AssuranceFinance & FinTechCounterparty Record VerificationPublic SectorCertificate-less ProceduresHealthcareQualified Worker AssuranceProcurement & Supply ChainSupplier Credential MonitoringMedia & ContentContent AuthenticityService & RetailCross-group IdentityAI Adoption (cross-industry)AI Run GovernanceDevelopers & Agent OpsAgent Authority Control ▸ Browse the use-case index
Pricing
Resources Critical BriefThe frontier of AI × trustBlogThinking and implementation notesDocumentationAPI & specsVerification CenterReal verification & issuance countsAbout usFRAME00, Inc.ContactSales & press inquiriesGlossaryDefinitionsFAQFrequently asked questions
Dashboard ↗ JA
Home / Critical Brief / No. 181
No. 181 Critical Brief · Verifiable Origin

UK Ministry of Defence: An Afghan relocation casework file, believed to hold some applicants' names, was emailed outside authorised systems (government statement to Parliament)

18,714people
Afghan applicants whose data was in the file (applications up to 2022-01-07, per the government)
150people
Applicants whose names the sender believed were being sent (per the government)
2022-02→2023-08
About 18 months from the email to ministers learning of it
CountryUK
Incident date2025-07-15
Published2026-11-05
AuthorsLemma Critical Team
Contents
  1. 01Summary
  2. 02What got through
  3. 03Pre-execution check
  4. 04What Lemma does
  5. 05Facts and timeline
  6. 06Sources

Summary

  1. 01What happened

    The sender believed they were sending the names of some applicants; what went out was the casework file itself. It held applicants’ names and contact details and, in some cases, family members (per the government).

  2. 02What was found

    It came to light about 18 months later, when some people’s details appeared online. The government called it a serious departmental error in clear breach of strict data protection protocols.

  3. 03Why it got through

    When a file holds more than the sender thinks, the difference shows up only after it is out, unless its records and fields are checked before sending.

Exhibit 1Detection vs pre-execution check

A pre-execution check means checking, before a file leaves, that its record count and fields match what is meant to be sent, and keeping a record. Detection means noticing after the send, such as when data is found outside. The dates below are from the government's statement.

Pre-execution check · not known from the disclosuresBefore sending, check that records and fields match what is meant to be sent
What was confirmedA file believed to hold 150 names
held data on 18,714 people
Detection · about 18 months laterSome details appear online and ministers learn of the loss
2022-02
The file is emailed
2023-08
Some details appear online
2023-09-01
High Court grants a superinjunction
2025-07-15
Order lifted; statement to Parliament

What got through

What got through
In February 2022, a Defence official emailed an ARAP casework file outside authorised government systems. The sender believed it held the names of 150 applicants; the file held data on 18,714 people (per the government).
What reached the receiving side
In general, an email arrives as an operation sending the file the sender chose to the recipient the sender chose. How many people and which fields the file holds cannot be told from the act of sending.
How it came to light
In mid-August 2023, details of nine people from the file appeared online and ministers at the time learned of the loss (per the government), about 18 months after the email.
Not disclosed
The recipient, why the file differed from what was intended, and how it spread after the send. Because the safety of the people affected is at stake, this Brief does not go into individuals or the content of applications.

Pre-execution check

Whatever the route, the condition for telling them apart is that the file’s record count and fields are checked against the approved scope, not the sender’s own judgement, before the file is sent out.

Pre-execution gate
Before sending outside, check the file's record count and fields against the scope the data holder approved, not the sender's own judgement.
Who approves
The organisation that holds the data. It decides which fields of the casework data, how many records, and which recipients may receive them. The sender’s judgement alone does not decide.
Where it is checked
Where casework data is exported, and where it leaves the organisation. Just before sending, the mechanism reads the file’s record count, columns and source dataset. It checks them against the approved scope (here, “the names of 150 applicants”) and holds a send that does not match.
What is recorded
Which file went out, on whose approval, and what it was checked against, kept so that data found outside later can be traced to the send it came from.

Detection worked, but about 18 months after the send. Other cases where what was sent differed from what the sender intended are TOPPAN’s mixed-in ZIP and Tokyo Housing Supply Corporation’s address labels.

What Lemma does

Lemma builds the pre-execution check into the route by which casework data is exported and sent out. It does not look for intrusions; just before sending, and apart from the sender’s judgement, it checks that the file’s record count and fields match the approved contents.

Industries and operations to watch

IndustryPublic sector
Bodies that track applications or benefits in lists and exchange names with partner agencies and supporters. Besides names, the lists carry columns such as contact details and family members.
OperationSending & delivery
Taking part of a list and emailing it outside. If the whole list goes instead of the extract, the difference cannot be seen at a glance.

Current controls vs Lemma

The route in this case is column 1 (a file larger than intended). Column 2 is the case where the contents are right but the recipient is wrong; the recipient in this case has not been disclosed.

Control File with more records or fields than intended Right contents to the wrong recipient
Handling rule: don’t send outside authorised systems Partial Partial
Sender’s own check before sending Not effective Partial
Recipient warnings and send-undo Not relevant Partial
Automated outbound scanning by count of personal data Partial Not relevant
Lemma (pre-execution check) Partial Partial

A handling rule sets the route, but per the government the file was sent outside it. The sender’s check does not look for differences inside the file while the sender believes it holds 150 names. Recipient warnings help with a wrong recipient but say nothing about the size of the contents. Automated scanning by count can catch a send containing a lot of personal data, but does not know how many records were approved. Lemma checks the approved contents (record count, fields, source) against the file’s actual contents just before sending.

Note: Lemma’s check works only when it is built in where casework data is exported or where it leaves the organisation, and the data holder registers which fields, how many records and which recipients may go out. A send made outside that route does not pass through it. Whether it applies when data is sent outside authorised systems, as here, depends on where it sits. If the registered scope is itself wrong, a wrong send still goes through. Lemma does not delete or recall data that has already gone out. The table compares what each control checks; it does not show whether this incident would have been stopped. Lemma does not detect or prevent intrusions.

CheckChecklist

Three things to confirm in your organisation about sending application or case lists outside

  • Are files exported from casework data blocked from being sent outside the agreed route?
  • When sending outside, are columns the recipient does not need (contact details, family members and so on) removed at export?
  • If data is found outside, is there a record to trace which file went out, when and on whose approval?

Facts and timeline

What was sent
An ARAP casework file (a spreadsheet) holding data on 18,714 Afghans who applied to the Ex Gratia scheme or ARAP on or before 7 January 2022: applicants’ names and contact details and, in some cases, family members. In a small number of cases, names of MPs, senior military officers and government officials were noted as supporting applications (per the government).
How it was sent
A Defence official emailed it outside authorised government systems, believing it held the names of 150 applicants. The government called it a serious departmental error in clear breach of strict data protection protocols (per the government).
After it came to light
The department removed the material online, ran an internal investigation, and reported to the Metropolitan Police and the Information Commissioner. The Met decided no criminal investigation was needed (per the government).
Superinjunction
On the previous government’s application, the High Court granted a superinjunction on 1 September 2023. Eight media organisations and their journalists were served, and the order’s existence could not be reported. On 15 July 2025 the High Court ruled, in light of an independent review, that there was no tenable basis to keep it, and it was lifted at noon that day (per the government).
Relocation
In autumn 2023 the Afghanistan Response Route (ARR) was set up for people in the file who were not eligible for ARAP but were judged at highest risk of reprisal. It was first aimed at about 200 principals and had grown to nearly 3,000 by early 2024. At the time of the statement, about 900 principals and 3,600 family members were in Britain or in transit, at a cost of £400 million (per the government).
Independent review
In early 2025 the Defence Secretary commissioned an independent review by a former senior civil servant (the Rimmer Review), which reported to ministers in June. Per the government, it found it unlikely that being in the file alone would lead to reprisal, while not ruling out risk.

Glossary
ARAP — The Afghan Relocations and Assistance Policy, which takes applications to relocate to the UK from Afghans who worked for the UK. The file was used for casework on those applications.
Casework file — A list for tracking each application (a spreadsheet, per the government). Besides names, it can hold columns such as contact details and family members.
Superinjunction — A court order that bars not only reporting but also reporting that the order exists. Here it ran from 2023-09-01 to 2025-07-15.

Timeline

2022-02
The ARAP casework file is emailed outside authorised government systems.
2023-08
Details of nine people from the file appear online and ministers learn of the loss. Removal, internal investigation, and reports to the Met and the ICO.
2023-09-01
The High Court grants a superinjunction.
Autumn 2023
The ARR is set up.
2025-06
The independent review reports to ministers.
2025-07-15
The superinjunction is lifted and the Defence Secretary makes a statement to the House of Commons. The ARR is closed.

Facts rest on the Defence Secretary’s statement to the House of Commons on 15 July 2025 (primary). The error is described, as in the statement, as a departmental error; this Brief does not go into the individual official. Because the safety of the people affected is at stake, details that could identify individuals or the content of applications are left out. The statement does not describe the recipient, why the file differed from what the sender intended, or the checks before sending. What has not been disclosed does not mean there were no controls.

After disclosure

  • UK government: The Defence Secretary apologised on behalf of the government. The ARR makes no new offers and is closed; about 600 existing invitations to people still in Afghanistan will be honoured. ARAP stopped taking new applications on 1 July 2025 (per the government).
  • Information Commissioner (ICO): Per the government, it has continued to work with the department since the report.

Sources

  1. Primary, government statement to ParliamentUK Ministry of Defence “Oral statement on Afghan data breach”2025-07-15 · gov.uk/government/…

This Brief uses only the government’s statement to Parliament as primary. The public version of the independent review and the ICO’s own statements have not been checked. Press and commentary sites are not included as sources.

References: “The last layer left in AI-era cyber defense”

The same method elsewhereSee all 9 "Human error" cases

This Brief sets out, from disclosed facts, what organisations in a similar position can check. It is not guidance on individual losses or procedures.

This material is a structured analysis of public information; it is not an audit, diagnosis, or recommendation for any specific organization.

Cite this Brief

Lemma Critical Team. (2026).
"UK Ministry of Defence: An Afghan relocation casework file, believed to hold some applicants' names, was emailed outside authorised systems (government statement to Parliament)".
Lemma Critical Brief No.181. Lemma / FRAME00, Inc.
https://lemma.frame00.com/critical/briefs/181-uk-mod-afghan-relocation-data-email/
Read nextNext
All Briefs →
Lemma

If it can't be verified,
it doesn't enter your operation.

Lemma is a pre-execution check: logins, payments, records and publishing that look genuine are checked before they run, with cryptographic proofs the receiving side verifies without asking the issuer. Detection stays; the check sits in front of it.