Go back to blog

What Operation Jackal IV Reveals About the Business of BEC

What Operation Jackal IV Reveals About the Business of BEC

On 25 August 2026, INTERPOL announced the results of Operation Jackal IV: 58 arrests, 263 suspects identified, and coordinated action across 22 countries on six continents. The eight-month operation, run between November 2025 and June 2026, targeted West African organised crime networks, Black Axe among them, and their fraud infrastructure โ€” romance scams, investment fraud, business email compromise, and the laundering networks that move the proceeds.

The figures are worth sitting with. In Romania, a call centre running a cryptocurrency and stock investment scam is estimated to have taken roughly โ‚ฌ143 million from victims worldwide before eleven arrests and the seizure of cash, crypto and six properties. In Argentina, investigators identified 196 people in a crime-as-a-service network that sold website domains and laundering support to fraud operators; 17 were arrested. In Italy, a single mule account moved โ‚ฌ845,000 through 560 transactions across twenty different financial instruments. In South Africa, 39 arrests followed raids that blocked 257 bank accounts and recovered $2.67 million from scams targeting English-speaking retirees.

None of this looks like opportunistic hacking. It looks like a supply chain: people who build infrastructure, people who run the social engineering, and people whose only job is moving money before it can be traced. BEC sits inside that same ecosystem, and Jackal IV is useful precisely because it makes the machinery behind it visible rather than abstract.

How a BEC scheme actually unfolds

Business email compromise does not usually involve malware. It relies on convincing a specific person, at a specific moment, to move money or change payment details. The pattern is consistent enough to describe in stages.

Reconnaissance. Attackers study a target company’s public footprint โ€” leadership names and titles, supplier relationships, out-of-office replies, press releases about deals or expansions โ€” to work out who can authorise a payment and who they would plausibly ask.

Impersonation or compromise. The attacker either spoofs a lookalike domain, registers one, or gains access to a real executive or supplier mailbox through prior credential theft. A compromised legitimate account is more dangerous, because it passes authentication checks that a spoofed sender fails.

The request. A message arrives with urgency and authority built in: a wire transfer needed before a deadline, an invoice with “updated” bank details, or a request to purchase gift cards for a client. The tone mimics how the impersonated person actually writes, and the ask is framed to discourage the recipient from checking with anyone else.

Cash-out. Once payment lands, it moves fast โ€” through mule accounts, shell companies, or crypto wallets, often within hours. This is where the infrastructure Jackal IV describes matters most: the Italian case shows funds fragmented across dozens of instruments precisely to outrun a bank’s ability to freeze them, and Argentina’s crime-as-a-service network shows that domains and laundering routes are increasingly bought in, not built from scratch.

Why the laundering layer changes the response

Most BEC advice focuses on catching the email. Jackal IV is a reminder that money still has to move through real accounts, and that speed is the attacker’s only advantage. A payment stopped within hours can often be recovered; one discovered after a week rarely can. That is why verification before payment matters more than detection after the fact.

Defensive priorities, in order of impact

Out-of-band verification for any payment or bank-detail change. No change to supplier bank details, and no urgent wire request, should be actioned on the basis of an email alone. A phone call to a known, previously verified number closes the gap that a compromised mailbox cannot.

Email authentication, properly enforced. SPF, DKIM and DMARC stop a large share of domain spoofing when DMARC is set to reject rather than merely monitor. This is table-stakes, not a complete defence โ€” it does nothing against a genuinely compromised account โ€” but there is no good reason to leave it half-configured.

Behavioural detection for compromised accounts. Because BEC increasingly rides on legitimate, authenticated mailboxes, technology needs to look at communication patterns, not just headers: unusual timing, a sudden change in tone, or a first-ever request for a bank-detail change from an established contact.

A documented payment workflow with a second approver. Any change above a defined threshold should require sign-off from someone who did not receive the original request, breaking the isolation the attacker depends on.

A checklist for finance and procurement this week

Confirm every bank-detail change goes through a callback to a verified number. Check whether DMARC is enforced at reject, not monitor. Ask whether your email security flags anomalous behaviour from known contacts, not only unknown senders. Review who can approve a wire transfer alone, and remove that possibility.