Practise spotting a scam before it happens to you

A cancelled order becomes a payment request.

1. A message is not proof of a refund.
2. Check whether the screen says Pay or Receive.
3. A QR-and-PIN payment sends money; it is not required to receive a refund.

Remember: Read the payment direction before approving anything.

A trial link hides the recurring amount.

1. A trial price is not the full recurring cost.
2. Read merchant, frequency and mandate amount.
3. Mandates can permit future debits under their terms.

Remember: Review the whole mandate and cancellation route before accepting.

A payment counter shows an unexpected payee.

1. A visible QR may have been replaced.
2. An unexpected recipient deserves verification.
3. Urgency is no reason to ignore the payee.

Remember: Verify recipient and amount, not just the QR sticker.

A buyer sends an edited-looking receipt.

1. Sender-provided receipts can be fabricated.
2. Your own transaction history is the check.
3. Pressure to release goods increases risk.

Remember: Verify the credit independently before releasing goods.

A stranger claims to have paid you by mistake.

1. A forwarded SMS does not establish a credit.
2. A different destination complicates the story.
3. Let the bank verify disputed transfers.

Remember: Use your bank’s process; do not improvise a stranger’s refund.

A reward page asks for a banking code.

1. An unexpected reward is a lure.
2. A bank code may authorise a sensitive action.
3. The SMS explains what the code is for.

Remember: Never disclose an OTP to someone offering a reward.

A caller claims authority and demands isolation.

1. Uniforms and badges on a screen prove nothing.
2. Secrecy prevents independent checking.
3. A “safe account” transfer is a major warning.

Remember: No Indian agency questions or arrests anyone over a video call. End the call and tell someone you trust.

An unsolicited parcel call turns into a police transfer.

1. A connected second caller is not independent verification.
2. An unsolicited allegation needs checking.
3. A personal payment demand is a warning.

Remember: Verify separately instead of staying inside the caller’s chain.

A blocking threat points to an unfamiliar page.

1. Urgency does not establish authenticity.
2. A familiar name can appear on an unrelated domain.
3. KYC is not a reason to disclose an OTP to a caller.

Remember: Check service notices through the provider you already use.

An unsolicited agent requests SIM-change approval.

1. An unsolicited upgrade can conceal a SIM change.
2. Activation codes must stay private.
3. The request’s actual purpose matters.

Remember: Unexpected loss of service also deserves prompt bank and telecom checks.

A family emergency arrives from an unknown number.

1. Voice alone is not identity verification.
2. Blocking a callback prevents verification.
3. Confirm a new payee through a trusted contact.

Remember: Pause for a separate check, even when the voice is convincing.

A stranger threatens to circulate private-looking material.

1. A threat is coercion, not proof of its claims.
2. Payment cannot ensure deletion.
3. Support can help break isolation.

Remember: Avoid further engagement; preserve evidence and report through appropriate channels.

A search result looks like the support you need.

1. A sponsored placement does not verify identity.
2. Check support details inside the official service.
3. Remote access is risky during banking.

Remember: Reach support through a known official route, not search placement alone.

A helper requests screen and device control.

1. A legitimate remote tool can still be abused.
2. Visible notifications can expose sensitive information.
3. Banking should not happen under a stranger’s control.

Remember: If access was already given, use a trusted device to contact your bank and secure accounts.

Small early payouts lead to a prepaid task.

1. An early payout does not validate the whole scheme.
2. Paying to unlock earnings changes the risk.
3. A wallet balance can be invented.

Remember: Do not let an on-screen balance pull you into repeated deposits.

A work offer turns into a threatening invoice.

1. A promised easy job can conceal coercive terms.
2. A unilateral score is not independent evidence.
3. A threat does not establish a valid legal demand.

Remember: Verify the entity and any legal notice independently; preserve the entire conversation.

An attractive offer bypasses normal verification.

1. Pay and perks do not verify an employer.
2. Job and visa conditions must match.
3. Loss of control over documents can increase danger.

Remember: Verify the employer, recruiter, visa and contract before travel.

A recruiter promises a job after a payment.

1. Verify selection with the employer itself.
2. A fee for a guaranteed job is a warning.
3. An unrelated personal payee needs scrutiny.

Remember: Check the employer’s own hiring channel before paying or sharing documents.

A commission offer asks you to move strangers’ funds.

1. Easy commission may hide an illicit money flow.
2. Your account remains tied to the transactions.
3. Someone else’s reassurance is not protection.

Remember: Do not lend account access or move unknown funds for a stranger.

An app shows profit but blocks withdrawals.

1. Guaranteed high returns deserve suspicion.
2. An app display is not verified ownership.
3. More money to unlock a balance is a warning.

Remember: Verify the broker and official app; do not treat screen profits as proof.

A new online partner recommends a private platform.

1. A relationship is not investment due diligence.
2. Secrecy limits outside advice.
3. A private platform may only simulate balances.

Remember: Keep financial verification independent of an online relationship.

A polished video claims a famous endorsement.

1. A convincing face or voice may be altered.
2. Guaranteed returns remain a warning.
3. Check the claim away from the ad.

Remember: Appearance is not authentication; verify the claim and the entity separately.

Someone promises to recover money you already lost.

1. Knowledge of your loss does not prove legitimacy.
2. Guaranteed recovery is a warning sign.
3. An upfront unlock fee can be another loss.

Remember: Keep using verified complaint channels; no demo can promise reimbursement.

A loan app asks to read contacts and messages.

1. Speed does not establish a lender’s legitimacy.
2. Contact access can expose other people.
3. Permissions must fit the actual service.

Remember: Check the lender and terms before installation; question excessive access.

A bill message includes an APK attachment.

1. A deadline can rush you past verification.
2. An unsolicited APK is not a normal proof of a bill.
3. SMS access can expose sensitive messages.

Remember: Open the provider’s official service yourself instead of installing a message attachment.

A challan message demands an app installation.

1. A fine claim should be checked independently.
2. APK attachments can be malicious.
3. Device-control access is sensitive.

Remember: Verify the notice outside the message; do not grant control to an unknown app.

A familiar contact sends a wedding APK.

1. A familiar account can be compromised.
2. An invitation does not need sensitive device access.
3. Confirm the sender through another channel.

Remember: Check unexpected app attachments even when the message comes from a contact.

A refund notice leads to an unfamiliar sign-in page.

1. A sender name can imitate an authority.
2. The destination must be independently verified.
3. A refund is not a reason to share card secrets.

Remember: Check refund status through the official service you navigate to yourself.

A points-expiry message requests card details.

1. Expiry pressure can reduce careful checking.
2. A branded page can still be unrelated.
3. Bank codes are not reward coupons.

Remember: Use the bank’s own rewards channel; keep authentication codes private.

A platform-looking email offers a badge.

1. Badges are attractive account-takeover lures.
2. Check messages within the actual platform.
3. Backup codes are account access secrets.

Remember: Protect recovery codes as carefully as passwords.

A familiar account asks you to forward a login code.

1. The code may belong to your own account.
2. A contact’s account may be taken over.
3. A separate call can verify the request.

Remember: A login code is for your sign-in, not something to forward.

A passive-income offer requests a linked device.

1. Easy income can hide abuse of your identity.
2. Linked devices can access account activity.
3. Unknown operators control what gets sent.

Remember: Do not rent messaging access; revoke unfamiliar linked devices.

A website pretends your browser needs an urgent download.

1. A page can impersonate browser chrome.
2. Use the browser’s own update mechanism.
3. Unexpected downloads can install malware.

Remember: Get updates through the app or official vendor, not an alarming page.

A social ad offers a premium product at a tiny price.

1. An extreme discount deserves extra checks.
2. Check the seller and return process.
3. Leaving the platform can remove protections.

Remember: Check the merchant and transaction protections before paying.

A resale listing uses military identity to gain trust.

1. An identity-card image can be copied.
2. Urgency is not a substitute for inspection.
3. Upfront transport charges can be a lure.

Remember: Verify the transaction, not just the person’s claimed profession.

An attractive rental demands a remote deposit.

1. Copied photos can make a fake listing convincing.
2. Verify who controls the property.
3. Pressure to pay before verification increases risk.

Remember: Confirm property and authority before sending a reservation payment.

A travel offer asks for a private transfer.

1. A confirmation claim needs operator verification.
2. Private payment may bypass normal safeguards.
3. Discouraging a check is a warning.

Remember: Confirm reservations through the transport or accommodation provider.

A prize you never entered requires a fee.

1. An unexpected prize is a common lure.
2. Advance fees can turn a prize into a loss.
3. Secrecy prevents a second opinion.

Remember: Do not pay an unexpected contact to unlock a supposed prize.

An emotional appeal points to an unrelated recipient.

1. Photos alone do not verify a fundraiser.
2. Check the organisation and recipient.
3. A verified donation route can still help promptly.

Remember: Verify where the donation goes before responding to urgency.

A supplier email requests new bank details.

1. An existing email conversation can be compromised.
2. Changed bank details need an independent callback.
3. Urgency can bypass payment controls.

Remember: Confirm bank changes through a previously trusted channel before payment.

Separate confirmed exposure from speculation.

1. Read the organisation’s own incident notice.
2. Unknown is not the same as confirmed.
3. Recovery offers can exploit worry.

Remember: Follow verified updates and watch for targeted follow-up scams.

An infected device may expose accounts and sessions.

1. An unsafe device can compromise new credentials too.
2. Session access may outlive a password change.
3. Review recovery options and active sessions.

Remember: Contain the device issue and secure accounts, sessions and recovery methods.

Practise defensive decisions in a composite incident.

1. A demand is a claim, not a complete forensic record.
2. Preserving evidence supports response.
3. Unplanned changes may destroy useful evidence.

Remember: Coordinate containment, evidence and recovery through the incident team.

Compare exposure, exploitation and vendor advice.

1. Internet exposure affects response urgency.
2. Known exploitation changes prioritisation.
3. Use the actual vendor’s affected-version list.

Remember: Use current advisories and change controls; do not patch from an unverified download.

A pending status triggers a fake fast-track offer.

1. Keep the acknowledgement and evidence.
2. Status should be checked on the official portal.
3. An unsolicited agent cannot guarantee recovery.

Remember: Use official tracking and documented contact with the relevant authority.

A restriction notice needs evidence and clear next steps.

1. Ask the bank for the reason and reference.
2. Preserve records of relevant transactions.
3. No stranger can guarantee immediate release.

Remember: Use written bank information and verified authority contacts, not release promises.

An exposure alert should lead to verified services.

1. Verify the exposure claim first.
2. Security actions belong on official services.
3. Avoid disclosing more data to unknown helpers.

Remember: Check official identity services and monitor for misuse without oversharing.

An unexpected approval request arrives on your phone.

1. Do not approve sign-ins you did not initiate.
2. A caller’s explanation is not authentication.
3. Review sessions and recovery-method changes.

Remember: Review active sessions, recovery methods and phishing-resistant authentication where supported.