Digital Forensics Investigation of Financial Cybercrime in Nepal: A Technical Analysis of the Rautahat KYC Fraud and Khalti Impersonation Incidents

 


Digital Forensics Investigation of Financial Cybercrime in Nepal: A Technical Analysis of the Rautahat KYC Fraud and Khalti Impersonation Incidents

Author: Kabin Khadka
Research Category: Digital Forensics | Cybercrime Investigation | Mobile Forensics | Financial Forensics | OSINT
Country: Nepal
Research Date: 8 November 2026
Publication: https://blog.kabinkhadka.com.np


Executive Summary

The rapid adoption of digital financial services in Nepal has introduced new opportunities for financial inclusion, electronic payments and mobile banking. At the same time, cybercriminals have increasingly exploited users' trust in financial institutions through impersonation, phishing, credential theft and social engineering.

Two publicly reported incidents from October 2026 provide valuable opportunities to examine these threats from a digital-forensics perspective:

  1. The Rautahat KYC-update fraud investigation, involving reported financial losses of approximately NPR 4.98 million.
  2. The Khalti employee impersonation investigation, involving allegations of unauthorized access to digital wallets and bank accounts through screen-sharing requests and OTP disclosure.

The Rautahat investigation is particularly significant because police reportedly recovered multiple mobile phones, SIM cards, bank deposit slips, ATM cards, cheque books, storage devices and handwritten financial records.

The Khalti investigation provides another perspective on how impersonation and manipulation of authentication processes can facilitate unauthorized financial activity.

This research examines the publicly available information surrounding both incidents and develops a technical framework for investigating similar financial cybercrime cases.

The analysis focuses on:

  • Mobile device forensics.
  • WhatsApp and communication evidence.
  • SIM identification and device attribution.
  • Phishing and Google Forms investigation.
  • OTP-related authentication evidence.
  • Bank and digital-wallet transaction tracing.
  • Cryptocurrency investigation.
  • Digital evidence preservation.
  • Chain of custody.
  • Forensic reporting and investigative limitations.

Research limitation: This documentation is based on publicly available police announcements and media reports. No confidential police records, original seized devices, private banking records or actual forensic extraction reports were available. Technical workflows presented here are proposed forensic procedures and educational reconstructions, not claims about examinations actually performed by Nepal Police.


1. Introduction

1.1 Background

Digital financial services have significantly changed the financial environment in Nepal.

Services such as mobile banking, digital wallets, QR payments and online financial transactions have made everyday payments easier.

However, the same digital environment creates opportunities for attackers to exploit weaknesses in human awareness, authentication practices and information security.

Unlike traditional financial crimes, digital financial fraud can involve multiple communication platforms, electronic identities, mobile devices, bank accounts and payment intermediaries.

An investigation may therefore require evidence from several different sources.

For example, a single financial fraud incident may involve:

  • A telephone call used to contact the victim.
  • A WhatsApp conversation used to establish trust.
  • A phishing form used to collect personal information.
  • An OTP used during authentication.
  • A mobile application used to access a financial account.
  • A bank transfer used to move the stolen funds.

Each event creates a different category of evidence.

Digital forensics provides the methodology for identifying, preserving, examining and interpreting these artifacts.

1.2 Research objectives

The primary objectives of this research are:

  1. Examine publicly reported financial cybercrime incidents in Nepal.
  2. Understand the reported techniques used in KYC-related impersonation.
  3. Identify potential sources of digital evidence.
  4. Develop a forensic methodology for mobile-device examination.
  5. Understand SIM-to-device correlation and attribution.
  6. Explain how financial transactions can be reconstructed.
  7. Examine the importance of preserving electronic evidence.
  8. Identify the limitations of publicly available investigative information.
  9. Develop a practical framework for future financial cybercrime investigations.

1.3 Research methodology

This research uses an open-source investigative approach.

The information is organized into five categories:

Category Description
Official information Police announcements and government publications
Media reporting Public reports from established news organizations
Technical interpretation Analysis of reported attack techniques
Forensic methodology Proposed evidence collection and examination procedures
Investigative hypotheses Questions requiring further evidence

This classification prevents reported allegations from being presented as established forensic findings.


2. Case Study A: Rautahat KYC-Update Fraud

2.1 Incident overview

In October 2026, Nepali media reported that Rautahat Police had arrested three individuals in connection with an alleged financial fraud operation involving impersonation of bank and digital-wallet employees.

According to The Himalayan Times, investigators had received 22 complaints involving reported financial losses of NPR 4,987,333.

The reported arrests took place on 9 October 2026 in Gaur Municipality, Rautahat.

The three individuals identified in media reporting were:

  • Mohammad Sahil.
  • Saloni Kumari Soni.
  • Nitesh Kushwaha.

The allegations involved obtaining sensitive financial information by claiming to represent banking or digital-payment organizations.

The suspects were reported to have used telephone calls, WhatsApp communications and video calls to contact potential victims.

These individuals were arrested in connection with the investigation. Their arrest must not be interpreted as proof of guilt.

2.2 Reported attack methodology

The reported operation can be examined through several stages.

Stage 1: Victim identification

The alleged operators contacted potential victims using mobile telephone numbers.

The objective was reportedly to identify individuals using banking and digital-wallet services.

Stage 2: Organizational impersonation

The callers allegedly introduced themselves as representatives of banks or eSewa.

They used KYC updates as a reason for contacting customers.

KYC, or Know Your Customer, is a customer-identification process used by financial institutions to verify customer identities.

Attackers can exploit the public's familiarity with KYC requirements to create urgency and trust.

Stage 3: Social engineering

Victims were reportedly contacted through telephone calls and WhatsApp.

The callers allegedly used video calls and other communication techniques to convince victims that they were interacting with legitimate representatives.

Stage 4: Collection of sensitive information

According to reporting, victims were directed to Google Forms and asked to provide financial information.

The reported use of screen sharing created an additional risk because sensitive information displayed on the device could potentially become visible to another party.

Stage 5: Unauthorized financial activity

Police reported that information obtained through these interactions was allegedly used to access victims' bank and digital-wallet accounts.

Funds were reportedly transferred to other accounts and through QR-based transactions.

A complete technical reconstruction of the authentication and transfer process is not available in the public reporting.

2.3 Reported physical and digital evidence

The reported seizure inventory is particularly important for understanding the potential scope of a financial cybercrime investigation.

Evidence Reported quantity
Mobile phones 7
SIM cards 11
Bank deposit slips 30
ATM cards 3
Cheque books 3
Pen drive 1
Memory cards 2
Nepali currency NPR 162,210
Indian currency INR 3,236

Additional reported materials included diaries, notebooks containing financial records, handwritten calling scripts and bank-related documents.

These items represent several possible evidence sources.

Mobile phones: Potential communication, application, authentication and transaction artifacts.

SIM cards: Potential subscriber and telecommunications associations.

Bank deposit slips: Potential financial transaction references.

ATM cards: Potential account associations requiring verification.

Pen drive and memory cards: Potential stored documents, spreadsheets, media and other relevant files.

Handwritten records: Potential information about financial movement and communication procedures.

The existence of an item does not establish its contents or evidentiary significance. Those require examination.


3. Case Study B: Khalti Employee Impersonation

3.1 Incident overview

On 9 October 2026, Nepal Police published an announcement concerning four individuals arrested for allegedly impersonating official Khalti employees.

The individuals identified in the announcement were:

  • Subham Kumar.
  • Aniket Yadav.
  • Pawan Kumar Chaudhary.
  • Rishi Ganga.

Police reported that the suspects allegedly contacted victims using different mobile numbers and requested access to their mobile screens.

They allegedly obtained OTP codes and used the information to gain unauthorized access to bank and digital-wallet accounts.

The arrests were reported by the District Police Range, Bhaktapur, at an apartment in Hatiban, Lalitpur.

The Bhaktapur District Court reportedly authorized five days of investigative custody.

The police announcement describes allegations and investigative actions, not a final judicial determination.

3.2 Reported impersonation techniques

The reported methods involved exploiting trust in the Khalti brand.

The alleged callers represented themselves as official employees and used different explanations to persuade victims to cooperate.

These reportedly included:

  • KYC updates.
  • Bank-account linking.
  • Prevention of account closure.
  • Digital payment services.
  • Electronic payment speaker offers.
  • Claims of free or discounted transfers.

The alleged objective was to convince victims to disclose sensitive information or share their mobile screens.

3.3 OTP and authentication abuse

An OTP is a One-Time Password used as an additional authentication factor.

OTP systems are designed to help verify that a user is authorized to perform an action.

However, the security benefit can be defeated when users are manipulated into disclosing their OTPs.

There are important technical distinctions between different types of OTP compromise:

Social-engineering disclosure: A victim voluntarily shares the OTP with an impersonator.

SIM swapping: An attacker obtains control of a victim's telephone number through an unauthorized SIM replacement or activation.

Malicious application abuse: A malicious application obtains access to messages or other sensitive information.

Network-level interception: An attacker exploits weaknesses in telecommunications infrastructure or related signaling systems.

The Khalti police announcement supports an allegation involving OTP disclosure. It does not establish that SIM swapping, malware or telecommunications interception occurred.

These possibilities must not be confused.


4. Digital Evidence Identification and Classification

An effective financial cybercrime investigation begins by identifying every potential evidence source.

For these cases, evidence can be divided into six major categories.

4.1 Mobile device evidence

Potential sources:

  • Android or iOS devices.
  • Device model and serial number.
  • IMEI.
  • Installed applications.
  • Application databases.
  • Browser history.
  • SMS messages.
  • Notification records.
  • Relevant downloaded files.
  • Device timestamps.

4.2 Communication evidence

Potential sources:

  • WhatsApp conversations.
  • Call logs.
  • SMS messages.
  • Voice recordings.
  • Relevant video files.
  • Contact information.
  • Communication timestamps.

Investigators should preserve original records where possible and obtain service-provider information through lawful procedures.

4.3 SIM and telecommunications evidence

Potential sources:

  • ICCID.
  • IMSI.
  • MSISDN.
  • Subscriber registration information.
  • Call-detail records.
  • Relevant network records.

A telephone number alone cannot reliably establish the identity of the person using it.

4.4 Financial evidence

Potential sources:

  • Bank statements.
  • Transaction reference numbers.
  • Digital-wallet records.
  • QR payment records.
  • Deposit slips.
  • ATM transactions.
  • Recipient account information.
  • Exchange transaction records.

4.5 Web and phishing evidence

Potential sources:

  • Original URLs.
  • Google Forms pages.
  • Domain registration records.
  • DNS records.
  • Redirect information.
  • Browser artifacts.
  • Screenshots.
  • Relevant service-provider records.

4.6 Storage-device evidence

Potential sources:

  • USB flash drives.
  • Memory cards.
  • External storage.
  • Documents.
  • Spreadsheets.
  • Images.
  • Archives.
  • Deleted-file remnants, where recoverable.

5. Mobile Device Forensics Methodology

Mobile devices can contain substantial information about communication, user activity and financial transactions.

However, mobile examination requires careful handling because interacting with a device can change its state.

5.1 Initial examination

Before examination, document:

  • Device manufacturer.
  • Model.
  • Serial number.
  • IMEI, where appropriate.
  • Operating system.
  • Physical condition.
  • Screen condition.
  • Power state.
  • Network connectivity.
  • SIM and memory-card presence.
  • Collection date and time.

Photograph the device and its condition before conducting further examination.

5.2 Evidence acquisition

The acquisition method depends on the device, operating system, encryption status and legal authorization.

Possible acquisition methods include:

Method Description
Logical acquisition Obtains data accessible through supported interfaces
File-system acquisition Obtains accessible file-system information
Physical acquisition Attempts to acquire a device-level image, where supported
Cloud acquisition Obtains relevant cloud records through authorized procedures

Not every acquisition method is available for every device.

Modern Android and iOS security controls can significantly limit access to device data.

5.3 WhatsApp forensic examination

WhatsApp may contain useful communication artifacts.

Potential examination areas include:

  • Chat history.
  • Contact information.
  • Message timestamps.
  • Media attachments.
  • Group information.
  • Relevant voice messages.
  • Available call information.
  • Database metadata.

Investigators should consider the following questions:

  1. Which account was used?
  2. Which contacts communicated with the victim?
  3. When did communication begin?
  4. Were there instructions to share an OTP?
  5. Were suspicious URLs transmitted?
  6. Was there communication immediately before an unauthorized transaction?

A recovered chat record must be interpreted carefully.

A WhatsApp account's registration does not automatically establish who physically operated the device.

5.4 Timeline reconstruction

A forensic timeline can help correlate communication with financial activity.

Example using fictional training data:

Event Time (UTC) Source
Initial contact 04:10 Call log
WhatsApp message 04:15 Chat export
Form opened 04:18 Browser history
OTP received 04:21 SMS
Financial transaction 04:24 Bank record

The times above are illustrative, not actual events from either investigation.

Investigators should preserve the original timestamp and document any timezone conversion.


6. SIM Card Identification and Attribution

SIM identification is an important part of telecommunications investigations.

Four identifiers must be understood.

Identifier Meaning
MSISDN Telephone number
IMSI Subscriber identity used by the mobile network
ICCID SIM card identifier
IMEI Mobile equipment identifier

These identifiers answer different questions.

For example:

  • MSISDN identifies the telephone number associated with a subscription.
  • IMSI identifies the mobile network subscriber identity.
  • ICCID identifies the SIM card.
  • IMEI identifies the mobile equipment.

6.1 SIM-to-device correlation

Investigators may correlate SIM identifiers with device identifiers using authorized telecommunications records.

A correlation table could look like this:

SIM reference Device reference Telephone number Evidence status
SIM-01 DEV-01 Restricted Under examination
SIM-02 DEV-02 Restricted Under examination
SIM-03 DEV-01 Restricted Under examination

This is a fictional training example.

The purpose is to determine whether different SIM cards were used in the same device or whether a particular SIM was associated with multiple devices.

6.2 Attribution limitations

SIM ownership is not proof of actual usage.

A SIM may be:

  • Registered to another person.
  • Shared.
  • Replaced.
  • Transferred.
  • Used in a different device.
  • Used without the registered owner's knowledge.

Reliable attribution requires multiple independent evidence sources.


7. Google Forms and Phishing Investigation

Google Forms is a legitimate service. However, legitimate platforms can be misused to collect sensitive information through deceptive forms.

In a financial fraud investigation, a Google Forms link should be treated as a potential evidence source.

7.1 Evidence collection

Document:

  • Original URL.
  • Date and time received.
  • Sender information.
  • Screenshots.
  • Form title.
  • Displayed organization name.
  • Requested information.
  • Redirect behavior.
  • Related communication.

Do not submit real personal or financial information into a suspicious form.

7.2 Technical investigation

A controlled examination may involve:

  1. Extracting the original URL from the message.
  2. Recording its exact contents.
  3. Identifying the hosting platform.
  4. Recording redirects.
  5. Examining the displayed form content.
  6. Documenting any suspicious branding.
  7. Preserving available metadata.
  8. Requesting relevant provider records through lawful channels.

7.3 Attribution challenges

A Google Forms URL does not automatically identify its creator.

Publicly visible information may be insufficient to establish:

  • The form owner's identity.
  • The account used to create it.
  • The location of the operator.
  • The identity of the person who accessed submitted information.

Provider-side records and independent evidence may be required.


8. OTP and Authentication Evidence Analysis

Authentication evidence can help establish whether an unauthorized financial transaction followed a suspicious interaction.

A forensic investigation should examine:

  • OTP delivery timestamps.
  • Login records.
  • Device-registration events.
  • Password-reset events.
  • Authentication notifications.
  • Transaction authorization records.
  • Bank or wallet session information.

8.1 Authentication timeline

A sample investigation timeline:

Step Event Evidence
1 Victim receives suspicious call Call record
2 Victim receives a form link WhatsApp record
3 Victim receives OTP SMS record
4 New login or authentication event Provider record
5 Unauthorized transaction Bank statement
6 Recipient account receives funds Bank record

The timeline is a proposed investigative model.

A close temporal relationship between events is useful, but it does not independently prove causation.


9. Financial Forensics and Transaction Tracing

Financial forensics examines the movement of money and the relationship between financial accounts.

The reported NPR 4,987,333 loss in the Rautahat incident makes transaction reconstruction an important research area.

9.1 Transaction data collection

Relevant records include:

  • Transaction ID.
  • Originating account.
  • Recipient account.
  • Amount.
  • Transaction timestamp.
  • Payment channel.
  • Bank reference.
  • Available authentication information.

9.2 Transaction correlation

Investigators should determine:

  • Which victims reported losses?
  • Which transactions are associated with each complaint?
  • Did multiple victims transfer money to common accounts?
  • Were funds moved through intermediary accounts?
  • Were withdrawals made after transfers?
  • Were digital-wallet and bank records consistent?

9.3 Example transaction ledger

The following is fictional data for forensic training.

Transaction Sender Receiver Amount
TX-001 Victim-A Account-X NPR 25,000
TX-002 Victim-B Account-X NPR 40,000
TX-003 Account-X Account-Y NPR 50,000
TX-004 Account-Y Wallet-Z NPR 15,000

This example demonstrates how a transaction graph can identify common destination accounts.

However, an account receiving money does not automatically establish criminal participation by its owner.

Investigators must establish account control, transaction authorization, relevant knowledge and other supporting facts.


10. Cryptocurrency and Blockchain Investigation

Media reporting on the Rautahat incident mentioned suspicion that some proceeds might have been transferred through Binance and converted into cryptocurrency.

This has not been established through a publicly available forensic report.

Nevertheless, cryptocurrency investigation is an important part of modern financial forensics.

10.1 Relevant evidence

Potential sources include:

  • Exchange account information.
  • Exchange KYC records.
  • Deposit and withdrawal records.
  • Wallet addresses.
  • Transaction hashes.
  • Blockchain timestamps.
  • Bank transfer records.
  • Relevant device artifacts.

10.2 Blockchain transaction analysis

A blockchain explorer can show publicly recorded transactions on supported networks.

Investigators can examine:

  • Transaction hash.
  • Sending address.
  • Receiving address.
  • Transaction value.
  • Block number.
  • Transaction timestamp.
  • Transaction status.

However, blockchain visibility does not automatically establish the real-world identity of an address owner.

Attribution requires supporting evidence, such as properly obtained exchange records and verified links between accounts, devices and individuals.


11. Digital Evidence Preservation and Chain of Custody

Evidence integrity is fundamental to digital-forensics investigations.

Improper handling can compromise the reliability of evidence.

11.1 Evidence identification

Every item should receive a unique evidence identifier.

Example:

Evidence ID Description
EV-001 Android smartphone
EV-002 SIM card
EV-003 USB flash drive
EV-004 Memory card
EV-005 Bank deposit slips

These identifiers are illustrative.

11.2 Evidence acquisition

Document:

  • Acquisition date.
  • Acquisition time.
  • Examiner identity.
  • Acquisition method.
  • Tools and versions.
  • Device condition.
  • Errors and limitations.

11.3 SHA-256 verification

SHA-256 is a cryptographic hash function that produces a 256-bit digest.

For example, on Linux:

sha256sum evidence_image.dd

For Windows PowerShell:

Get-FileHash .\evidence_image.dd -Algorithm SHA256

Record the resulting hash in the case documentation.

A matching hash supports the conclusion that the compared data is unchanged between the two verification points.

Hashing alone does not prove that the original evidence was authentic or correctly acquired.

11.4 Chain-of-custody documentation

A chain-of-custody record should contain:

Field Description
Case ID Investigation reference
Evidence ID Unique item identifier
Collected by Authorized collector
Collected date Collection date and time
Transferred by Person transferring evidence
Received by Person receiving evidence
Storage location Authorized evidence storage
Purpose Reason for transfer or access
Signature Appropriate authorization and acknowledgment

Every transfer, examination and storage change must be documented according to the applicable procedures.


12. Practical Digital Forensics Laboratory

The following laboratory exercises are designed for students and beginner digital-forensics investigators.

They use fictional evidence and must not be confused with actual police evidence from the reported cases.

Laboratory 1: Mobile Device Examination

Objective: Understand mobile-device evidence.

Tools:

  • Autopsy.
  • Android forensic acquisition tools.
  • A legally acquired training image.

Tasks:

  1. Identify device-related artifacts.
  2. Examine available application information.
  3. Identify relevant timestamps.
  4. Prepare an evidence summary.

Expected output: Mobile forensic examination report.

Laboratory 2: WhatsApp Evidence Analysis

Objective: Examine communication evidence.

Tasks:

  1. Work with a fictional WhatsApp chat export.
  2. Identify relevant messages.
  3. Extract suspicious URLs.
  4. Build a communication timeline.
  5. Identify evidence limitations.

Expected output: Communication analysis report.

Laboratory 3: SIM and Device Correlation

Objective: Understand telecommunications identifiers.

Tasks:

  1. Create a sample evidence inventory.
  2. Record fictional SIM identifiers.
  3. Correlate SIM and device references.
  4. Identify attribution limitations.

Expected output: SIM-to-device correlation table.

Laboratory 4: Phishing Investigation

Objective: Examine a suspicious KYC-update form.

Tasks:

  1. Preserve the original URL.
  2. Record the visible form content.
  3. Examine the URL structure.
  4. Identify suspicious branding.
  5. Document potential evidence sources.

Expected output: Phishing analysis report.

Laboratory 5: Financial Transaction Analysis

Objective: Reconstruct suspicious money movements.

Tasks:

  1. Import fictional transaction records.
  2. Identify repeated destination accounts.
  3. Correlate transaction IDs.
  4. Build a transaction timeline.
  5. Calculate total reported losses.

Expected output: Financial transaction analysis.

Laboratory 6: Evidence Integrity

Objective: Verify acquired evidence.

Tasks:

  1. Create a training evidence file.
  2. Calculate its SHA-256 hash.
  3. Copy the file.
  4. Recalculate its hash.
  5. Compare the results.
  6. Document the verification.

Expected output: Evidence integrity verification report.


13. Investigative Challenges and Limitations

Several challenges can affect financial cybercrime investigations.

13.1 Attribution

Identifying a telephone number, account or device is not equivalent to identifying the individual responsible for an action.

13.2 Encrypted communications

End-to-end encryption and device-level security can limit access to communication content.

13.3 Deleted information

Deleted data may be unrecoverable, particularly on modern devices using encryption and storage management.

13.4 Multiple financial intermediaries

Funds can move through several bank accounts, wallets and exchange services.

13.5 Cross-border investigation

Where telecommunications providers, financial institutions or suspects are located in different jurisdictions, lawful cooperation may be necessary.

13.6 Evidence integrity

Improper collection, acquisition or handling can affect the reliability of forensic findings.

13.7 Public-information limitations

News reports rarely provide complete forensic details.

Therefore, conclusions based on public reporting should remain appropriately qualified.


14. Legal and Regulatory Considerations in Nepal

Digital evidence investigations in Nepal must consider applicable laws and authorized investigative procedures.

Important legal references include:

Electronic Transactions Act, 2063

Relevant to electronic records, authentication, retention and electronic transactions.

National Criminal Procedure Code, 2074

Relevant to criminal investigation and procedural requirements.

Evidence Act, 2031

Relevant to evidentiary considerations and the presentation of evidence.

Investigators must follow applicable legal procedures for obtaining devices, financial records, telecommunications information and provider-held data.

The legal admissibility of a particular digital artifact depends on its circumstances, authenticity, integrity and the applicable law.

Official resources:

  • Nepal Law Commission: https://lawcommission.gov.np/
  • Nepal Police Cyber Bureau: https://cyberbureau.nepalpolice.gov.np/
  • Nepal Police: https://www.nepalpolice.gov.np/

This section is an educational overview, not a legal opinion.


15. Findings and Recommendations

Based on the public reporting reviewed, the two incidents demonstrate the importance of examining financial cybercrime through multiple evidence sources.

Key findings

  1. Impersonation of financial-service employees was a reported technique in both incidents.
  2. OTP disclosure and screen-sharing abuse were reported in the Khalti incident.
  3. The Rautahat case involved reported Google Forms use and collection of sensitive financial information.
  4. The Rautahat investigation involved a substantial reported seizure of mobile devices, SIM cards and financial documents.
  5. Financial transaction correlation can provide important investigative leads.
  6. Device ownership and SIM registration alone cannot establish individual attribution.
  7. Public reporting does not provide enough information to reconstruct the complete forensic timeline of either incident.

Recommendations for financial-service users

  • Never disclose OTPs to callers.
  • Never share mobile screens with unverified individuals.
  • Verify customer-support contacts through official channels.
  • Avoid submitting sensitive financial information through unexpected links.
  • Contact the financial institution immediately after suspected account compromise.
  • Preserve suspicious messages, call details and transaction receipts.
  • Report suspected financial cybercrime to the appropriate authorities.

Recommendations for investigators

  • Preserve original digital evidence.
  • Maintain complete chain-of-custody records.
  • Correlate device, SIM and financial records.
  • Obtain service-provider records through lawful channels.
  • Use verified timestamps.
  • Document acquisition methods and limitations.
  • Avoid conclusions based on a single identifier.
  • Clearly distinguish allegations, technical findings and established facts.

16. Conclusion

The Rautahat KYC fraud and Khalti employee impersonation incidents demonstrate how social engineering can exploit trust in digital financial services.

Although the reported incidents involve different organizations and methods, both highlight the importance of communication analysis, mobile-device examination, authentication evidence and financial transaction tracing.

The Rautahat case provides a particularly useful example of investigating physical and digital evidence together, given the reported seizure of mobile phones, SIM cards, banking documents and storage devices.

The Khalti incident demonstrates the importance of examining impersonation, screen-sharing abuse and OTP-related authentication events.

For digital-forensics investigators, the objective is not simply to identify suspicious activity. It is to reconstruct events using reliable evidence, establish the relationships between devices and accounts, and explain the limitations of each finding.

The most important principle remains:

Digital forensics is not about assumptions. It is about evidence, verification, integrity and defensible conclusions.

The development of stronger digital-forensics capabilities will be increasingly important for Nepal as digital financial services continue to expand.


References and Sources

Official sources

  1. Nepal Police – Khalti impersonation arrest announcement, 9 October 2026.
    https://www.nepalpolice.gov.np/ne/news/10695/

  2. Nepal Law Commission – Electronic Transactions Act, 2063.
    https://lawcommission.gov.np/content/13397/

  3. Nepal Police Cyber Bureau.
    https://cyberbureau.nepalpolice.gov.np/

Media reporting

  1. The Himalayan Times – Three arrested in Rautahat over Rs 4.98m KYC scam, October 2026.
    https://thehimalayantimes.com/nepal/three-arrested-in-rautahat-over-rs-498m-kyc-scam

  2. Nagarik News – KYC-update fraud reporting, October 2026.
    https://nagariknews.nagariknetwork.com/social-affairs/three-arrested-for-defrauding-5-million-rupees-under-the-pretext-of-kyc-update-44-71.html

  3. Kantipur – Rautahat KYC fraud case reporting, October 2026.
    https://ekantipur.com/madhesh-pradesh/2026/10/13/en/49-million-fraud-on-the-pretext-of-kyc-update-case-against-three-people-15-14.html

  4. OnlineKhabar – Khalti employee impersonation arrest reporting, October 2026.
    https://english.onlinekhabar.com/4-arrested-for-allegedly-defrauding-people-by-posing-as-khalti-employees.html

  5. Banking News – Khalti impersonation investigation, October 2026.
    https://bankingnews.com.np/2026/10/7679/


Author's Research Disclaimer

This article is an independent educational research publication based on publicly available information. It is not an official Nepal Police forensic report and does not claim access to confidential investigative materials.

The technical workflows and laboratory examples are provided for educational purposes using fictional training scenarios. They must not be interpreted as actual findings from seized devices or financial accounts.

Individuals mentioned in connection with reported arrests are presumed innocent unless proven guilty through the applicable judicial process.

© 2026 Kabin Khadka | Digital Forensics & Cybersecurity Research

Website: https://blog.kabinkhadka.com.np

Comments

Popular posts from this blog

The 2026 DataHub Nepal Infrastructure Breach & Financial Sector Fallback

PhantomSub Campaign:Malicious npm Packages Silently Hijack WhatsApp Accounts

Welcome to My Cybersecurity Research Blog