Pular para o conteúdo
Novo

DeepSeek V4.1 Flash grátis por 7 dias: 10M tokens por dia após recarga de $10 ou mais. Até 30/11.

Como funciona
noorqureshi/social-eng-phishingEngenharia social e física

social-eng-phishing

⁨Run an authorized phishing / spear-phishing assessment that measures human-factor risk — pretext, delivery, landing page, and tracking — without harming staff or hoarding real data. Load after social-eng-methodology when the objective is email-based (click, credential submission, or report rate). Si⁩

v2026.10.14-ee0e0c53 instalações+3 em 7 dias27 EstrelasMITsincronizado há 22 horas

Instalar

Ainda não tem a CLI da NotHoly? Instale primeiro.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install noorqureshi/social-eng-phishing

Grava em ⁦~/.notholy/skills⁩ depois de conferir a assinatura e o SHA-256.

AssinaturaAssinado, ed25519
Zglqy9p02+…WW6lLoBw==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacote7310aef2…5cb5f057
7310aef2266a…f2a05cb5f0571 arquivo · ⁦1.9 KB⁩
VarreduraBaixonenhum achado
A varredura não encontrou nada para apontar nesta versão.Ver a varredura completa
Fontegithub.com/NoorQureshi/security-skills/tree/main/skills/social-eng/social-eng-phishing@ee0e0c5

Este item ainda não foi escrito no seu idioma, então aparece em English.

When it applies

The engagement authorizes an email human-factor test and you've cleared social-eng-methodology (authorization, allowed pretext themes, target boundaries, no-harm line). The goal is a measurement — click rate, credential-submission rate, and, most importantly, the report rate — not to embarrass anyone.

Why it works

Phishing exploits trust and context, not a software bug: a message that looks like it comes from a trusted source, with a plausible reason to act now, gets clicks even from trained users. Measuring that safely tells the client where awareness and technical controls (MFA, mail filtering, reporting tooling) need to improve.

Method

  1. Pick the objective and metric. Awareness baseline (did they click?), credential resilience (did they submit?), or reporting culture (did they report it, and how fast?). The metric shapes the whole campaign.
  2. Scope the target list to authorized recipients only; segment (department/role) so results are actionable. Never add anyone outside the agreed boundaries.
  3. Design a proportionate pretext within the allowed themes (e.g. an internal IT/HR notice, a shared-document notification). Keep it believable but avoid excluded/harmful themes and real named individuals.
  4. Stand up tracked infrastructure. A dedicated sender domain and a landing page, every recipient carrying a unique token so clicks/submissions are attributable to the test. Use a framework built for this (e.g. GoPhish) so tracking and teardown are clean.
  5. Land safely. The page measures the action and then discloses it's an authorized assessment with a short awareness message. A credential form records "a credential was submitted" for the metric — it does not store, display, or reuse the real password.
  6. Deliver and measure over the agreed window; capture click/submit/report rates and time-to- report per segment.
  7. Tear down and clean up. Disable the infra, purge any captured data beyond the metric, and confirm nothing is left reachable.

Gotchas

  • Never keep real credentials. Record the event, not the secret; a test that stockpiles staff passwords has itself become the risk.
  • Report rate is the win metric — a high report rate is a healthy result; frame it that way, don't optimize purely for clicks.
  • Coordinate with the blue team/help desk per RoE so a real incident response isn't triggered (or, if testing detection, so it's an intended part of the exercise).
  • Aggregate results. The report improves controls and training; it does not name and shame individuals.
  • Excluded themes stay excluded — no fake emergencies, layoffs, or bonuses; proportionality is a hard limit from social-eng-methodology.

Verify success

A clean metric set (click / submission / report rates, time-to-report) attributable to the test, with all pretext infrastructure torn down and no real personal data retained — feeding an awareness-focused writeup (reporting-pentest-report).

References

MITRE ATT&CK T1566.001/.002, T1598.003; GoPhish documentation; awareness-program metrics guidance.

Arquivos desta versão

Permissões

PermissãoDeclaradaEncontrada na varredura
Lê arquivosNãoNão
Grava arquivosNãoNão
Roda comandos no shellNãoNão
Usa a redeNãoNão
Usa conectoresNãoNão
Controla um navegadorNãoNão

Achados da varredura

Revisado em 13 de nov. de 2026

A varredura não encontrou nada para apontar nesta versão.

Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.

VersãoPublicada emCommitSHA-256AssinaturaMudança de permissão
v2026.10.14-ee0e0c513 de nov. de 2026ee0e0c57310aef2Assinada–

Pergunte tudo o que o seu escopo permite.

Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.

  1. 1/3

    Crie a conta

    Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.

    Pessoa físicaEmpresa
  2. 2/3

    Adicione créditos

    No cartão. Você paga por token, sem assinatura.

    $5.00recarga mínima
  3. 3/3

    Pergunte

    No chat, ou instale o CLI e rode notholy login no terminal.

    $ notholy login