Quishing Attacks on the Rise: How QR Code Phishing Targets Indian Enterprises

  • Home
  • Quishing Attacks on the Rise: How QR Code Phishing Targets Indian Enterprises
Quishing Attacks on the Rise: How QR Code Phishing Targets Indian Enterprises

Cybercriminals are continuously evolving their tactics, and one of the most alarming trends to emerge in the last 18 months is quishing — phishing delivered through QR codes. What began as scattered attacks against consumer banking customers has matured into a calculated threat against enterprise environments, and Indian organisations are firmly in the crosshairs.

For IT leaders and CISOs overseeing large, distributed workforces, quishing is particularly dangerous because it bypasses almost every conventional email security layer. No malicious URL in plain text means no URL reputation check fires. No weaponised attachment means no sandbox detonation. The attack vector is a harmless-looking image embedded in a PDF, an email, a printed poster, or even a WhatsApp message — and a single employee scan is all it takes.

What Is Quishing and Why Is It Accelerating?

A quishing attack begins with a QR code that encodes a malicious URL — usually a convincing credential-harvest page, a fake SSO portal, or a malware dropper. The attacker embeds this code in:

  • Emails impersonating HR portals, Microsoft 365 re-authentication notices, or payroll systems
  • PDF attachments that pass clean through email gateways (the PDF is benign; the QR code is not)
  • Physical media — printed memos, desk-drop flyers, conference lanyards — placed inside company premises
  • Messaging apps outside corporate visibility: WhatsApp, Telegram, SMS

The acceleration is driven by two factors. First, mobile devices used to scan QR codes are frequently not managed by enterprise MDM — employees use personal handsets to scan codes in offices every day. Second, the explosion of QR codes during and after the COVID-19 pandemic has conditioned people to scan first and question later.

The Indian Enterprise Threat Landscape

India presents a uniquely attractive target for quishing campaigns for several reasons:

UPI and Payment App Familiarity

Indians scan QR codes for payments dozens of times a week. This muscle memory carries over to work environments, reducing natural scepticism. Attackers have weaponised fake UPI collection QR codes that redirect to enterprise credential pages — a particularly effective hybrid social-engineering vector.

Large, Distributed Workforces

Manufacturing groups, BFSI conglomerates, and IT services companies often have tens of thousands of employees spread across hundreds of locations. Security awareness training reaches head-office staff reliably; it frequently does not reach factory floors, regional branches, or field personnel at the same fidelity.

Multi-Vendor BYOD Environments

Many Indian enterprises still operate partially or fully BYOD (Bring Your Own Device) models for mobile. This means the device that scans the quishing QR code may have no corporate security agents, no VPN enforcement, and no filtering between the camera app and a malicious URL.

Microsoft 365 and Cloud App Proliferation

The rapid migration to Microsoft 365, Google Workspace, and cloud-hosted ERPs has made credential phishing extremely valuable. A single set of Microsoft 365 credentials can unlock email, SharePoint, Teams, Azure resources, and connected third-party SaaS platforms. Quishing campaigns increasingly target M365 re-authentication prompts specifically.

Technical Anatomy of a Quishing Campaign

Understanding the attack chain helps defenders identify the right intervention points:

  1. QR code generation: Attackers generate a QR code pointing to a domain with a short lifespan — often registered within days of the campaign — or to an abused legitimate service (Google Sites, Adobe Experience Cloud, Cloudflare Workers) to avoid domain-reputation blacklisting.
  2. Lure construction: A PDF or HTML email template is crafted. The email body may be entirely image-based, further evading text-based content filtering. Common lures: “Your MFA session has expired — scan to re-authenticate”, “New HR policy — scan for details”, “IT security mandatory training”.
  3. Delivery: Sent via compromised business email accounts (bypassing SPF/DKIM/DMARC), bulk mailers, or messaging apps. The PDF attachment scores clean on VirusTotal; no URL extraction means no threat feeds fire.
  4. Victim scan: Employee scans from personal phone. The phone’s OS-level QR scanner opens the URL directly in a browser with no corporate proxy or DNS filtering.
  5. Credential harvest: A convincing fake login page (Microsoft, SAP, Salesforce) captures credentials. Advanced campaigns deploy adversary-in-the-middle (AiTM) proxies — tools like Evilginx — that relay real session cookies, defeating MFA.
  6. Post-exploitation: Stolen credentials or session tokens used for email account takeover, business email compromise (BEC) follow-on fraud, or lateral movement into cloud tenants.

Detection Challenges for Security Operations Teams

Quishing is specifically designed to be hard to detect at the network and email layers. The traditional SOC playbook — inspect attachments, detonate URLs, check sender reputation — does not fire cleanly on a QR code embedded in a PDF. However, detection is not impossible. The right signals exist at different layers:

Email Gateway Signals

  • Image-only email body (no text) is a high-confidence anomaly signal when combined with an attachment
  • PDF attachments with no readable text content after extraction
  • Sender domains registered recently (WHOIS age < 30 days) or sender-receiver relationship never seen before
  • QR code images extracted from PDFs and decoded — this requires an email security platform with QR decode capability or a custom detection rule in your SIEM

Endpoint and Mobile Signals

  • A corporate-managed device visiting a domain not in the corporate DNS resolver cache (proxy logs)
  • Browser navigating to a site classified as newly registered and passing credentials (CASB/DLP integration)
  • Authentication events from unusual geographies or ASNs immediately after no prior login from that ASN

Identity and Access Signals

  • Impossible-travel alerts: credential used in Mumbai at 10:00 and Netherlands at 10:04
  • Token-only sessions (no password authentication logged) from new device fingerprints
  • Privilege escalation or new OAuth app consent events shortly after credential use from an unknown device

The challenge is correlating these signals across email gateways, endpoint agents, identity providers, and network logs — in near real time, at enterprise scale. This is exactly the problem a converged SOC with modern tooling is built to solve.

Defending Against Quishing: A Practical Checklist for Indian Enterprises

Immediate actions (0–30 days):

  • Configure email security to extract and decode QR codes from attachments. FortiMail’s Advanced Threat Protection can be configured to extract images from PDFs and run them through additional inspection; enable QR code URL extraction if your gateway supports it.
  • Enforce Phishing-Resistant MFA (FIDO2/Passkeys) for all cloud applications — not TOTP codes, which AiTM attacks defeat. Microsoft Authenticator’s number matching and additional context options are a good interim step while hardware tokens are rolled out.
  • Block unknown-device logins at the identity layer. Conditional Access (Azure AD) or equivalent: require device compliance checks before granting tokens. An unmanaged personal phone scanning a QR code should not be able to authenticate to your M365 tenant.
  • Run a targeted quishing simulation. Send a benign QR code lure to your user population and measure click-through (scan-through) rates. The results will almost certainly surprise you.

Medium-term actions (30–90 days):

  • Deploy mobile threat defence (MTD) on any device — BYOD or corporate — that can access corporate resources. MTD agents check URLs at the point of scan.
  • Extend DNS filtering to mobile devices via MDM-enforced DNS-over-HTTPS to corporate resolver so newly registered domains are blocked even on personal phones when accessing corporate resources.
  • Create a SIEM detection rule for PDF attachments with high image-to-text ratio from senders with no prior relationship to the recipient. Alert and route for analyst review.
  • Review OAuth app consent policies in M365 and Google Workspace. Disable user-level consent for new apps; require admin approval. This contains the blast radius of any credential compromise.
  • Establish a CERT-In-compliant incident reporting workflow. If a quishing attack results in a data breach, you have six hours to file an initial report with CERT-In and must preserve logs for 180 days. Without an automated process, this timeline is extremely difficult to meet.

PrahiX Ora: Unified SecOps Visibility for the Quishing Threat Surface

One of the core frustrations in detecting and responding to quishing attacks is that the evidence is spread across disconnected systems — email logs, identity provider event streams, endpoint telemetry, network proxy records, and cloud access logs. Each tool sees a slice; no single analyst sees the whole picture without a platform that aggregates and correlates across all of them.

PrahiX Ora is a unified SecOps platform built by PrahiX Tech Pvt Ltd. PJ Networks is its primary field deployment and operations partner, and we deploy and operate this platform for clients across manufacturing, BFSI, retail, and services sectors in India.

SIEM — Correlation Across the Quishing Kill Chain: Ora’s SIEM ingests logs from FortiGate firewalls, FortiMail, Microsoft 365 audit logs, identity providers, endpoint agents, and cloud access proxies into a unified event lake. Correlation rules mapped to MITRE ATT&CK — specifically Initial Access (T1566), Credential Access (T1056), and Valid Accounts (T1078) — can fire on the multi-source signal combinations that indicate a quishing-derived account takeover: an unusual PDF attachment from a new sender, followed by an authentication event from an unrecognised device, followed by a new OAuth consent event. Graph-based attack storyline reconstruction links these events into a readable timeline for the analyst. Crucially, Ora supports tiered log retention — hot, cold, and archive — with in-country data residency, helping enterprises evidence compliance with CERT-In’s 180-day log retention direction without shipping logs offshore.

NMS — Catching the Post-Compromise Lateral Movement: Once an attacker holds a valid session token from a quishing attack, they begin lateral movement. Ora’s NMS provides unified observability across your FortiGate firewalls, switches, access points, and SD-WAN links, with LLDP/CDP topology discovery and network path tracing. In multi-vendor estates — common in Indian enterprises that have grown through acquisition — NOC visibility is frequently fragmented across vendor-specific dashboards. Ora’s ML-based anomaly detection fires on unusual east-west traffic patterns (a credential-compromised server suddenly scanning internal subnets) and can trigger auto-healing policies such as isolating the affected segment.

Video Surveillance (VMS) — Closing the Physical Vector: Quishing attacks via physically planted QR codes — on printed memos, desk-drops, or posters — require physical security correlation. Ora’s video surveillance (VMS) module, compatible with ONVIF, Hikvision, and Dahua cameras, brings video analytics into the same operational view as network and security events. For manufacturing, retail, and multi-site enterprises, this means a suspicious individual placing materials in a secure area can be correlated with a spike in QR-code-related network events from that location — an investigative thread that is simply invisible when physical and digital operations are siloed.

SOAR — Meeting the CERT-In 6-Hour Reporting Window: CERT-In’s 6-hour initial incident reporting requirement is one of the most operationally demanding compliance obligations Indian enterprises face. When a quishing-derived account takeover is confirmed, the clock starts immediately. Ora’s SOAR capability provides pre-built playbook automation with connectors to FortiGate (pushing blocklists, isolating affected IPs), to Microsoft 365 (revoking active sessions, disabling the compromised account), and to the CERT-In reporting interface. Automated evidence collection — pulling the relevant email headers, authentication logs, and network events — is what makes the six-hour window realistic. Without automation, coordinating that evidence collection manually while simultaneously containing the incident is an enormous operational burden on SOC teams.

If you are evaluating how a converged SecOps platform could improve your visibility across the quishing threat surface, our team can walk you through how we have deployed and operationalised PrahiX Ora for organisations with similar environments.

The DPDP Act Dimension

India’s Digital Personal Data Protection Act (DPDP Act, 2023) introduces significant obligations for data fiduciaries in the event of a personal data breach. A quishing attack that results in the compromise of an employee’s credentials — which may in turn expose customer records, HR data, or financial information — is squarely within the definition of a reportable incident.

Key obligations relevant to quishing incident response:

  • Notification to the Data Protection Board of India (DPBI) in the prescribed form and timeframe once a breach is established
  • Notification to affected data principals (individuals whose data was breached) in prescribed form
  • Reasonable security safeguards — the Act requires data fiduciaries to implement “reasonable security safeguards to prevent personal data breach”, which regulators will assess against what an organisation of that size and data sensitivity could reasonably have done

Deploying quishing-specific defences — MFA hardening, QR-aware email security, identity protection policies — is now not just good security practice but part of the evidence base for “reasonable security safeguards” under the DPDP Act.

What to Do This Week

If your organisation has not assessed its exposure to quishing attacks, here are five actions to initiate this week:

  1. Ask your email security vendor whether QR code URL extraction and inspection is enabled on your gateway.
  2. Review Conditional Access policies in your identity provider: can an unmanaged personal device authenticate to your cloud tenants?
  3. Check your SIEM alert coverage: do you have rules that correlate PDF-heavy email anomalies with subsequent unusual authentication events?
  4. Schedule a quishing simulation as part of your next security awareness cycle — at minimum for your finance, HR, and IT administration teams.
  5. Map your CERT-In 6-hour reporting process: who owns the initial report, what data must it include, and can you assemble that data within six hours of detection?

Closing

Quishing is not a niche curiosity. It is an actively exploited, rapidly scaling attack vector that exploits the intersection of human behaviour (QR scanning habits), security blind spots (image-based payloads bypassing email gateways), and the proliferation of unmanaged mobile devices in enterprise environments. Indian organisations face an elevated risk profile because of UPI payment familiarity, BYOD norms, and large distributed workforces.

The good news is that quishing attacks are detectable and preventable with the right combination of controls: phishing-resistant MFA, QR-aware email security, identity-layer device compliance enforcement, mobile threat defence, and a SOC with the telemetry to correlate signals across the full kill chain.

PJ Networks helps Indian enterprises design, deploy, and operate these controls — from FortiGate and FortiMail configuration hardening to 24/7 SOC operations and CERT-In compliance readiness. Reach out to our team to discuss how we can help you assess and close your quishing exposure before your next phishing simulation — or your next real incident.

Leave a Reply

Your email address will not be published. Required fields are marked *