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-methodologyEngenharia social e física

social-eng-methodology

⁨Plan and run an AUTHORIZED social-engineering assessment safely — the load-first guardrails for any human-factor test. Load before any phishing, vishing, pretext, or physical work. Signals: "social engineering", "phishing assessment", "test our employees", "security awareness", a human-factor object⁩

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

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

AssinaturaAssinado, ed25519
4L4gLqdcu9…YIBlgTDA==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacotea30b6649…c3c069b6
a30b6649a6e7…bf1ec3c069b61 arquivo · ⁦2.1 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-methodology@ee0e0c5

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

When this governs

Load this first, before any phishing/vishing/pretext/physical skill. Social engineering targets people, so it carries authorization and duty-of-care requirements beyond a normal technical test. This is pentest-only: it is never run against a bug-bounty target, and never against individuals or organizations that have not authorized it in writing.

Authorization — stricter than technical scope

On top of tradecraft-scope-roe, an SE engagement requires, in writing, before anything:

  • Explicit sign-off from someone empowered to consent for the employees being tested (not just IT) — SE tests real staff, so leadership/HR/legal must have approved the human-factor testing.
  • The pretext boundaries: which themes are allowed and which are off-limits (no fake layoffs, bonuses, medical/family emergencies, or anything that causes real distress or coerces protected decisions).
  • Target boundaries: which people/roles/sites are in scope; who is explicitly excluded.
  • A "no-harm" line: no real financial transactions, no exfiltration of real personal data, no actions that damage systems, and no impersonation of real named individuals without consent.
  • A get-out-of-jail letter carried during any physical work, plus a live emergency contact who can confirm authorization to anyone who challenges the tester.

If any of that is missing or unclear, stop and get it — do not "just send a test phish".

The lifecycle

  1. Objective — what the client wants to learn (click rate, credential submission, report rate, physical access, callback rate). It's a measurement, not a "gotcha".
  2. Recon — only OSINT needed for a credible pretext (recon-osint), scoped to in-scope targets.
  3. Pretext design — believable, within the allowed themes, proportionate to the objective.
  4. Execute with tracking — instrument so every step is measured and attributable to the test (unique tokens/links), and so results can't be confused with a real attack.
  5. Measure & clean up — collect metrics, disable pretext infra, and delete any personal data captured beyond what the metric needs.
  6. Report for awareness — outcomes and root causes, framed to improve defenses and training, never to name-and-shame individuals.

Guardrails (always)

  • Minimize harm and data. Prove the human-factor risk with the least intrusion; capture the metric, not people's real secrets. A credential-harvest page records "a credential was submitted", it does not store or reuse real passwords.
  • Stay attributable and reversible. Every artifact is tagged as the assessment; nothing is left running; a challenged tester can prove authorization immediately.
  • Protect the humans. No lasting distress, no targeting of individuals' personal/home life, no themes the client excluded. If a target escalates emotionally, de-escalate and disclose.
  • Report defensively. Findings drive controls (MFA, reporting culture, physical procedures) and training — individuals are aggregated, not singled out.

Verify

Written authorization (incl. consent for testing staff), agreed pretext/target boundaries, a no-harm line, and a tracking + cleanup plan all exist before execution; the deliverable is an awareness-oriented report with metrics and remediation.

References

MITRE ATT&CK T1566 (Phishing), T1598 (Phishing for Information); disclose.io-style safe-harbor framing; standard pentest SE rules of engagement.

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 2026ee0e0c5a30b6649Assinada–

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