A courier asks for a code before delivery
Separate a real parcel handover code from an unrelated account-login request.
Delivery services sometimes use collection codes. Attackers exploit that familiarity by calling a login or password-reset code a delivery confirmation. Check the actual order and the purpose written in the message before sharing anything.
Find the real order
Open your existing retailer app and compare the carrier, status and handover instructions. Knowing your name or address does not authenticate a courier. If the parcel is unexpected, check with the alleged sender through a known contact. Do not assume every incoming call is genuine merely because you are waiting for a package.
Notice when the task changes
Illustrative example: a caller first asks whether you are home, then says a messenger login code is needed to fix the address. That new request is the turning point. Read the original message and do not relay the digits. Contact delivery support from the real order, not from a link or number supplied by the caller.
Recover the account actually affected
If a code was disclosed, identify its sending service and follow that service’s recovery process. Review active sessions and recovery methods. Reporting the fake courier to the shop does not terminate access to a different account. Keep messages privately and avoid posting active codes in a review. A payment or remote-access request requires its own provider response as well.
Quick checklist
- Check the real order.
- Read the service named in the code.
- Reject unrelated account approvals.
- Secure the account actually affected.
Sources and editorial responsibility
Prepared by the KtoTam.to team. Examples are illustrative, not user reports. Number lookups and reviews do not verify a caller’s identity. Check service terms and device instructions with the original provider.
Found an error? Tell our team which guide needs correcting and include a supporting source.
Report a correction