Back to catalog
Static reviewDevelopment

Skill dossier

performing-initial-access-with-evilginx3

Source declaration

Perform authorized initial access using EvilGinx3 adversary-in-the-middle phishing framework to capture session tokens and bypass multi-factor authentication during red team engagements.

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

Perform authorized initial access using EvilGinx3 adversary-in-the-middle phishing framework to capture session tokens and bypass multi-factor authentication during red team engagements.

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.

Perform authorized initial access using EvilGinx3 adversary-in-the-middle phishing framework to capture session tokens and bypass multi-factor authentication during red team engagements. 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/performing-initial-access-with-evilginx3/SKILL.md:L110]

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/performing-initial-access-with-evilginx3/SKILL.md:L1-L70]

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
37.1 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/performing-initial-access-with-evilginx3/assets/template.mdReference1.2 KB
skills/performing-initial-access-with-evilginx3/LICENSEOther11 KB
skills/performing-initial-access-with-evilginx3/references/api-reference.mdReference1.6 KB
skills/performing-initial-access-with-evilginx3/references/standards.mdReference1.2 KB
skills/performing-initial-access-with-evilginx3/references/workflows.mdReference2.1 KB
skills/performing-initial-access-with-evilginx3/scripts/agent.pyScript6.7 KB
skills/performing-initial-access-with-evilginx3/scripts/process.pyScript5.8 KB
skills/performing-initial-access-with-evilginx3/SKILL.mdInstruction7.6 KB

SKILL.md frontmatter

{
  "name": "performing-initial-access-with-evilginx3",
  "description": "Perform authorized initial access using EvilGinx3 adversary-in-the-middle phishing framework to capture session tokens and bypass multi-factor authentication during red team engagements.",
  "domain": "cybersecurity",
  "subdomain": "red-teaming",
  "tags": [
    "red-team",
    "initial-access",
    "phishing",
    "evilginx",
    "mfa-bypass",
    "adversary-in-the-middle",
    "credential-theft"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "d3fend_techniques": [
    "File Metadata Consistency Validation",
    "Application Protocol Command Analysis",
    "Identifier Analysis",
    "Content Format Conversion",
    "Message Analysis"
  ],
  "nist_csf": [
    "ID.RA-01",
    "GV.OV-02",
    "DE.AE-07"
  ],
  "mitre_attack": [
    "T1595",
    "T1190",
    "T1059",
    "T1078",
    "T1003"
  ],
  "mitre_f3": {
    "version": "1.1",
    "tactics": [
      "resource-development",
      "initial-access",
      "positioning"
    ],
    "techniques": [
      {
        "id": "T1583.001",
        "name": "Acquire Infrastructure: Domains",
        "tactic": "resource-development",
        "source": "attack"
      },
      {
        "id": "T1660",
        "name": "Phishing",
        "tactic": "initial-access",
        "source": "attack"
      },
      {
        "id": "T1557",
        "name": "Adversary-in-the-Middle",
        "tactic": "initial-access",
        "source": "attack"
      },
      {
        "id": "T1539",
        "name": "Steal Web Session Cookie",
        "tactic": "positioning",
        "source": "attack"
      },
      {
        "id": "T1111",
        "name": "Multi-Factor Authentication Interception",
        "tactic": "initial-access",
        "source": "attack"
      },
      {
        "id": "F1004",
        "name": "Access with Stolen Session Cookie",
        "tactic": "initial-access",
        "source": "f3"
      },
      {
        "id": "F1006",
        "name": "Account Takeover",
        "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

    Objectives

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

  4. 04
    Action

    MITRE ATT&CK Mapping

    Source-described action candidate under “MITRE ATT&CK Mapping”; not verified execution.

  5. 05
    Action

    Workflow

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

  6. 06
    Action

    Register a convincing lookalike domain (e.g., using homoglyphs or typosquatting)

    Source-described action candidate under “Phase 1: Infrastructure Setup”; not verified execution.

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

    Provision a VPS and point the domain's DNS A record to the server IP

    Source-described action candidate under “Phase 1: Infrastructure Setup”; not verified execution.

  2. 08
    Action

    Install EvilGinx3:

    Source-described action candidate under “Phase 1: Infrastructure Setup”; not verified execution.

  3. 09
    Action

    Configure the domain and IP in EvilGinx3:

    Source-described action candidate under “Phase 1: Infrastructure Setup”; not verified execution.

  4. 10
    Action

    EvilGinx3 automatically provisions Let's Encrypt certificates for configured hostnames

    Source-described action candidate under “Phase 1: Infrastructure Setup”; not verified execution.

  5. 11
    Action

    Select or create a phishlet for the target service (e.g., Microsoft 365, Google Workspace):

    Source-described action candidate under “Phase 2: Phishlet Configuration”; not verified execution.

  6. 12
    Action

    Verify phishlet is active and SSL certificate is issued:

    Source-described action candidate under “Phase 2: Phishlet Configuration”; not verified execution.

  7. 13
    Action

    Create a lure URL for the phishing campaign:

    Source-described action candidate under “Phase 2: Phishlet Configuration”; not verified execution.

  8. 14
    Action

    Optionally configure a redirect URL for post-capture:

    Source-described action candidate under “Phase 2: Phishlet Configuration”; not verified execution.

  9. 15
    Action

    Craft a pretext email with the lure URL embedded

    Source-described action candidate under “Phase 3: Phishing Delivery”; not verified execution.

  10. 16
    Action

    Use GoPhish or manual SMTP for email delivery:

    Source-described action candidate under “Phase 3: Phishing Delivery”; not verified execution.

  11. 17
    Decision

    Implement URL masking or shortening if needed for link obfuscation

    Source-described decision candidate under “Phase 3: Phishing Delivery”; not verified execution.

  12. 18
    Action

    Deploy landing page with appropriate social engineering pretext

    Source-described action candidate under “Phase 3: Phishing Delivery”; not verified execution.

  13. 19
    Action

    Monitor EvilGinx3 for captured sessions:

    Source-described action candidate under “Phase 4: Session Hijacking”; not verified execution.

  14. 20
    Action

    Extract captured session cookies from the session:

    Source-described action candidate under “Phase 4: Session Hijacking”; not verified execution.

  15. 21
    Input

    Import session cookies into a browser using a cookie editor extension:

    Source-described input candidate under “Phase 4: Session Hijacking”; not verified execution.

  16. 22
    Action

    Establish persistent access by creating application passwords or OAuth tokens

    Source-described action candidate under “Phase 4: Session Hijacking”; not verified execution.

  17. 23
    Action

    Enumerate mailbox contents, contacts, and shared drives

    Source-described action candidate under “Phase 5: Post-Access Activities”; not verified execution.

  18. 24
    Action

    Identify additional targets for lateral phishing

    Source-described action candidate under “Phase 5: Post-Access Activities”; not verified execution.

  19. 25
    Action

    Check for access to connected cloud applications (SharePoint, Teams, OneDrive)

    Source-described action candidate under “Phase 5: Post-Access Activities”; not verified execution.

  20. 26
    Action

    Document all captured credentials and access achieved

    Source-described action candidate under “Phase 5: Post-Access Activities”; not verified execution.

  21. 27
    Action

    Tools and Resources

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

  22. 28
    Action

    Phishlet Targets

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

  23. 29
    Action

    Detection Indicators

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

  24. 30
    Action

    Validation Criteria

    Source-described action candidate under “Validation Criteria”; 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

22 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 useNot observed
Medium

Network access is mentioned

9 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 9 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

12 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 12 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

Elevated privileges are referenced

Privilege-elevation syntax is present. Confirm whether elevation is necessary and inspect every operation performed under it; static analysis cannot prove that elevation succeeded. 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/performing-initial-access-with-evilginx3/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/performing-initial-access-with-evilginx3/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/performing-initial-access-with-evilginx3
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.