Back to catalog
Static reviewDevelopment

Skill dossier

detecting-qr-code-phishing-with-email-security

Source declaration

Detect and prevent QR code phishing (quishing) attacks that embed malicious URLs inside QR code images to bypass link-based email security, using image-based threat detection, OCR/QR decoding, and mobile-side scanning (Microsoft Defender for O365, Proofpoint TAP, Barracuda Multimodal AI). Use when configuring gateway rules against QR phishing or investigating suspicious emails containing QR codes.

The author's original description, preserved in English. It describes intent, not verified performance.

Detect and prevent QR code phishing (quishing) attacks that embed malicious URLs inside QR code images to bypass link-based email security, using image-based threat detection, OCR/QR decoding, and mobile-side scanning (Microsoft Defender for O365, Proofpoint TAP, Barracuda Multimodal AI). Use when configuring gateway rules against QR phishing or investigating suspicious emails containing QR codes.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Detect and prevent QR code phishing (quishing) attacks that embed malicious URLs inside QR code images to bypass link-based email security, using image-based threat detection, OCR/QR decoding, and mobile-side scanning (Microsoft Defender for O365, Proofpoint TAP, Barracuda Multimodal AI). Use when configuring gateway rules against QR phishing or investigating suspicious emails containing QR codes. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/detecting-qr-code-phishing-with-email-security/SKILL.md:L108]
  • Step 1: Enable Image-Based Threat Detection [Source statement; provisional, not tested. Evidence: skills/detecting-qr-code-phishing-with-email-security/SKILL.md:L110]
  • Step 2: Configure QR Code URL Analysis [Source statement; provisional, not tested. Evidence: skills/detecting-qr-code-phishing-with-email-security/SKILL.md:L117]
  • Step 3: Deploy Mobile-Side Protection [Source statement; provisional, not tested. Evidence: skills/detecting-qr-code-phishing-with-email-security/SKILL.md:L124]
  • Step 4: Build Detection Rules [Source statement; provisional, not tested. Evidence: skills/detecting-qr-code-phishing-with-email-security/SKILL.md:L131]
  • Step 5: Train Users on Quishing Recognition [Source statement; provisional, not tested. Evidence: skills/detecting-qr-code-phishing-with-email-security/SKILL.md:L138]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/detecting-qr-code-phishing-with-email-security/SKILL.md:L1-L67]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
8
Markdown files
5
scripts
2
references
4
Size
43 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/detecting-qr-code-phishing-with-email-security/assets/template.mdReference1.5 KB
skills/detecting-qr-code-phishing-with-email-security/LICENSEOther11 KB
skills/detecting-qr-code-phishing-with-email-security/references/api-reference.mdReference2.4 KB
skills/detecting-qr-code-phishing-with-email-security/references/standards.mdReference1.6 KB
skills/detecting-qr-code-phishing-with-email-security/references/workflows.mdReference2.5 KB
skills/detecting-qr-code-phishing-with-email-security/scripts/agent.pyScript5.9 KB
skills/detecting-qr-code-phishing-with-email-security/scripts/process.pyScript11.5 KB
skills/detecting-qr-code-phishing-with-email-security/SKILL.mdInstruction6.6 KB

SKILL.md frontmatter

{
  "name": "detecting-qr-code-phishing-with-email-security",
  "description": "Detect and prevent QR code phishing (quishing) attacks that embed malicious URLs inside QR code images to bypass link-based email security, using image-based threat detection, OCR/QR decoding, and mobile-side scanning (Microsoft Defender for O365, Proofpoint TAP, Barracuda Multimodal AI). Use when configuring gateway rules against QR phishing or investigating suspicious emails containing QR codes.",
  "domain": "cybersecurity",
  "subdomain": "phishing-defense",
  "tags": [
    "quishing",
    "qr-code",
    "phishing",
    "email-security",
    "image-analysis",
    "ocr",
    "mobile-security"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "atlas_techniques": [
    "AML.T0052",
    "AML.T0024",
    "AML.T0035"
  ],
  "nist_ai_rmf": [
    "MEASURE-2.8",
    "MAP-5.1"
  ],
  "nist_csf": [
    "PR.AT-01",
    "DE.CM-09",
    "RS.CO-02",
    "DE.AE-02"
  ],
  "mitre_attack": [
    "T1566",
    "T1598",
    "T1534",
    "T1036",
    "T1027"
  ],
  "mitre_f3": {
    "version": "1.1",
    "tactics": [
      "reconnaissance",
      "resource-development",
      "initial-access"
    ],
    "techniques": [
      {
        "id": "T1598",
        "name": "Phishing for Information",
        "tactic": "reconnaissance",
        "source": "attack"
      },
      {
        "id": "T1660",
        "name": "Phishing",
        "tactic": "initial-access",
        "source": "attack"
      },
      {
        "id": "F1020.002",
        "name": "Create Fake Materials: Fake Website",
        "tactic": "resource-development",
        "source": "f3"
      },
      {
        "id": "T1583.001",
        "name": "Acquire Infrastructure: Domains",
        "tactic": "resource-development",
        "source": "attack"
      },
      {
        "id": "F1006.002",
        "name": "Account Takeover: Exposed Login Credential",
        "tactic": "initial-access",
        "source": "f3"
      }
    ]
  }
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Action

    Overview

    Source-described action candidate under “Overview”; not verified execution.

  2. 02
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  3. 03
    Action

    Key Concepts

    Source-described action candidate under “Key Concepts”; not verified execution.

  4. 04
    Action

    Bypasses URL Scanners: Traditional gateways scan text-based URLs but cannot decode image-embedded URLs

    Source-described action candidate under “Why Quishing Works”; not verified execution.

  5. 05
    Action

    Shifts to Unprotected Devices: Corporate email arrives on secured systems but QR scan occurs on personal mobile devices

    Source-described action candidate under “Why Quishing Works”; not verified execution.

  6. 06
    Action

    User Trust: QR codes are normalized in daily life (payments, menus, parking)

    Source-described action candidate under “Why Quishing Works”; not verified execution.

Inspect all extracted workflow candidates (40 candidate steps)
  1. 07
    Action

    Low Detection Rate: Only 36% of quishing incidents are accurately identified by recipients

    Source-described action candidate under “Why Quishing Works”; not verified execution.

  2. 08
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  3. 09
    Action

    Step 1: Enable Image-Based Threat Detection

    Source-described action candidate under “Step 1: Enable Image-Based Threat Detection”; not verified execution.

  4. 10
    Action

    Configure email gateway to scan embedded images for QR codes

    Source-described action candidate under “Step 1: Enable Image-Based Threat Detection”; not verified execution.

  5. 11
    Action

    Enable OCR processing on image attachments (PNG, JPG, GIF, BMP)

    Source-described action candidate under “Step 1: Enable Image-Based Threat Detection”; not verified execution.

  6. 12
    Action

    Deploy multimodal AI that combines image processing, OCR, and NLP analysis

    Source-described action candidate under “Step 1: Enable Image-Based Threat Detection”; not verified execution.

  7. 13
    Action

    Configure PDF scanning to detect QR codes within attachments

    Source-described action candidate under “Step 1: Enable Image-Based Threat Detection”; not verified execution.

  8. 14
    Action

    Set up detection for ASCII/text-based QR code rendering

    Source-described action candidate under “Step 1: Enable Image-Based Threat Detection”; not verified execution.

  9. 15
    Action

    Step 2: Configure QR Code URL Analysis

    Source-described action candidate under “Step 2: Configure QR Code URL Analysis”; not verified execution.

  10. 16
    Action

    Extract URLs from detected QR codes and submit to URL reputation services

    Source-described action candidate under “Step 2: Configure QR Code URL Analysis”; not verified execution.

  11. 17
    Action

    Apply same URL scanning policies to QR-extracted URLs as text-based URLs

    Source-described action candidate under “Step 2: Configure QR Code URL Analysis”; not verified execution.

  12. 18
    Action

    Enable real-time sandbox analysis for QR-decoded destination pages

    Source-described action candidate under “Step 2: Configure QR Code URL Analysis”; not verified execution.

  13. 19
    Action

    Configure time-of-click protection for QR-extracted URLs where possible

    Source-described action candidate under “Step 2: Configure QR Code URL Analysis”; not verified execution.

  14. 20
    Action

    Block known phishing domains extracted from QR codes

    Source-described action candidate under “Step 2: Configure QR Code URL Analysis”; not verified execution.

  15. 21
    Action

    Step 3: Deploy Mobile-Side Protection

    Source-described action candidate under “Step 3: Deploy Mobile-Side Protection”; not verified execution.

  16. 22
    Action

    Implement mobile threat defense (MTD) with QR code scanning capability

    Source-described action candidate under “Step 3: Deploy Mobile-Side Protection”; not verified execution.

  17. 23
    Action

    Deploy Palo Alto ALFA or equivalent safe-by-design QR scanning

    Source-described action candidate under “Step 3: Deploy Mobile-Side Protection”; not verified execution.

  18. 24
    Action

    Configure MDM policies to warn users before opening scanned URLs

    Source-described action candidate under “Step 3: Deploy Mobile-Side Protection”; not verified execution.

  19. 25
    Action

    Enable corporate VPN/secure browser for QR-scanned destinations

    Source-described action candidate under “Step 3: Deploy Mobile-Side Protection”; not verified execution.

  20. 26
    Action

    Block known credential harvesting domains at the mobile proxy level

    Source-described action candidate under “Step 3: Deploy Mobile-Side Protection”; not verified execution.

  21. 27
    Action

    Step 4: Build Detection Rules

    Source-described action candidate under “Step 4: Build Detection Rules”; not verified execution.

  22. 28
    Action

    Alert on emails containing only an image and minimal text (common quishing pattern)

    Source-described action candidate under “Step 4: Build Detection Rules”; not verified execution.

  23. 29
    Action

    Flag emails with QR code images from external first-time senders

    Source-described action candidate under “Step 4: Build Detection Rules”; not verified execution.

  24. 30
    Action

    Detect urgency language combined with QR code presence

    Source-described action candidate under “Step 4: Build Detection Rules”; not verified execution.

  25. 31
    Action

    Alert on emails impersonating IT/security team requesting QR scan for MFA setup

    Source-described action candidate under “Step 4: Build Detection Rules”; not verified execution.

  26. 32
    Action

    Monitor for common quishing themes: MFA reset, document signing, voicemail notification

    Source-described action candidate under “Step 4: Build Detection Rules”; not verified execution.

  27. 33
    Action

    Step 5: Train Users on Quishing Recognition

    Source-described action candidate under “Step 5: Train Users on Quishing Recognition”; not verified execution.

  28. 34
    Action

    Update security awareness program to include QR code phishing scenarios

    Source-described action candidate under “Step 5: Train Users on Quishing Recognition”; not verified execution.

  29. 35
    Action

    Conduct quishing simulation campaigns using controlled QR codes

    Source-described action candidate under “Step 5: Train Users on Quishing Recognition”; not verified execution.

  30. 36
    Action

    Teach users to verify QR destination URLs before entering credentials

    Source-described action candidate under “Step 5: Train Users on Quishing Recognition”; not verified execution.

  31. 37
    Action

    Establish reporting process for suspicious QR code emails

    Source-described action candidate under “Step 5: Train Users on Quishing Recognition”; not verified execution.

  32. 38
    Action

    Distribute guidance on safe QR scanning practices

    Source-described action candidate under “Step 5: Train Users on Quishing Recognition”; not verified execution.

  33. 39
    Action

    Tools & Resources

    Source-described action candidate under “Tools & Resources”; not verified execution.

  34. 40
    Action

    Validation

    Source-described action candidate under “Validation”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

36 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useObserved
Medium

Network access is mentioned

13 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 13 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

22 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 22 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Credential or secret material is referenced

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 1 location(s) in the collected text; 1 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/detecting-qr-code-phishing-with-email-security/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 8 collected file(s), 5 Markdown file(s), and 2 script file(s), enabling source-level inspection. [Evidence: skills/detecting-qr-code-phishing-with-email-security/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/detecting-qr-code-phishing-with-email-security
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.