SEE THE SITUATION

An everyday document can carry an unusual request.

Invoices and shared work orders belong in a normal workday. That makes them useful disguises. Ask whether you expected this exact file, from this person, at this time. A real project number helps establish context, but it does not make a file safe. Verify a changed delivery process before opening the attachment.

YOUR GOAL

Check an unexpected file without opening it, weakening protection or sharing it widely.

Message preview

Vendor accountsinvoices@vendor-files.example

Invoice for your recent service visit

“Your balance is attached. Please review before end of day.”

Service-invoice.pdfAn expected kind of document, received unexpectedly

Routine document type ≠ verified request.

Training example · fictional details

Keep these essentials

Expected document type is not the same as an expected document. Real sharing services and PDFs can carry unsafe links.

Report through the approved method. Do not reopen downloaded files to investigate, forward them widely or upload confidential work files to unapproved public tools.

Download the response field guide ↓