Unexpected file or installer
The attachment type, download, or software request does not match the sender, role, or active business task.
Malware Phishing Awareness
How to Recognize and Report Malware Phishing
Malware phishing uses a message to persuade the recipient to open, download, install, or run harmful software or content.
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
Malware Phishing: a practical definition
Malware phishing uses a message to persuade the recipient to open, download, install, or run harmful software or content.
The payload can be disguised as an ordinary document, archive, installer, update, or link. Employees should not be expected to analyze a file; they need a safe decision and reporting path.
Source: CISA Phishing Guidance
02Recognition clues
Warning signs employees can check in a malware 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.
Security exception requested
Instructions ask the user to enable macros, disable protection, bypass a warning, or install an unfamiliar viewer.
Layered packaging
A message uses an archive, password-protected file, nested attachment, or external download without a known reason.
03Safe response
Move from suspicion to a supported next step
| Moment | Employee action | Program preparation |
|---|---|---|
| Before acting | Confirm the file and task through the known sender or workflow, and report unexpected content rather than opening it to determine what it is. | 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
Malware 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.
Harmless attachment
Use an inert controlled file to test reporting and the educational handoff without executing active content.
Installation-request lesson
Present a fictional document that asks for an unfamiliar viewer and identify the real software-request process.
Archive decision tabletop
Discuss how to handle a password-protected or nested file from an unexpected sender.
05Campaign workflow
Build the exercise around a decision employees can repeat
- 1
Define the behavior
Write down the malware 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 malware 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.
Should employees open a file to see whether it is safe?
No. When the file is unexpected, employees should use the known verification and reporting process instead of investigating it themselves.
Can a simulation attachment contain a harmless macro?
Avoid active code entirely. An inert file or visual example can test the employee decision without creating unnecessary device and control risk.
Can malware 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 only inert content. Do not include macros, executables, exploits, obfuscated scripts, active downloads, persistence, or any behavior that can change a device or evade security controls.
How should malware 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 malware 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.