A Colleague Asked for a Code. Should That Change What You Do?
A familiar sender does not make a verification code an ordinary work message. Check the requested action independently and use the authorised support route.

“Could you send me the code that just arrived? I need it to finish this.” The message appears to come from a colleague, and helping feels like the quickest way to keep the work moving.
Treat the code as part of an account action, not as a convenient piece of information to forward. The apparent relationship with the sender does not explain what the code would authorise.
Identify the action the code belongs to
Imagine a fictional small agency where a coordinator receives a message during a busy handover. A separate notification mentions a sign-in or account-recovery action they did not initiate.
Read the notification carefully through the provider’s established route. Determine which account and action it concerns without sending the code or opening a new link supplied by the requester.
A code can form part of access verification or recovery. It should not be copied into a general case note, a shared checklist or a conversation merely because somebody asks for it.
Check the request through a separate route
Contact the colleague using an established channel outside the questionable exchange. Ask what work they were trying to do and which authorised support process applies.
A familiar display name is not enough to settle the matter. The NCSC has warned that messaging-app attacks can involve impersonating someone people know and persuading them to share login or recovery codes.
Its guidance advises against sharing verification codes. The original alert addresses targeted messaging-app attacks; it is not evidence that every unusual message in your own business is such an attack. The practical point is to avoid letting familiarity replace an independent check.
Use the supported help process
If there is a genuine access problem, use the organisation’s authorised administrator or the account provider’s official help route. Do not improvise a workaround by lending another person your personal sign-in or recovery step.
What recovery options exist depends on the service and its configuration. NCSC guidance notes that some services provide backup codes and that those codes need safe storage. That is a reason to prepare an approved recovery route, not a reason to pass stored recovery material around in chat.
If you have already shared a code or approved something unexpected, tell the responsible support person promptly and follow the provider’s incident or recovery instructions. Give them the relevant context through the approved route without unnecessarily circulating the code itself.
Rehearse the conversation without real credentials
Use a fictional message and no working code. Ask a colleague to describe the action being requested, how they would verify the sender independently and where an unresolved access question goes.
The useful finish is a known support route that remains usable under pressure. Helping a colleague should not require treating an account-verification secret as an ordinary handover note.
Primary references: NCSC: messaging-app targeting, NCSC: setting up two-step verification.
Continue with a related working question
Explore Check the Request Behind a Familiar-Looking Message, or read The Invoice Looks Familiar. Why Did the Bank Details Change?.
For a written learning option, see the Work Safely Online with Matze course overview. You use your own authorised tools and review the exercises yourself.
Review the course contents and current terms. Affiliate link: Superstore may earn a commission if you buy.




Discussion 0
What did this article make you think about?