Skip to content

Risk Digest

What the NATO intern's spying charges mean for Belgian criminal law

This article breaks down the two-count charging structure Belgian prosecutors used against the NATO intern, explains why the criminal-organization charge was necessary under the old Penal Code, and identifies the distinct pleading burdens and penalty exposures that legal practitioners need to assess when counseling clients with NATO or allied-government personnel.

By Editorial TeamUpdated Jul 29, 2026Verified Jul 30, 2026
REPORTED — UNVERIFIED
Jurisdiction
Belgium
Court
Brussels Court of First Instance
AI tool named
None
Ruling date
Jul 25, 2026
Source document
View primary court order ↗
Last verified
Jul 30, 2026

Lex Machina Review is an independent risk-tracking and reference resource. Nothing on this site is legal advice, and using it does not create an attorney-client relationship. Every record is reviewed against primary sources but may not reflect the most current status of a matter — always verify directly against the cited court order, rule text, or a licensed attorney before relying on it.

Companion explanation — secondary to the source document above

Start with the two counts, not the spy-story scenery

The legal implications of the NATO intern spying charges begin with the charging structure Belgian prosecutors actually announced. On July 25, 2026, the Belgian Federal Prosecutor’s Office said the suspect had been charged with espionage on behalf of a third country and membership in a criminal organization; on July 28, prosecutors said pretrial custody had been extended for one month, with 24 hours to appeal.[1][2]

Those are not interchangeable labels for the same alleged conduct. The espionage count supplies the foreign-state secrecy offense. The criminal-organization count supplies a network theory: that the alleged activity was not merely an individual access breach, but part of coordinated, foreign-directed conduct. For counsel assessing exposure around NATO, EU, or allied-government personnel in Belgium, that distinction matters more than the nationality of the suspect or the intelligence service assumed in headlines.

The “third country” has not been officially named by the Belgian Federal Prosecutor’s Office. Media coverage has widely pointed toward China, but that is not the same thing as a charged or confirmed prosecutorial allegation. The same caution applies to the suspect’s name: “Claire Z.” has been reported by several outlets, but prosecutors have not officially confirmed the identity.

Belgian courthouse facade with two legal document scrolls suggesting two distinct legal pathways
ChargeWhat it addsWhat counsel should test
Espionage on behalf of a third countryA foreign-state secrecy frame for the alleged conductWhat information, access, intent, and foreign-benefit theory prosecutors can actually plead and prove
Membership in a criminal organizationA network theory that may connect the suspect to direction, recruitment, tasking, or support by othersWhether the evidence supports participation in an organization rather than suspicious individual conduct

A criminal-organization charge in this posture should not be treated as prosecutorial decoration. It changes the case from “a person allegedly obtained or sought sensitive information” to “a person allegedly operated within, or for, an organized structure.” That shift affects what prosecutors may try to prove, what evidence becomes relevant, and how penalty exposure is assessed if the count is sustained.

The reason is partly structural. Belgium’s existing espionage provisions are old and awkward for modern foreign-intelligence cases. Politico’s 2023 reporting on Belgium’s “spy law problem” described provisions dating to the 1930s and the absence of a comprehensive standalone espionage offense, with prosecutors relying on adjacent tools such as criminal-organization charges to capture conduct that looks like contemporary espionage but does not fit neatly into a single modern code offense.[3]

That context makes the second count more intelligible. If prosecutors believe an intern-level access point was being used by a foreign-directed network, the organization count helps them plead beyond the narrow act of access. It can bring in communications, recruitment pathways, direction by handlers, links to other participants, and conduct that may not itself be the taking of secrets but may support an inference of organized participation.

It also adds a burden. A network theory must still be proved as a network theory. Odd questions about security protocols, foreign origin, or proximity to sensitive buildings do not by themselves establish membership in a criminal organization. The charge matters because it gives prosecutors a broader evidentiary frame; it is not a substitute for proving the elements that make organized participation criminal.

FTM’s reporting treated the organization count as a bridge in a Belgian system that lacks a comprehensive standalone espionage offense, and connected the theory to the alleged access-agent profile rather than to a traditional senior official with formal classified authority.[4] That is precisely why the count is consequential for risk advice: it tells counsel to assess not only what a staff member could access, but also whether communications, tasking, travel, funding, or contacts could be characterized as participation in a broader operation.

The old Penal Code problem has not disappeared

This case should be analyzed under the old 1867 Penal Code framework, not as an early test of the new Criminal Code. Belgium approved Books I and II of the new Criminal Code in February 2024, and the reform introduced a new penalty architecture, including eight penalty levels.[5][6] But the effective date was postponed from April 8, 2026, to September 1, 2026, and the arrest and charging events in this case occurred in July 2026.[5][6]

That timing is not a technical footnote. If a client asks what Belgian prosecutors have just shown they are willing to do, the answer is not “use the new Code.” The answer is that prosecutors, before the new Code’s revised effective date, brought a dual-track case under the existing structure: an espionage allegation paired with a criminal-organization allegation.

The new Code is still relevant for forward-looking compliance advice, but only within limits. The reform changes important aspects of Belgian criminal law and penalties, yet the available materials do not show that it comprehensively recodifies espionage as a modern standalone offense.[5][6] If that gap remains, future cases may continue to feature the same basic prosecutorial move: plead the secrecy offense available, then use organization-based liability to reach the alleged network behind the access point.

The access-agent facts matter only if they connect to an element

The reported biography is easy to overread. FTM, Le Soir, and Knack identified the suspect as Claire Z. based on two security officials, but the Belgian Federal Prosecutor’s Office has not publicly confirmed the name.[4] AP described the matter as an intern arrested in Belgium on suspicion of spying inside NATO’s military headquarters.[7]

FTM reported that the suspect worked in SHAPE’s IT department, was in her 30s, held a master’s degree in computer science, had published AI research, and was observed “hanging around NATO’s buildings” and “frequently asking hypothetical questions about breaches of security protocols,” citing security officials.[4] Those facts are legally useful only if they do work: access to systems or spaces, knowledge of security procedures, intent, or an inference that the suspect was being tasked or groomed by others.

They do not, on the available public record, establish the disputed propositions that would matter most at trial. The materials provided do not confirm what information, if any, was taken; whether the suspect had formal access to classified material; which third country prosecutors allege benefited; or what evidence connects the suspect to a criminal organization. For defense counsel, that is where the case will have to be narrowed. For institutional counsel, that is where internal fact-gathering should begin.

What the detention ruling tells practitioners—and what it does not

The July 28 extension of pretrial custody for one month indicates that the investigating magistrate found sufficient grounds to keep the suspect detained at this stage, with a 24-hour appeal window.[2] It keeps the case active into late August 2026. It does not prove the espionage count, prove the organization count, identify the third country, or settle how Belgian courts will treat the dual-track theory.

That procedural posture matters for companies, universities, contractors, and public-sector partners with personnel moving through NATO-adjacent environments. A detention order can increase urgency without answering the merits. Counsel still need to separate employment discipline, security access review, data preservation, criminal-law exposure, and diplomatic or status questions rather than letting one “spy case” label collapse them into a single response.

The risk review now has to follow both statutory tracks

For similarly situated personnel, the practical review should start with the same split prosecutors used. One file should ask the espionage questions: what information was accessible, what information was sought, what restrictions applied, what foreign-benefit theory could be alleged, and what evidence bears on intent. A separate file should ask the organization questions: who communicated with whom, whether there were instructions or tasking, whether there was compensation or support, whether others played defined roles, and whether the pattern can be characterized as participation in an organization.

That second file is often the one institutions underbuild. Security teams naturally focus on credentials, badges, devices, network logs, and physical access. Those records matter. But in a Belgian charging pattern that includes criminal-organization membership, the surrounding relationship evidence may become just as important: travel records, outside affiliations, unexplained contacts, messaging channels, recruitment touchpoints, and the reasons a junior or temporary staff member asked unusually specific security questions.

The review should also keep nationality and status issues in their proper lane. Reuters described the suspect as a Canadian intern.[1] That may prompt questions about consular notification, cross-border evidence, extradition exposure in other factual settings, or NATO status-of-forces complications. The available materials do not establish those consequences here. They are watch points for counsel, not settled outcomes.

The significant lesson is narrower and more useful than the headline version. Belgian prosecutors have not merely alleged spying inside NATO. They have shown, in a live July 2026 prosecution, how an espionage case may be assembled through separate statutory tracks: one aimed at foreign-directed secrecy conduct, the other at organized participation. Each track carries its own pleading burden, evidentiary reach, and penalty exposure. Any risk assessment that treats them as one generic espionage charge will miss the shape of the case prosecutors actually filed.

References

  1. Canadian intern at NATO military HQ arrested in Belgium on spying charge — Reuters, July 25, 2026
  2. Pretrial custody of alleged NATO spy extended, Belgian prosecutor says — Reuters, July 28, 2026
  3. Belgium's spy problem — Politico, 2023
  4. Espionage at NATO: This is the suspect who was arrested last week — FTM, July 2026
  5. The time for change is now: the new Belgian Criminal Code — Freshfields
  6. 10 hot topics on the new Belgian Criminal Code — ARCAS Law
  7. Intern arrested in Belgium on suspicion of spying inside NATO military headquarters — AP News

Report a correction or tip

Spotted an outdated figure, a misstated fact, or a ruling this case record should reflect? Public comments are disabled for this content given the professional cost of a misreported case outcome, penalty amount, or rule text — use the structured correction channel instead.

Report a correction or tip for this record →