Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
noorqureshi/social-eng-methodologySocial engineering and physical

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 installs+3 in 7 days27 StarsMITsynced 22 hours ago

Install

No NotHoly CLI yet? Install it first.

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

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
4L4gLqdcu9…YIBlgTDA==The CLI checks the SHA-256 and the signature before it writes a file.
Packagea30b6649…c3c069b6
a30b6649a6e7…bf1ec3c069b61 file · ⁦2.1 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/social-eng/social-eng-methodology@ee0e0c5

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.

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsNoNo
Uses the networkNoNo
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

The scan found nothing to flag in this version.

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.10.14-ee0e0c5Nov 13, 2026ee0e0c5a30b6649Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login