Direct-deposit change by email
A supposed employee asks to replace payment details without using the approved payroll or identity process.
Payroll Phishing Awareness
How to Recognize and Report Payroll Phishing
Payroll phishing impersonates an employee, leader, payroll provider, or HR process to redirect pay, obtain workforce data, or capture account access.
Use this guide to turn the threat into a clear employee decision, a safe practice scenario, and a reporting step your organization can support.
Plain-English definition • Warning signs • Safe simulation ideas • Reporting practice
01Understand the threat
Payroll Phishing: a practical definition
Payroll phishing impersonates an employee, leader, payroll provider, or HR process to redirect pay, obtain workforce data, or capture account access.
The attack targets both employees and the teams authorized to change records. A strong response depends on identity and change-control procedures outside email.
Source: CISA Phishing Guidance
02Recognition clues
Warning signs employees can check in a payroll phishing message
No single clue proves that a message is malicious. Teach employees to combine the request, sender, business context, destination, and available verification route before acting.
Sensitive workforce document
A requester seeks tax, compensation, employee-list, or payroll information outside the normal reporting workflow.
Personal urgency
The message uses travel, access problems, a new phone, or financial hardship to justify an exception.
03Safe response
Move from suspicion to a supported next step
| Moment | Employee action | Program preparation |
|---|---|---|
| Before acting | Use the established employee identity, payroll portal, and approval process for every sensitive record or payment change. | Publish the authentic contact, application, or reporting route somewhere employees can reach without using the message. |
| When uncertain | Pause the request and report it through the approved channel with enough context for review. | Explain what the response team needs and how employees will know that their report was received. |
| After an interaction | Stop, contact the responsible team promptly, and describe the action taken without hiding the mistake. | Provide a well-known response route and avoid communications that discourage early reporting. |
Source: NIST: Recognizing, verifying, and reporting phishing
04Practice safely
Payroll Phishing simulation and discussion ideas
Choose one learning objective per exercise. Use fictional people, organizations, accounts, payments, documents, and events, and test the reporting route before sending to employees.
Fictional direct-deposit request
Practice routing an invented change through identity verification and the payroll system.
Executive payroll file
Ask an authorized HR audience to verify a fictional leadership request for workforce data.
Employee portal notice
Teach employees to open the known payroll service instead of using an unexpected message link.
05Campaign workflow
Build the exercise around a decision employees can repeat
- 1
Define the behavior
Write down the payroll phishing clue being practiced, the expected action, the authorized audience, and the owner of follow-up.
- 2
Confirm the real process
Test the independent verification route, message-reporting option, response handoff, and employee support path from a representative account.
- 3
Pilot the scenario
Check delivery, links, landing content, accessibility, event records, automated inspection, stop conditions, and the explanation employees will receive.
- 4
Review in context
Reconcile intended recipients, successful deliveries, unique employee events, verified reports, response handling, and completed follow-up before drawing conclusions.
Source: NIST SP 800-50 Rev. 1: Building a Cybersecurity and Privacy Learning Program
06Useful measurement
Evaluate recognition, reporting, and the surrounding process
Record actual counts and denominators for delivery, unique recipient events, reports, and follow-up. Separate automated email inspection and repeat events where the available evidence supports doing so.
A payroll phishing exercise samples one scenario under one set of conditions. It does not establish an employee's intent, overall security awareness, or likelihood of responding the same way to a real attack.
Use findings to improve the real workflow: clearer verification instructions, easier reporting, faster response handling, better role-specific training, or a business control that reduces reliance on email alone.
Common questions
Common questions about Phishmake's features, onboarding, and support, answered to help you get started with confidence.
Who should receive payroll-phishing training?
Include payroll and HR teams, managers who approve changes, employees who receive payroll notices, and support staff who may handle account-access requests.
Can email be used to approve payroll changes?
Follow the organization's documented process. The awareness objective should reinforce identity verification and required approvals rather than normalize email-only changes.
Can payroll phishing be used in a phishing simulation?
It can be practiced when the scenario is authorized, proportionate, and tied to a real reporting or verification process. Use fictional employees, accounts, tax forms, salaries, and records. Do not alter production payroll, imitate a real employee hardship, or expose workforce information.
How should payroll phishing simulation results be measured?
Review successful delivery, unique employee events, reports, response handling, and completed follow-up. Include scenario difficulty and operating context, and do not treat a click or report as a complete measure of employee risk.
Sources & further reading
Published by Phishmake · Updated
Keep building your program
All resourcesPut it into practice
Turn payroll phishing awareness into a repeatable response.
Use Phishmake to run controlled employee simulations, review campaign activity, assign relevant training, and keep follow-up records in one workflow.