Case Library / Phishing / Pine Bluff School District's $3.2M BEC: one extra letter in a domain (2025)
Phishing Documented incident

Pine Bluff School District's $3.2M BEC: one extra letter in a domain (2025)

Scammers hijacked a real invoice thread with a lookalike domain and got an Arkansas school district to wire $3.2M. $1.1M recovered. How the thread hijack worked.

Share:

Social Engineering Examples·6 sources

Pine Bluff School District's BEC loss came down to one extra letter. In December 2025, the Arkansas district was making a routine monthly payment to East Harding Construction for its roughly $74 million new high school. Scammers slipped into the real email thread from a lookalike domain, "easthardings.com" instead of "eastharding.com", and asked for the payment by wire because of a year-end audit. On 17 December the district wired $3,204,639.55 to accounts they controlled. By May 2026 it had recovered $1,120,051.15. Status: Under FBI investigation.

Key takeaways

  • This wasn't a cold phishing email. It was a real, expected invoice thread, hijacked.
  • The excuse was true. There really was a year-end audit.
  • The finance director's Google account had been accessed from Lekki, Nigeria, as early as 12 December, records show.
  • One phone call to a known number would have stopped it. That's how the fraud was finally confirmed.

Timeline

Date Event
By 12 December 2025 The finance director's Google account is accessed from a device in Lekki, Nigeria, per a login screenshot in released records
December 2025 Architect Lewis Architects Engineers sends the pay application to East Harding, which forwards it to the district. Attackers join the thread from easthardings.com
17 December 2025 The district wires $3,204,639.55 through Simmons Bank. The superintendent approves it
18 December 2025 While checking an unrelated vendor request, the finance director spots the wrong domain. She calls East Harding and confirms the fraud at about 2:10pm
19 December 2025 She files a complaint with the FBI's IC3
May 2026 The district reports $1,120,051.15 recovered

Most of what's known comes from district records released under Arkansas's open records law, including annotated email printouts and the IC3 complaint, as reported by the Arkansas Democrat-Gazette.

How the thread hijack worked

Move Why it worked
Ride a real thread Topic, timing, amount and people were all expected. Nothing looked off
Add one letter "easthardings.com" reads as right at a glance
Use a true reason A real year-end audit explained the switch from the usual cheque pickup to an electronic payment
Hide the real email Notes in the records suggest the genuine contractor message was hidden in the finance director's mailbox
Adapt When she said she couldn't pay by ACH, the scammers offered wire instructions instead

That last step tells you something. These people knew the relationship well enough to roll with a no.

Tip: a change in how you pay a vendor, cheque to wire, is as risky as a change of bank details. Call before you send.

What happened next

The money went through Citibank to several other accounts. Simmons Bank's fraud team asked for it back. The district still had to pay East Harding the real amount owed. It has no separate cyber insurance and filed a claim with the Arkansas Cyber Response Board. The FBI opened an investigation. The finance director was later put on paid administrative leave. East Harding said its own systems weren't breached. Nobody has been identified or charged.

What stops it

  • Call the vendor on a number you already have before acting on any new or changed payment instructions.
  • Two people for every wire, one to start it and one to approve it, both checking.
  • Treat a change of payment method as a red flag, especially with a deadline or audit attached.
  • Turn on MFA and watch for odd logins, like foreign locations, and for inbox rules that hide messages.
  • Check sender domains letter by letter, and flag lookalikes automatically.
  • Report fast. A quick recall request is the best chance of getting money back.

Pine Bluff has since adopted these controls. See also invoice fraud, the Dickinson Public Schools case and business email compromise.

Common questions

How much did Pine Bluff School District lose?

It wired $3,204,639.55 to scammers on 17 December 2025 and had recovered $1,120,051.15 by May 2026.

How did the scammers trick the district?

They joined a real invoice email thread from a lookalike domain, easthardings.com, and asked for the payment by wire, citing a real audit.

Was the contractor hacked?

East Harding said its own systems were not breached.

How was the fraud discovered?

The next day, the finance director noticed the wrong domain and called East Harding, which confirmed it never asked for a wire.

Sources
Cite this case

Social Engineering Examples. “Pine Bluff School District's $3.2M BEC: one extra letter in a domain (2025)”. Accessed 3 November 2026. https://socialengineeringexamples.com/pine-bluff-school-district-vendor-bec-2025

Attack Chain & Defense
1Reconnaissance
What happened

Attackers likely used public sources such as school-board meeting records, bond/construction-project disclosures, and local news coverage of the district's ~$74M high school project to identify Pine Bluff School District's large, recurring vendor payments and its relationship with contractor East Harding Construction and architect Lewis Architects Engineers.

The control that would have stopped it

Public disclosures about large capital projects (board minutes, bond announcements, local news) serve legitimate transparency purposes and are very hard to suppress; the realistic control assumes attackers can find this information and instead hardens the payment process it gets used against, which is addressed at later stages.

2Look-alike domain registration
What happened

The actors registered a domain, "easthardings.com" (an added "s"), built to visually mimic the real "eastharding.com" vendor domain, staging infrastructure in advance so it could receive copied correspondence and later send messages that appeared to come from East Harding.

The control that would have stopped it

Brand-protection or DNS-monitoring services that alert on newly registered look-alike domains, plus an organization proactively registering close variants of its own vendor and partner domain names, can catch some of these registrations, though not every permutation.

3Account compromise
What happened

Consistent with FOIA-released login records showing access to the finance director's Google account from a device in Lekki, Nigeria as early as Dec. 12, and with the finance director's own IC3 statement that the construction manager's email account was compromised too, the attackers gained unauthorized access to email on both sides of the vendor relationship, likely through prior phishing or stolen/leaked credentials rather than a documented technical exploit.

The control that would have stopped it

Enforcing multi-factor authentication on all finance-adjacent email accounts and monitoring for logins from unexpected geographies is exactly the kind of control that would have flagged the Nigeria-based access in this case in real time rather than only after the fact via FOIA records.

4Mailbox manipulation
What happened

Once inside, the attackers appear to have applied a mailbox filter that moved the district's legitimate contractor email into the finance director's trash folder so she would not see it, then inserted the look-alike domain address into the ongoing invoice thread as a hidden participant.

The control that would have stopped it

Regularly auditing mailbox rules and filters for unexpected forwarding, deletion, or filing rules catches the kind of attacker-created rule that hid the genuine contractor email here, a well-documented BEC persistence technique.

5Pretext injection
What happened

Posing as a known East Harding executive inside the hijacked, genuine thread, the attackers cited the district's real, already-known year-end audit as the reason to switch the routine payment from an in-person check pickup to an electronic transfer, an accurate detail that made the request feel unremarkable.

The control that would have stopped it

Treating any request to change a payment method or timing as an automatic trigger for out-of-band verification, even one wrapped in an accurate, familiar-sounding pretext like a known audit, keeps a true supporting detail from being enough on its own to authorize a change.

6Adaptive social engineering
What happened

When the finance director said she could not pay by ACH, the attackers adapted in real time and offered wire instructions instead, showing they were monitoring replies and understood the vendor relationship well enough to keep the pretext credible.

The control that would have stopped it

Requiring that any change to payment channel or banking details be confirmed by calling the vendor back on a previously known phone number, never one supplied in the same email thread, closes the gap that adaptive, in-thread social engineering exploited here.

7Payment execution
What happened

The finance director initiated the $3,204,639.55 wire through Simmons Bank on Dec. 17, 2025, with the superintendent's approval, sending the funds toward an account at Citibank that the attackers controlled.

The control that would have stopped it

Dual authorization and separation of duties, so no single employee can both initiate and approve a large wire, plus a mandatory small test transfer with a waiting period for new or changed banking instructions, are the controls Pine Bluff adopted after the fact and would have interrupted execution.

8Cash-out and dispersal
What happened

Per the superintendent's account to reporters, funds moved from the receiving Citibank account on to multiple further downstream accounts, a rapid-dispersal pattern typical of BEC money-mule layering meant to frustrate wire-recall efforts before the fraud is discovered.

The control that would have stopped it

Immediate fraud reporting to the originating bank and to FBI IC3 enables fast wire-recall requests to the receiving bank, the main lever for clawing back funds before further dispersal, which is what produced the roughly $1.12M Pine Bluff recovered.

Quick Facts
Victim
Pine Bluff School District
(Pine Bluff, Arkansas); its contractor East Harding Construction Co. and architect Lewis Architects Engineers had accounts/threads abused but East Harding stated its own systems were not breached.
Company
Pine Bluff School District
Location
Pine Bluff, Arkansas, USA
Date
2025-12-17
Impact
$3,204,639.55 wired to fraudulent accounts on Dec.
BasisreportedWire amount stated by the district; recovery amount reported by the district in May 19, 2026 coverage
17, 2025; the district reported recovery of $1,120,051.15 in May 19, 2026 coverage and hoped for additional recovery. District filed a claim with the Arkansas Cyber Response Board; the district said it does not carry separate cyber insurance.
Status
Documented incident
Case Type
Real-World Incident
Sector
Construction & Engineering, Education
Threat Actor
unknown
Explore more

Related Cases

Browse by what this case has in common with others in the library.