Datahorses

Social engineering against finance and HR teams: the warning signs

By · · 4 min read

Social engineering against finance and HR teams means persuading the people who move money or hold personal data to do it for the wrong person. No malware is needed. The attacker sends a believable request, often from a forged or compromised mailbox, and relies on routine: an invoice to pay, a bank detail to update, a document to send.

The scale is large. The FBI's Internet Crime Complaint Center counted 24,768 business email compromise complaints in 2025, with reported losses of $3,046,598,558 (IC3 2025 Internet Crime Report). The FBI also notes that these schemes often involve requesting employees' personal information in order to compromise other accounts (IC3 PSA I-091124-PSA).

The good news is that most attempts share a short list of signs. A team that knows them, and has a habit of verifying, stops the majority before any money leaves.

Why finance and HR are the target

Finance can change where money goes. HR can change where salaries go and holds Social Security numbers, tax forms, addresses and bank details. Both teams also receive many legitimate requests from outside: suppliers, applicants, benefits providers, payroll services. A fraudulent message blends in with that traffic.

Attackers prepare by studying what anyone can see from outside: names and roles on your website and professional networks, the format of your email addresses, which accounting or payroll platform you mention in job ads, and who your suppliers are.

The warning signs in finance

  • A supplier announces new bank details. "We have changed banks, please use the account below for this and all future invoices." This is the core of the invoice scheme described in fake invoices sent in your company's name.
  • An executive asks for an urgent, confidential payment. Secrecy plus urgency is the classic pattern of CEO fraud and executive impersonation.
  • The sender address is almost right. billing@examp1e.com instead of billing@example.com, or a familiar display name with an unfamiliar address behind it.
  • The reply goes somewhere else. The Reply-To header points to a different domain than the From address.
  • The thread changes tone. A long, real conversation with a supplier suddenly asks for faster payment or a different account. This can mean the supplier's own mailbox was taken over.
  • Pressure to skip the process. "No time for the usual approval", "the auditors need it today".

The warning signs in HR

  • An employee asks to change direct deposit by email. The FBI has described payroll diversion in which criminals phish employee credentials, change the bank account in the payroll system and add mailbox rules so the employee never sees the alert (IC3 PSA I-091818-PSA). A variant skips the login entirely and simply emails HR "from" the employee.
  • A request for a bulk export of employee data. Tax forms, salary lists or ID copies requested by "the CEO" or "the accountant", often near a deadline.
  • A login link that looks like your payroll or benefits portal. Fake login pages built around your brand are covered in fake login pages using your brand.
  • An attachment from an applicant that asks to enable content or a link to a CV on an unfamiliar file sharing site.

How to check a suspicious request

  1. Look at the real address, not the display name. On a phone, tap the sender name to reveal it.
  2. Compare From and Reply-To. In most mail clients you can view the original message and its headers.
  3. Check the domain. Is it your supplier's usual domain, or a near copy? A domain registered a few days ago is a strong signal.
  4. Confirm on a second channel. Call the supplier or the employee on a number you already have on file, never the number in the message.
  5. Check your own domain's protection:
dig +short TXT _dmarc.yourcompany.com

If the policy is p=none or the record is missing, messages forging your own domain can still reach inboxes. SPF, DKIM and DMARC explained walks through the records.

Habits that stop most attempts

  • No bank detail change without a call back to a known contact, and a 2nd person approving it.
  • Direct deposit changes only inside the payroll system, after the employee signs in with multi-factor authentication, never by email.
  • Personal data is never sent by email on request. Bulk exports go through a defined process with a named owner.
  • Executives say openly that they will never ask to skip a process. That turns "keep it between us" into a warning sign.
  • Thank people who pause to verify, even when the request turns out to be real.
  • Multi-factor authentication and alerts on payroll, banking and mailbox rule changes, so a compromised account is noticed quickly.

If money or data already left

Contact your bank at once and ask for a recall of the transfer, then file a complaint at ic3.gov. The FBI stresses that time matters for recovering funds (IC3 PSA I-091124-PSA). Keep the original messages with full headers, reset passwords on affected mailboxes, and remove any forwarding or filter rules the attacker created. If employee data was sent, involve your legal counsel about notification duties.

A short checklist

  • Bank detail changes confirmed by phone and approved by 2 people.
  • Direct deposit changes only through the payroll system with multi-factor authentication.
  • DMARC enforced on your domain, external sender tags on.
  • Lookalike domains of your company and key suppliers identified.
  • A clear way without blame to report a suspicious message.

How Datahorses helps

Social engineering works best when your domain can be forged or a lookalike domain is ready to send mail. Datahorses watches your company from the outside the way an attacker would: new domains resembling yours (see lookalike domains and typosquatting), fake login pages, and your email authentication settings. A person reviews each finding and you receive clear steps. See what we guard, what happens when we find something, or the example dashboard.

More articles

All articles