An email arrives that looks like it is from the Income Tax Department: a refund is pending, click here to confirm your bank details. The logo is right and the language sounds official, but the link leads to a page built to steal a password or an OTP. This is phishing, and in a small office the best defence is not an expensive tool but short, regular phishing training that teaches every person what these messages look like and what to do next.
How big a risk is phishing?
Phishing is one of the three most common ways attackers get in. The Verizon Data Breach Investigations Report 2025 found that 16% of breaches began with phishing, behind the abuse of stolen or guessed credentials (22%) and the exploitation of software vulnerabilities (20%). The same report found a human element, such as someone clicking a link or being tricked, in about 60% of breaches. And a password typed into a fake login page becomes a stolen credential, so phishing and the top category are closely linked.
The forms phishing takes
- Email phishing. A fake message that copies a government department, a bank, a software vendor or a client.
- SMS and WhatsApp (smishing). Short messages with a link: a refund, a parcel, an electricity bill, a KYC update.
- Phone calls (vishing). Someone claiming to be from a bank, a courier, “Microsoft support” or the police, asking for an OTP or for remote access to a computer through AnyDesk or a similar tool.
- Spear phishing. A message written for one person, using details from the firm’s website, LinkedIn or a real client conversation.
Lures that target CA firms
Use these in your training, because they are the ones your team will actually see:
- Fake income-tax notices and refund messages. “Your refund of ₹14,500 is approved, verify your account.” The Income Tax Department asks people to report phishing by forwarding the email to [email protected] and [email protected]. Real refunds are checked by logging in to the e-filing portal yourself, never through a link.
- Fake GST notices. A “show cause notice” or “demand order” as a ZIP or PDF attachment, timed around return deadlines. Check notices on the GST portal, not in the email.
- Changed bank details on a client or vendor invoice. An email, sometimes from a real but hacked mailbox, saying “our account has changed, please pay this invoice by NEFT/RTGS to the new account”. Always confirm a bank-detail change by phoning a number you already have.
- UPI collect requests and QR codes. “Scan to receive your payment.” You never need to enter a UPI PIN to receive money; entering it sends money.
- Software renewals and logins. “Your Tally licence / Microsoft 365 mailbox expires today, sign in to renew.”
Red flags to teach
- Urgency or threats. “Account will be suspended in 24 hours”, “penalty will be levied today”.
- A sender address that does not match. The display name says “Income Tax Department” but the address is from a look-alike domain. Check the full address, not the name.
- Links that go somewhere else. Hover over a link (or press and hold on a phone) to see where it really goes before you tap it.
- Unexpected attachments, especially ZIP files, and Office files that ask you to “enable content”.
- Requests for secrets. No genuine bank, department or vendor asks for a password, an OTP, a UPI PIN or a full card number by email, SMS or phone. PAN and Aadhaar details should only be shared on a channel you started.
- Something slightly off. Odd phrasing, a client writing in a way they never do, or a request at an unusual time. Good phishing has few spelling mistakes now, so this is a hint, not a test.
Phishing training that works in a small team
- Ten minutes, every quarter. Show two or three real examples your office received and walk through the red flags. Short and regular beats one long annual session.
- Before the busy season. Run a refresher just before ITR and audit deadlines, when fake tax and GST messages peak and everyone is rushed.
- One place to report. Name the person (or the email address) that suspicious messages go to, and make it clear nobody gets into trouble for reporting, even after a click.
- “Call to confirm” for money. Any request to pay, change bank details, buy gift cards or share an OTP is confirmed by phone on a known number. No exceptions for partners.
- Practice emails. Free and low-cost tools can send simulated phishing to your staff. Treat the results as a lesson, not a scorecard.
What to do when someone clicks
Mistakes will happen. If someone clicks a link or enters a password or OTP on a fake page:
- Change the password of that account straight away, from a known-good device, and on any other account that used the same password (here is why reuse matters).
- Sign the account out everywhere (Microsoft 365 and Google both have this option) so a stolen session stops working.
- Check the mailbox for new forwarding rules or filters. Attackers add them to copy or hide email quietly.
- Turn on two-factor authentication if it was off. Remember that an OTP typed into a fake page can be used by the attacker too.
- If money moved, call the bank and 1930 immediately and file at cybercrime.gov.in. Speed matters for freezing a transfer.
- Tell your IT contact, and if the attachment ran or the server may be involved, follow your incident response plan.
A phished password often ends up being tried against the office server, and a malicious attachment is a common start for ransomware; see how ransomware gets into Windows servers. That is the part Prixl Warden covers: it watches the server’s sign-in logs and emails you about brute-force patterns, sign-ins outside working hours, admin sign-ins and new accounts, so a stolen password being used shows up quickly. Start your 30-day free trial.
