Authentication appears out of context
A document, voicemail, survey, delivery, or policy message unexpectedly asks the employee to sign in.
Fake Login Pages Awareness
How to Recognize and Report Fake Login Pages
A fake login page imitates a trusted sign-in experience to capture credentials, authentication codes, recovery details, or other account information.
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
Fake Login Pages: a practical definition
A fake login page imitates a trusted sign-in experience to capture credentials, authentication codes, recovery details, or other account information.
Branding and page design can be copied. The safer habit is to begin at a known application or organizational sign-in route and to question why an unexpected message requires authentication.
Source: CISA Phishing Guidance
02Recognition clues
Warning signs employees can check in a fake login pages 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.
Unfamiliar destination
The page is not reached through the normal application route or does not match the organization's expected identity flow.
Repeated or expanded requests
The page asks for credentials again, requests an MFA or recovery code, or changes the type of secret requested.
03Safe response
Move from suspicion to a supported next step
| Moment | Employee action | Program preparation |
|---|---|---|
| Before acting | Close the page, open the known application or company portal independently, and check whether the expected task exists there. | 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
Fake Login Pages 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.
Educational landing page
Use a controlled destination that explains the clue and records only approved simulation activity—not anything typed as a password.
Known-route exercise
Ask employees to reach a fictional shared item through the normal application bookmark or portal.
Mobile sign-in review
Demonstrate how the organization's mobile client exposes the destination before opening a link.
05Campaign workflow
Build the exercise around a decision employees can repeat
- 1
Define the behavior
Write down the fake login pages 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 fake login pages 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.
Can a fake login page look identical to the real one?
Visual appearance is not reliable proof. Teach employees to use a known application entry point and to assess why authentication is being requested.
What should happen if an employee entered a password?
They should report the event promptly through the established response route. The responsible team should follow its documented account and incident process; awareness content should not improvise production response steps.
Can fake login pages 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. The simulation must not accept, validate, transmit, or store real passwords, authentication codes, recovery codes, or session data.
How should fake login pages 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 fake login pages 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.