How To SurviveLife-Safety Intelligence for India
Language
Automatic translation
Case Study · Cyber & Financial Crime

Jaipur scam: a false director message preceded ₹6.80 crore in transfers

A company accounts head reportedly sent ₹6.80 crore to three accounts after messages impersonating a director. Police announced a 12th arrest on 26 September.

DateTransfers reported on 24 August 2026; latest arrest update 26 September 2026LocationJaipur company, Rajasthan, India; digital contact and transfer route crossed locations
01
Case Study

What happened here

Reported transfers₹6.80 crore
Transfer date24 August 2026
Reported beneficiary accounts3
Complaint25 August 2026
Arrests announced by 26 September12
RecoveryNot established by the reviewed latest report

A company accounts head reportedly sent ₹6.80 crore to three accounts after messages impersonating a director. Police announced a 12th arrest on 26 September.

The payment request appeared to come from inside the company

Rajasthan police say an accounts head at a Jaipur company received WhatsApp instructions that appeared to come from a director. Investigators allege the offenders gained access to a company computer or messaging session, changed the apparent contact identity and recreated earlier chat context. The record reviewed here does not establish every technical step independently.

Transfers and discovery

On 24 August 2026, the firm reportedly transferred ₹6.80 crore to three bank accounts. The company later confirmed that its directors had not authorised the payments and reported the fraud on 25 August. The reported amount is the value transferred, not a confirmed final loss or recovery total.

The investigation continued

Early September reporting described six arrests. Police later said the number had risen to 12 after a further arrest announced on 26 September. Those arrested are accused, not convicted. Investigators describe supporting bank accounts and movement of funds, but the public record does not establish how much money has ultimately been returned to the company.

Where the control failed

The request was treated as an instruction from a trusted senior person within a familiar chat thread. A high-value payment required a second, independent authorisation channel and beneficiary verification. Even a familiar profile, old message history or apparent urgency cannot replace a call to a known number and a documented approval.

If your organisation notices a false instruction

Stop further transfers, call the bank’s official fraud contact, preserve chats and payment references, and report immediately to 1930 and cybercrime.gov.in. Have a separate incident lead check account access and tell staff which messages are no longer trustworthy. Do not publicly name uninvolved employees or promise recovery before the bank confirms it.

  1. Suspects allegedly gained access to messaging context and created an apparent director identity
  2. Accounts head reportedly transferred ₹6.80 crore to three accounts
  3. Company complained after directors denied authorising payments
  4. Police reported initial arrests, later reaching six and then eight
  5. Police announced a 12th arrest and continued tracing the network

Why consequences escalated

  • The apparent trusted sender and recreated chat history made the instruction persuasive.
  • A messaging account or profile is not independent proof of authority.
  • A second channel to a known number could have interrupted the payment.
  • Three beneficiary accounts were reported for the transfers.
  • The announced arrest count changed as the investigation progressed.
  • Transfer amount, held funds and money returned are distinct measurements.

Failures and risk multipliers

  • Approving a large transfer solely from a chat instruction.
  • Using a number supplied in the suspicious message to verify it.
  • Skipping beneficiary-account checks because the request looks urgent.
  • Treating a familiar profile photo or prior conversation as authentication.
  • Failing to report the transfer promptly to the bank and 1930.

People closest to the evidence

“I4C and SEBI warn that senior-executive impersonation can arrive over messaging and direct subordinates to transfer funds”

SEBI press release 40/2026 · General advisory, not a finding about this accused group · Source ↗

Actions that reduce risk

  1. Require two-person approval for high-value or new-beneficiary payments.
  2. Confirm urgent executive requests by calling a previously verified number.
  3. Separate payment creation from release authority.
  4. Review active linked messaging sessions and device access.
  5. Train staff to pause confidential or time-pressured payment requests.
  6. Contact the bank and 1930 immediately if a payment was sent.
  7. Document actual funds held and returned separately.
02
Watch & learn

Video reports & learning

Captions
Exact case, external publisher video

Jaipur company boss identity hijacked

NDTV Rajasthan · Hindi

Relevant report dated 23 September; publisher page player, not verified as a YouTube embed

Exact case, external publisher video · Open on publisher websiteJaipur company boss identity hijackedNDTV Rajasthan · Hindi
03
Incident data

The broader evidence

Survival sequence

  1. Stop pending payments.
  2. Call the executive using an existing contact record.
  3. Notify the bank's fraud team immediately.
  4. Preserve chats, device details and payment references.
  5. Call 1930 and file at cybercrime.gov.in.
  6. Use an incident lead to secure affected accounts without destroying evidence.
  7. Do not promise that frozen money has been recovered until confirmed.
₹6.80 croreReported value transferredNot confirmed final net loss
3Beneficiary accountsPolice account
12Arrests announced by 26 SeptemberAllegations, not convictions
1930Cyber-fraud reporting helplineIndia
EntryApparent trusted identityDirector name and chat context used
PressureUrgent payment requestAccounts head asked to transfer money
Loss eventThree account transfers₹6.80 crore reportedly sent
DiscoveryDirector checkDirectors denied authorisation
ResponseBank and police reportComplaint and fund tracing
InvestigationContinuing arrestsTwelve reported by 26 September

Limitations

  • No complete police case diary, banking ledger or forensic device report was publicly reviewed.
  • The exact access method remains an allegation in reporting.
  • The ₹6.80 crore figure is value transferred; recovery is not established here.
  • Arrests are not convictions.
  • NDTV's exact-case video is external and may not embed in the site's player.
  • The cover is an editorial reconstruction.

Immediate actions

  • Publish a payment approval rule that no chat message can override.
  • Call the executive on a known number for any urgent transfer.
  • Check beneficiary names and accounts independently.
  • Review linked-device sessions and access logs.
  • Put the bank fraud desk and 1930 in the finance team's incident contacts.
Community discussion

Questions, experience and constructive safety discussion

Comments publish immediately unless security controls identify spam. Please do not post private information, unsupported allegations or unsafe instructions.

Leave a comment

* Name and email are required. Your email address will not be published.


The reCAPTCHA verification period has expired. Please reload the page.