Forensic Case Study: The Direct-Deposit Change Nobody Asked For

An email is not proof of a payroll change

A missing paycheck is an unusually clear signal. Security alerts are often ambiguous, but a missed paycheck is hard to ignore. This composite case study describes a common direct-deposit diversion pattern and the points where an organization can make its own job harder.

Composite case study: based on patterns observed across incident response engagements; details are blended and illustrative.

The situation

In payroll-diversion cases, a common pattern starts with an employee who notices a deposit has not arrived. The bank shows nothing pending, so the employee asks HR. The answer can be that the bank details were changed on request and the money went to the account on file. HR may point to an email asking for the change as justification.

An email is a claim, not proof. A request that appears to come from an employee still needs confirming through a channel the organization already trusts, especially when the employee says they did not send it.

What the investigator saw

Investigators typically start with the email. Useful things to look for:

  • A sender address that is personal-style or resembles the employee’s name rather than the corporate mailbox.
  • Short, urgent wording that asks for the next pay run to use new bank details.
  • Headers that show whether the message passed through the corporate mailbox at all.

These signs can point to simple impersonation, but that may be only part of the picture. The HR platform commonly has its own self-service login, separate from email. Its audit log can show the bank-detail change saved from the employee’s own portal account.

That is the complication. Because the change is made under the employee’s own credentials, it can look like a legitimate user editing personal data. In the audit log, look for sessions from locations or devices that do not match the user’s usual pattern, and for changes timed close to the email request. The email can serve as cover for the change rather than as the mechanism.

How it was confirmed

Confirmation typically means comparing the portal audit log with the email evidence and the sign-in records, and asking the employee whether they made the change. Mismatches can point toward a phished or reused password. Treat that as a hypothesis to test, not a finding.

Because this type of incident can reach beyond one person, investigators search the portal audit log for other bank-detail edits in the same period and look for similar edits from unfamiliar sessions. Some affected staff may not notice until their own pay run is affected.

What it cost

The possible consequences are mostly about money and trust. There may be a diverted payment and the effort of chasing it. Employees who report a problem and are told it was their own mistake may be less likely to report the next one. Staff may come to see that a payroll record can be changed without anyone confirming it with them. HR teams may also need to re-verify details by hand, which is slow work.

Containment

Once the portal pattern is clear, containment starts promptly:

  • Pause payroll changes so no further pay run uses the edited details.
  • Lock the affected portal logins, end active sessions, and reset passwords.
  • Contact the bank to flag the diverted payment. Recall requests tend to work better when made quickly.
  • Restore correct bank details only after each employee confirms them by a known channel, such as a phone number already on file.
  • Tell affected staff plainly what happened and what to watch for.

Evidence capture runs in parallel: the audit log export, the original email with full headers, and the sign-in records are preserved while the lockouts proceed. As a precaution, reset the affected email accounts as well, since the portal and mailbox might share a credential.

Lessons

  • Treat payroll data like payments. A change to where money goes deserves the same scrutiny as a change to a vendor’s bank account.
  • An email asking for a change is a request, not proof. Verify through a channel you already trust.
  • The HR portal has its own login. Resetting email alone does not close that door.
  • Multi-factor authentication on the HR portal can make a stolen password less useful, though it does not stop every takeover.
  • When one employee is affected, check colleagues. A shared cause, such as a phish or reused password, can touch more than one account.
  • A cooling-off window before a bank change takes effect gives the real employee time to object.

Checklist for your next incident

  • Pause bank-detail changes until the scope is understood.
  • Pull the portal audit log and compare it with email evidence.
  • Lock portal logins, end sessions, and reset credentials.
  • Call the bank and ask about stopping or recalling the payment.
  • Confirm correct details with each person through a known channel.
  • Search for the same pattern across other employees.
  • Tell affected staff what happened and what to watch for.
  • Turn on multi-factor authentication for the HR portal, which can make a stolen password less useful though it does not stop every takeover.
  • Add out-of-band verification and a cooling-off period to the change process.

Message us to talk through your payroll change verification plan.


Discover more from Core-Infosec

Subscribe to get the latest posts sent to your email.

Picture of Core Watch

Core Watch

Practical security guidance from Core-Infosec.

Read More