VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

How We Can Be Scammed | How a Fake Bank SMS and Phishing Website Works

A message claims your bank account will be frozen unless you verify it immediately. The sender name looks familiar and the link leads to a polished login screen. A fraudulent message can borrow a real bank’s identity while directing you to a page the bank does not control.

Do not open the link. Use the genuine banking app or a verified bank phone number. If you entered credentials or approved a payment, call the bank’s fraud team immediately.

  • Pause before sending money or sharing credentials.
  • Verify the identity through an independent trusted channel.
  • Check the actual recipient and purpose of any payment.
  • Contact your bank immediately if financial information was exposed.
  • Keep evidence and use official reporting routes.

How this scam works

The fraudulent alert creates a problem such as account suspension or a suspicious transaction. A counterfeit page then collects banking credentials or approval codes. The attacker may attempt real transactions while the victim believes they are completing a security check.

Where trust breaks down

A sender label, HTTPS padlock and familiar logo do not establish that a bank operates a page. Trust information confirmed through your genuine account and independently contacted bank.

A realistic example

A working adult receives an urgent message about a blocked card. Rather than opening the link, the person opens the genuine banking app and checks for notices, then contacts the bank through its verified number. This is a fictional scenario.

Common mistakes

The victim may repeatedly enter a password, approve an unexpected transaction or share an OTP. Those steps can turn a suspicious message into account compromise.

Why the request feels believable

The scammer attaches an unexpected instruction to a familiar everyday task. Because the recipient already recognises the subject, the request can feel more credible than an unrelated message. But a plausible subject is not independent evidence of who sent the instruction.

Why urgency changes our judgement

A deadline or threat makes verification seem costly. The reader may believe there is no time to check. In fact, a request involving money, identity or account access deserves more verification when the claimed consequences are serious. An urgent message does not create authority.

What a polished page proves

Logos, typography, professional forms and a secure-looking web address can be copied. HTTPS can encrypt communication with a fraudulent site; it does not certify that the site belongs to the company named on its page. Visual quality is not the same as independently verified identity.

The trust-boundary test

Ask what the sender wants to receive: money, a password, identity documents, a one-time code, an approval or access to a device. Then ask how you can establish the recipient’s identity without using information supplied by that recipient. This separates the story from the actual risk.

How to verify independently

Use an application you already trust, a known official website, an existing card-back telephone number or an appropriate official register. Do not rely on a new contact number or link supplied in the suspicious message. Search advertisements can also mislead, so prefer saved, verified destinations.

The difference between a claim and a record

A message saying money has been sent is a claim. A transaction confirmed in your own bank is a record. A website displaying an investment balance is a claim unless assets and ownership can be verified independently. Train yourself to distinguish what another person asserts from what a trusted system confirms.

What to preserve after an incident

Keep the date, time, sender details as displayed, requested amount, transaction references, relevant messages and any screenshots already available. Avoid reopening suspicious links solely to gather evidence. Record precisely what information you disclosed and whether any financial authorisation occurred.

Why quick reporting matters

Delaying because of embarrassment or uncertainty can leave accounts exposed. The bank or service provider needs factual information to decide what restrictions or investigations are possible. Recovery cannot be promised, but prompt contact can help reduce further damage and preserve evidence.

How to teach children and older relatives

Practise with fictional messages rather than real suspicious links. Ask learners to identify the claim, the requested action, the possible loss and the independent checking route. Repeat the same exercise with different stories until the checking process becomes familiar.

How workplaces can reduce exposure

Organisations should define approved payment routes and require independent confirmation of unusual financial instructions. Staff should know where to report suspicious messages without being pressured to resolve them alone. Good procedures make safe verification the normal workflow.

What to do if you already responded

Tell the bank whether you opened a link, entered passwords or card details, installed software or approved a transaction. Ask about emergency account restrictions, revoke exposed sessions and preserve records.

Frequently asked questions

Does a familiar name prove the sender is genuine?

No. Names, logos and caller displays can be copied. Check through a separate trusted route.

What if the sender knows personal details?

Correct personal details do not establish authority. Avoid disclosing more information before verification.

Can a small payment still be dangerous?

Yes. A small payment may be used to collect credentials or encourage a larger later transfer.

Is a website safe because it uses HTTPS?

No. Encryption does not prove that the site belongs to the institution it claims to represent.

What if I already clicked a link?

Stop interacting. Assess whether you entered information, installed software or approved transactions; take the appropriate security steps.

Should I pay another fee to reverse the first payment?

Do not pay an unverified party to unlock or recover funds. Contact the bank or legitimate service directly.

What should I report to the bank?

Explain the actual transactions, credentials disclosed, devices affected and approvals given. Preserve references and dates.

Where can Singapore readers get help?

Use your bank’s official emergency channel for financial exposure and ScamShield or 1799 for scam-related checks.

Related eduKate reading

Official guidance and editorial scope

For current advice, consult the relevant official Singapore authority, ScamShield and your financial institution’s verified support channels. The worked example is fictional. This article explains general risk patterns, not a verified account of a specific incident or a guarantee of recovery. Procedures differ by jurisdiction.