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. 182
No. 182 Critical Brief · Regulatory Attribute Proof

Northern Territory Government agency, Australia: A bank-detail change emailed by a construction contractor impostor sent a payment to another account (AFP media release)

A$3.58M
Paid by the agency to an account it believed was the contractor's (AFP media release)
A$3.57M
Recovered after quick action and preventative measures by the bank (AFP media release)
2024-11-07→2025-07-27
From the fake email to the AFP announcing charges against a man in NSW
CountryAustralia
Incident date2024-11-07
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

    According to the Australian Federal Police (AFP), the agency received an email in the name of its construction contractor, with a completed vendor identification form carrying new bank details. The agency paid an account it believed belonged to the real contractor.

  2. 02What was found

    Other addresses from the company were copied in. The AFP alleges those addresses were created to make the scam look legitimate.

  3. 03Why it got through

    Even when a bank-detail change arrives complete and in a vendor’s name, the payment goes to another account unless someone checks that the account was approved through the vendor’s registered contact.

Exhibit 1Detection vs pre-execution check

A pre-execution check means confirming, before using a bank-detail change for payment, that it was approved through the vendor's registered contact, and keeping a record. Detection means noticing a fraudulent transaction after the payment. The sequence relies on the AFP media release. The payment date and the date the bank noticed have not been disclosed.

Pre-execution check · not known from the disclosuresCheck bank-detail changes through the vendor's registered contact before paying
What was confirmedA$3,583,363 paid to another account
A$3,571,760 recovered
Detection · worked after the paymentA bank reports a suspected BEC incident and quick action recovers most of the money
2024-11-07
An email and form in the contractor's name arrive
Afterwards
The agency pays another account
2024-11
A bank reports; the AFP investigates
Afterwards
The bank's action recovers most funds

What got through

What got through
A vendor identification form with updated bank details, emailed in the name of the agency’s construction contractor. The agency then paid A$3,583,363 to an account it believed belonged to the legitimate contractor (AFP).
How the email looked
According to the AFP, the sender appeared to copy in other email addresses from the construction company. Those addresses were allegedly created to make the scam appear legitimate.
What reached the receiving side
In general, whoever processes vendor records sees the vendor’s name, the form, the new bank account and the sender’s address. If the name and form match the real vendor’s, only the account and the sender differ.
Not disclosed
The names of the agency and the contractor. The steps between receiving the form and paying, and the payment date. Whether there was one payment or several. The receiving bank and how it noticed. Any procedures the agency changed afterwards.

Pre-execution check

Whatever the route, the condition for telling them apart is that the vendor’s approval of the bank-detail change on the form is checked with its registered contact, not the email or form that arrived, before paying.

Pre-execution gate
Before paying, check the new bank details on the form with the vendor's registered contact, not the email or form that arrived.
Who approves
The vendor. When an account is registered or changed, it approves the account through its registered contact. A contact given in the email or form is not used.
Where it is checked
Both the step that accepts a vendor form and changes the bank details, and the approval step before payment. An account that does not match the vendor’s approval is not activated, and payments to it are held. This is separate from reviewing the form’s contents or the look of the email.
What is recorded
Which vendor’s bank-detail change arrived from which address, and who checked it with which contact before using it for payment. That record is reviewed before paying.

It was the bank, after the payment had gone through, that noticed. Similar cases, where a vendor’s payments were pointed at an impostor, are the Portland Water Bureau (bank details switched via a password-reset link), the City of Baltimore (a fake contact was added to a supplier’s account) and the City of Mobile (an arena payment went to a contractor impostor).

What Lemma does

Lemma builds the pre-execution check into the side that accepts vendors’ bank-detail changes and uses them for payment. It does not look for intrusions; it checks, before paying, that the destination account was approved through the vendor’s registered contact.

Industries and operations to watch

IndustryPublic sector
Government agencies, local governments and public bodies that pay large sums to construction and other contractors. Contractor names are often public through tenders and contract notices.
OperationBank account changes
Vendor forms and bank-detail changes that arrive in a vendor’s name.
OperationAccount and record admin
Changing vendor records (company details, contacts, accounts).

Current controls vs Lemma

The route in this case is column 1 (a bank-detail change form sent in the vendor’s name from lookalike addresses). Column 2 covers a takeover of the vendor’s registered contact itself; nothing disclosed says that happened here.

Control Bank-detail form from lookalike addresses Takeover of the vendor’s registered contact
Reviewing the email’s appearance and the form’s contents Not effective Not effective
Detection and recovery by the bank Partial Partial
Lemma (pre-execution check) Effective Not effective

Reviewing the email and the form is hard to rely on here: according to the AFP, the sender appeared to copy in other company addresses created for the scam (police also allege a business resembling the real contractor was registered). Detection and recovery by the bank brought back A$3,571,760 of A$3,583,363 in this case, but it acts after the payment and does not help if noticed too late. Lemma checks the destination account, not the look of the email or form, against the vendor’s approval through its registered contact before paying.

Note: Lemma’s check works only when it is built into both the step that accepts vendor forms and the approval step before payment, and the contact used for approval is managed apart from the system that takes changes. Forms arriving by email and changes arriving by any other route go through the same check. It passes if the registered contact itself has been taken over. 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, and it does not recover funds.

CheckChecklist

Three things to confirm about vendor bank-detail changes and payments

  • Do you confirm bank-detail changes through the vendor’s registered contact, not a contact given in the email sent in the vendor’s name?
  • Do you hold payments made right after bank details change until the check is complete?
  • If a payment is found to have gone to the wrong place, is there a set procedure to contact the bank and police immediately?

Facts and timeline

Party
An agency of the Northern Territory Government, Australia (the AFP did not name the agency). The vendor was a construction contractor, also not named.
Loss
The agency paid A$3,583,363 to an account it believed belonged to the legitimate contractor. After quick action and preventative measures by the bank, A$3,571,760 was recovered (AFP).
What was confirmed
According to the AFP, the email to the agency carried a completed vendor identification form with updated bank details. Other company addresses were copied in. The AFP alleges those addresses were created to make the scam appear legitimate.
Investigation
The AFP charged a 38-year-old man from Lurnea, NSW, with dealing with proceeds of crime worth A$1 million or more. Police will allege he registered a business resembling the legitimate contractor, opened the receiving account and withdrew cash on several occasions. These are allegations (AFP).

Glossary
Business email compromise (BEC) — A scam using email that poses as a business partner or colleague to request a bank-detail change or a transfer.
Vendor identification form — A form a supplier uses to register its company details and the bank account it should be paid to.
Australian Federal Police (AFP) — Australia's federal police, which investigates cybercrime and crime across state lines.

Timeline

2024-11-07
The agency receives an email it believes is from its construction contractor, with a vendor form carrying updated bank details (AFP).
Afterwards
The agency pays A$3,583,363 to an account it believes is the contractor’s (AFP; date not disclosed).
2024-11
A bank reports a suspected BEC incident and the AFP opens an investigation (AFP).
2025-07-23
Having traced a phone number linked to the vendor form, the AFP searches the man’s home and seizes devices and company documents (AFP).
2025-07-24
The man appears in Liverpool Local Court and is granted conditional bail (AFP).
2025-07-27
The AFP announces the charge.

The amounts paid and recovered, the email and form, and the course of the investigation rely on the AFP media release (primary). The charge reflects police allegations and has not been decided by a court. The agency’s and contractor’s names, the payment date, and the bank’s name and how it noticed have not been disclosed. What has not been disclosed does not mean there were no controls.

After disclosure

  • Australian Federal Police: Advises confirming any request to change bank details by calling the party on a number you have previously used or independently verified, not a number in the suspicious email, and reporting to your bank and the police immediately if you have fallen victim.
  • Court: The man was due to appear in Campbelltown Local Court on 17 September 2025 (AFP).

Sources

  1. Primary, police media releaseAustralian Federal Police “Alleged scammer charged in NSW over $3.5 million fleeced from government agency”2025-07-27 · afp.gov.au/news-centre/…

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

The same method elsewhereSee all 16 "Payee & bank-account changes" 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).
"Northern Territory Government agency, Australia: A bank-detail change emailed by a construction contractor impostor sent a payment to another account (AFP media release)".
Lemma Critical Brief No.182. Lemma / FRAME00, Inc.
https://lemma.frame00.com/critical/briefs/182-northern-territory-agency-vendor-bank-change/
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.