Case Library / Smishing (SMS Phishing) / Pune CFO loses Rs 56 lakh to a Microsoft Teams boss scam (2026)
Smishing (SMS Phishing) Documented incident

Pune CFO loses Rs 56 lakh to a Microsoft Teams boss scam (2026)

A Pune CFO sent Rs 56 lakh after a Microsoft Teams message from a fake CEO profile. A second Rs 1.5 crore request made her call the real CEO. What happened.

Share:

Social Engineering Examples·3 sources

On the morning of 13 July 2026, the chief financial officer of an Italian engineering company's Pune office got a Microsoft Teams message from a profile with her CEO's name and photo. He was busy with a government project, it said, and she needed to transfer Rs 56 lakh to two bank accounts. She did. The next morning came a second request, for Rs 1.5 crore. That one made her suspicious. She called the real CEO, found out she'd been tricked, and went to the police. Status: Reported to police, under investigation.

Key takeaways

  • This was CEO fraud on Teams instead of email. A name and a photo were enough.
  • "Busy with a government project" explains why the boss can't talk, and stops you from checking.
  • One phone call to the real CEO stopped the second, bigger payment.
  • The case came out as India's market regulator, SEBI, warned listed companies about CEO impersonation.

What happened

When What happened
13 July 2026, morning A Teams message from a profile with the CEO's name and photo asks her to send Rs 56 lakh to two accounts. She is working from home and pays
14 July 2026, morning A second message asks for Rs 1.5 crore
Same day She calls the real CEO, learns it's a scam, and goes to the police
19 July 2026 The Indian Express reports the case; Pimpri-Chinchwad police are investigating

The reporting doesn't explain how the fake profile was created, whether any account was hacked, or how the scammers knew who to target. No recovery or arrest had been reported.

Tip: when the "boss" messages about money and says they can't talk, that's exactly the moment to call them.

Why it worked

  • Familiar app. Teams is where colleagues really talk, so a message there feels internal.
  • Name and photo. Both are easy to copy from public profiles.
  • Built-in excuse. A busy CEO on a government project sounds important and explains the rush.
  • Working from home. No chance to walk over and ask.

The second request was the scammers' mistake. Rs 1.5 crore, a day after Rs 56 lakh, was big enough to make her stop and check.

The wider warning

Around the same time, SEBI cautioned regulated entities and listed companies about fraudsters posing as CEOs or managing directors, after an alert from India's Indian Cyber Crime Coordination Centre (I4C). The warning covered email, WhatsApp, Teams and social media, with newer tricks including deepfakes and malicious downloads that hijack WhatsApp Web sessions. The reporting doesn't say this case prompted the warning.

What would have stopped it

  • Call before you pay. Any payment request from an executive gets checked by phone on a known number.
  • Two approvers for large transfers, with no exceptions for the CEO.
  • No payments on chat alone. Teams, WhatsApp or email aren't approval channels.
  • Flag external Teams users so messages from outside the company are clearly labelled.

See also how to prevent CEO fraud and the WhatsApp CEO fraud case in India.

Common questions

What is a boss scam?

A scam where criminals pose as a company's CEO or another senior leader, usually on email or chat, and ask an employee to make an urgent payment.

How much did the Pune CFO lose?

Rs 56 lakh, sent to two bank accounts. A second request for Rs 1.5 crore was not paid.

How did she find out?

The second, larger request made her suspicious, so she called the real CEO, who knew nothing about it.

Can scammers impersonate people on Microsoft Teams?

Yes. A profile with a copied name and photo can look like a colleague. Check payment requests by phone, whatever app they arrive on.

Sources
Cite this case

Social Engineering Examples. “Pune CFO loses Rs 56 lakh to a Microsoft Teams boss scam (2026)”. Accessed 3 November 2026. https://socialengineeringexamples.com/pune-teams-boss-scam-cfo-2026

Attack Chain & Defense
1Executive impersonation
What happened

the attacker used the CEO's name and photograph. The July 19 report does not establish how those details were obtained.

The control that would have stopped it

Public executive identifying information (a CEO's name, role, and photograph on a company website, LinkedIn, or in press coverage) is very difficult to eliminate for any public-facing senior executive; the realistic control assumes this exposure exists and instead hardens the payment-verification process it later gets used against, per Stage 5's countermeasure.

2Impersonation channel
What happened

a Microsoft Teams profile displayed the real CEO's name and photograph; the report does not establish how the profile was created or whether an account was compromised.

The control that would have stopped it

Enterprise Microsoft 365/Teams administrators can enable external-sender and unverified-account warning labels, restrict who can message internal staff under an executive's display name from outside the tenant, and monitor for newly created accounts impersonating senior officials.

3Initial contact
What happened

the CFO received the message through Microsoft Teams while working from home.

The control that would have stopped it

Train employees that a message's legitimacy depends on verified sender identity, not on which application it arrives through; internal collaboration tools like Teams should receive the same scrutiny for high-stakes financial requests as external email.

4Pretext
What happened

the message said the CEO was busy with a government project and instructed the CFO to transfer Rs 56 lakh to two accounts.

The control that would have stopped it

Treat an "unavailable executive plus urgent, confidential payment" narrative as a fraud warning sign and require finance staff to verify the request through an independent channel before acting.

5Stage 5
What happened

Payment instruction and fund transfer (objective completion, first tranche): the CFO transferred Rs 56 lakh to two specified bank accounts without an out-of-band verification call, completing the attacker's financial objective for the initial request.

The control that would have stopped it

Require mandatory out-of-band verification, a phone call to a known, pre-established number rather than a reply in the same chat thread, before executing any executive-originated wire transfer; applied here, this single control would have prevented the entire Rs 56 lakh loss.

6Detection
What happened

a second message the next morning demanded Rs 1.5 crore. The CFO became suspicious, called the real CEO and then approached police.

The control that would have stopped it

require a callback to the known executive contact and independent authorization before releasing funds. In this incident, the CFO's callback exposed the fraud before the second demand was paid.

Quick Facts
Victim
CFO
(49, female) of the Pune office/subsidiary of an Italy-headquartered engineering company (company name not publicly disclosed in reporting)
Location
Pune, Maharashtra, India
(CFO and engineering firm); Pimpri-Chinchwad police investigated; parent company headquartered in Italy
Date
2026-07-13
Impact
The CFO reported transferring Rs 56 lakh to two bank accounts.
BasisreportedAmount from the police complaint as reported; the second demand was never paid
A second demand for Rs 1.5 crore the following morning was not paid after she called the real CEO. The transferred amount and the additional attempted demand are separate; no USD conversion is used.
Status
Documented incident
Case Type
Real-World Incident
Sector
Financial Services & Insurance, Manufacturing & Industrial
Threat Actor
unknown
Explore more

Related Cases

Browse by what this case has in common with others in the library.