AGENT SKILL

performing-initial-access-with-evilginx3

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.

License 许可
Apache-2.0
最近更新
2026-09-11
Stars
★ 0
Forks
0

01 前言 Front Matter

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

02 资源文件 7

03 SKILL.md 正文

Performing Initial Access with EvilGinx3

Overview

EvilGinx3 is a man-in-the-middle attack framework used for phishing login credentials along with session cookies, enabling bypass of multi-factor authentication (MFA). Unlike traditional credential phishing that only captures usernames and passwords, EvilGinx3 operates as a transparent reverse proxy between the victim and the legitimate authentication service, intercepting the full authentication flow including MFA tokens and session cookies. This makes it the primary tool for red teams demonstrating the risk of adversary-in-the-middle (AiTM) attacks against organizations relying solely on MFA for protection.

When to Use

  • When conducting security assessments that involve performing initial access with evilginx3
  • When following incident response procedures for related security events
  • When performing scheduled security testing or auditing activities
  • When validating security controls through hands-on testing

Prerequisites

  • Familiarity with red teaming concepts and tools
  • Access to a test or lab environment for safe execution
  • Python 3.8+ with required dependencies installed
  • Appropriate authorization for any testing activities

Objectives

  • Deploy EvilGinx3 with custom phishlets targeting authorized scope
  • Configure DNS and SSL certificates for the phishing domain
  • Capture session tokens that bypass MFA protections
  • Import stolen session cookies into a browser to hijack authenticated sessions
  • Integrate with GoPhish or custom delivery mechanisms for phishing email campaigns
  • Document the complete attack chain from phishing email to authenticated access

MITRE ATT&CK Mapping

  • T1566.002 - Phishing: Spearphishing Link
  • T1557 - Adversary-in-the-Middle
  • T1539 - Steal Web Session Cookie
  • T1078 - Valid Accounts
  • T1556 - Modify Authentication Process
  • T1550.004 - Use Alternate Authentication Material: Web Session Cookie

Workflow

Phase 1: Infrastructure Setup

  1. Register a convincing lookalike domain (e.g., using homoglyphs or typosquatting)
  2. Provision a VPS and point the domain's DNS A record to the server IP
  3. Install EvilGinx3:
    git clone https://github.com/kgretzky/evilginx2.git
    cd evilginx2
    make
    sudo ./bin/evilginx -p ./phishlets
    
  4. Configure the domain and IP in EvilGinx3:
    config domain example-phish.com
    config ipv4 <server-ip>
    
  5. EvilGinx3 automatically provisions Let's Encrypt certificates for configured hostnames

Phase 2: Phishlet Configuration

  1. Select or create a phishlet for the target service (e.g., Microsoft 365, Google Workspace):
    phishlets hostname o365 login.example-phish.com
    phishlets enable o365
    
  2. Verify phishlet is active and SSL certificate is issued:
    phishlets
    
  3. Create a lure URL for the phishing campaign:
    lures create o365
    lures get-url 0
    
  4. Optionally configure a redirect URL for post-capture:
    lures edit 0 redirect_url https://legitimate-site.com
    

Phase 3: Phishing Delivery

  1. Craft a pretext email with the lure URL embedded
  2. Use GoPhish or manual SMTP for email delivery:
    # Integration with EvilGoPhish for combined campaigns
    # Provides GoPhish email tracking + EvilGinx3 credential capture
    
  3. Implement URL masking or shortening if needed for link obfuscation
  4. Deploy landing page with appropriate social engineering pretext

Phase 4: Session Hijacking

  1. Monitor EvilGinx3 for captured sessions:
    sessions
    sessions <session-id>
    
  2. Extract captured session cookies from the session:
    # Session output includes:
    # - Username and password
    # - Session cookies (authentication tokens)
    # - Custom captured parameters
    
  3. Import session cookies into a browser using a cookie editor extension:
    • Export cookies in JSON format
    • Use Cookie-Editor or EditThisCookie browser extension
    • Navigate to the target service to validate session hijack
  4. Establish persistent access by creating application passwords or OAuth tokens

Phase 5: Post-Access Activities

  1. Enumerate mailbox contents, contacts, and shared drives
  2. Identify additional targets for lateral phishing
  3. Check for access to connected cloud applications (SharePoint, Teams, OneDrive)
  4. Document all captured credentials and access achieved

Tools and Resources

Tool Purpose Platform
EvilGinx3 AiTM phishing framework Linux
GoPhish Phishing campaign management Cross-platform
EvilGoPhish Combined EvilGinx3 + GoPhish integration Linux
Cookie-Editor Browser cookie import/export Browser Extension
Modlishka Alternative AiTM proxy framework Linux
Muraena Alternative AiTM phishing proxy Linux

Phishlet Targets

Target Service Phishlet Captured Data
Microsoft 365 o365 Session cookies, credentials
Google Workspace google Session cookies, credentials
Okta okta Session tokens, credentials
GitHub github Session cookies, credentials
AWS Console aws Session tokens, credentials

Detection Indicators

Indicator Detection Method
Newly registered lookalike domains Domain monitoring and certificate transparency logs
SSL certificates for suspicious domains CT log monitoring (crt.sh, Censys)
Unusual login locations after phishing SIEM correlation of authentication events
Session cookie replay from different IP Conditional access policy alerts
AiTM proxy headers in traffic Network inspection for proxy artifacts

Validation Criteria

  • [ ] EvilGinx3 deployed with valid SSL certificates
  • [ ] Phishlet configured and enabled for target service
  • [ ] Lure URL generated and accessible
  • [ ] Test credentials captured successfully through phishing flow
  • [ ] Session cookies captured and validated for MFA bypass
  • [ ] Session hijack demonstrated in browser with stolen cookies
  • [ ] Post-authentication access to target service confirmed
  • [ ] Evidence documented with screenshots and session logs

04 同仓库更多 Skills

NeelakshSaxena
NeelakshSaxena/Vayu

runpodctl

Runpod CLI for managing GPU/CPU workloads from the terminal — pods, serverless endpoints, templates, network volumes, Hub deploys, models, SSH, and file transfer (send/receive). Use for terminal/CI/scripting, Hub browse/deploy, SSH setup, `doctor`, or when the Runpod MCP tools are not connected. For structured tool calls in an MCP-enabled session, prefer runpod-mcp.

★ 0
NeelakshSaxena
NeelakshSaxena/Vayu

runpod

Start here for any Runpod task — running GPU/CPU pods, deploying serverless endpoints, templates, network volumes, building images, or understanding how Runpod works. Routes to the right skill (runpod-mcp, runpodctl, flash, companion-clis, runpod-usage, runpod-templates, runpod-migrate) and indexes two dozen live-verified end-to-end examples (golden paths) — use it when the lane is unclear, and for any multi-step or provisioning task even when it is not.

★ 0
NeelakshSaxena
NeelakshSaxena/Vayu

runpod-usage

How Runpod works and how to work it — pods vs serverless, GPU/VRAM selection, storage, building a container, networking, plus the agentic pod development loop (provision → ssh-exec → set up → poll readiness) and on-pod install hygiene (uv/apt). Use to answer "how does X work", "which GPU", "how do I build a container", or "how do I stand up a workload on a pod". Guidance, not a tool — execute with runpodctl, runpod-mcp, or flash.

★ 0
NeelakshSaxena
NeelakshSaxena/Vayu

runpod-templates

Runpod's official prebuilt pod templates (ComfyUI, PyTorch, and others): what each image ships, which ports and paths it uses, how to pick one, how to pin a version, and what is missing on first boot. Use when a task says "run <X> on a pod" and an official template already covers it, instead of building an image — and when a user needs help with or wants to fix something about a Runpod template they are already running (won't boot, can't reach the UI, missing models, wrong CUDA line, broken ComfyUI workflow metadata on imported workflows): start here and route onward. Deploy with runpodctl or runpod-mcp; end-to-end walkthroughs live in the runpod router's golden paths.

★ 0
NeelakshSaxena
NeelakshSaxena/Vayu

runpod-migrate

Migrate a codebase from the Runpod GraphQL API or REST v1 to REST v2 — inventory which parts use which API version, rewrite the call sites, flag breaking changes, and verify. Use when someone asks to move to v2, asks what v2 would change, or asks which Runpod API their code is on. For managing infrastructure rather than migrating code, use runpod-mcp or runpodctl.

★ 0
NeelakshSaxena
NeelakshSaxena/Vayu

runpod-mcp

Manage Runpod infrastructure — pods, serverless endpoints, jobs, templates, network volumes, container-registry auth, GPU/CPU catalog, and billing — via the Runpod MCP server's structured tool calls. Use when the Runpod MCP tools (create-pod, list-endpoints, …) are connected in this session, or to connect them (hosted OAuth or local npx). Prefer this over runpodctl for plain infra CRUD when MCP is available; use runpodctl for the terminal, file transfer, or SSH setup.

★ 0