Saltar al contenido
Nuevo

DeepSeek V4.1 Flash gratis por 7 días: 10M tokens al día tras una recarga de $10 o más. Hasta el 30/11.

Cómo funciona
mukul975/conducting-spearphishing-simulation-campaignWeb y bug bounty

conducting-spearphishing-simulation-campaign

⁨Run a targeted spearphishing simulation for initial access by developing OSINT-derived pretexts, building payloads (HTML smuggling, macro docs, ISO/LNK, OneNote, QR codes), standing up look-alike-domain email infrastructure with SPF/DKIM/DMARC via GoPhish, and tracking results. Use in authorized eng⁩

v1.03 instalaciones+3 en 7 días36,3 mil EstrellasApache-2.0sincronizado hace 12 horas

Instalar

¿Aún no tienes la CLI de NotHoly? Instálala primero.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install mukul975/conducting-spearphishing-simulation-campaign

Escribe en ⁦~/.notholy/skills⁩ después de comprobar la firma y el SHA-256.

FirmaFirmado, ed25519
93hQewOtrL…UQ4L4OBQ==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paquete8868dc0c…dc4e2c29
8868dc0c3324…5ab8dc4e2c298 archivos · ⁦19.5 KB⁩
EscaneoMedio3 hallazgos
  • Script ejecutable incluido con la skillscripts/agent.py
  • Script ejecutable incluido con la skillscripts/process.py
  • Enlaces a dominios externos
Ver el escaneo completo
Fuentegithub.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/conducting-spearphishing-simulation-campaign@54a7988

Esta entrada todavía no está escrita en tu idioma, así que aparece en English.

Legal Notice: This skill is for authorized security testing and educational purposes only. Unauthorized use against systems you do not own or have written permission to test is illegal and may violate computer fraud laws.

Overview

Spearphishing simulation is a targeted social engineering attack vector used by red teams to gain initial access. Unlike broad phishing campaigns, spearphishing uses OSINT-derived intelligence to craft highly personalized messages targeting specific individuals. This skill covers developing pretexts, building payloads, setting up email infrastructure, executing the campaign, and tracking results.

When to Use

  • When conducting security assessments that involve conducting spearphishing simulation campaign
  • 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

  • Develop convincing pretexts tailored to specific target personnel
  • Create weaponized payloads that bypass email security controls
  • Set up email delivery infrastructure with proper SPF/DKIM/DMARC configuration
  • Execute phishing campaigns with real-time tracking and metrics
  • Document results for engagement reporting and security awareness improvement

MITRE ATT&CK Mapping

  • T1566.001 - Phishing: Spearphishing Attachment
  • T1566.002 - Phishing: Spearphishing Link
  • T1566.003 - Phishing: Spearphishing via Service
  • T1598.003 - Phishing for Information: Spearphishing Link
  • T1204.001 - User Execution: Malicious Link
  • T1204.002 - User Execution: Malicious File
  • T1608.001 - Stage Capabilities: Upload Malware
  • T1608.005 - Stage Capabilities: Link Target
  • T1583.001 - Acquire Infrastructure: Domains
  • T1585.002 - Establish Accounts: Email Accounts

Workflow

Phase 1: Pretext Development

  1. Review OSINT findings for target personnel profiles
  2. Identify current organizational events (mergers, projects, new hires)
  3. Select pretext theme (IT helpdesk, HR benefits, vendor communication, executive request)
  4. Craft email templates with appropriate urgency and authority cues
  5. Create landing pages that mirror target organization's branding

Phase 2: Payload Development

  1. Select payload type based on target security controls:
    • HTML smuggling for email gateway bypass
    • Macro-enabled documents (if macros not blocked)
    • ISO/IMG files containing LNK payloads
    • OneNote files with embedded scripts
    • QR codes linking to credential harvesting pages
  2. Test payload against target's known security stack
  3. Implement payload obfuscation techniques
  4. Configure callback to C2 infrastructure

Phase 3: Infrastructure Setup

  1. Register convincing look-alike domain
  2. Age domain and build reputation (minimum 2 weeks recommended)
  3. Configure SPF, DKIM, and DMARC records
  4. Set up SMTP relay with GoPhish or custom mail server
  5. Deploy credential harvesting pages with SSL certificates
  6. Configure tracking pixels and click tracking

Phase 4: Campaign Execution

  1. Send test emails to verify delivery and rendering
  2. Launch campaign in waves (avoid mass sending)
  3. Monitor email delivery rates and opens in real-time
  4. Track link clicks and credential submissions
  5. Deploy payloads to users who interact with phishing emails
  6. Capture screenshots and evidence for reporting

Phase 5: Post-Campaign Analysis

  1. Calculate campaign metrics (delivery rate, open rate, click rate, credential capture rate)
  2. Identify users who reported phishing to SOC
  3. Document bypass of email security controls
  4. Map successful compromises to MITRE ATT&CK
  5. Compile findings for engagement report

Tools and Resources

Tool Purpose License
GoPhish Phishing campaign management Open Source
Evilginx2 Real-time credential harvesting with MFA bypass Open Source
King Phisher Phishing campaign toolkit Open Source
SET (Social Engineering Toolkit) Multi-vector social engineering Open Source
Modlishka Reverse proxy phishing Open Source
CredSniper Credential harvesting framework Open Source
Fierce Phish Phishing framework Open Source

Validation Criteria

  • Pretext tailored to specific targets with OSINT data
  • Payload tested against email security controls
  • Infrastructure configured with proper email authentication
  • Campaign tracked with delivery and interaction metrics
  • Evidence collected for engagement report
  • Cleanup performed on infrastructure post-campaign

Archivos de esta versión

Permisos

PermisoDeclaradoHallado en el escaneo
Lee archivosNoNo
Escribe archivosSíSí
Ejecuta comandos de shellSíSí
Usa la redSíSí
Usa conectoresNoNo
Controla un navegadorNoNo

Hallazgos del escaneo

Revisado el 13 nov 2026

  1. MediaArchivo · Script ejecutable incluido con la skillscripts/agent.py
  2. MediaArchivo · Script ejecutable incluido con la skillscripts/process.py
  3. InfoEnlace · Enlaces a dominios externos

Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.

VersiónPublicadaCommitSHA-256FirmaCambio de permisos
v1.013 nov 202654a79888868dc0cFirmada–

Pregunta todo lo que tu alcance permite.

Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.

  1. 1/3

    Crea la cuenta

    Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.

    IndividualEmpresa
  2. 2/3

    Añade créditos

    Con tarjeta. Pagas por token, sin suscripción.

    $5.00recarga mínima
  3. 3/3

    Pregunta

    En el chat, o instala el CLI y ejecuta notholy login en tu terminal.

    $ notholy login