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-vishing-pretextSocial engineering and physical

social-eng-vishing-pretext

⁨Run authorized voice-phishing (vishing) and pretext-based scenarios that test whether staff and help desks follow verification procedures — safely and by consent. Load after social-eng-methodology when the objective is phone/live-interaction based (help-desk password reset, MFA-reset abuse, pretext ⁩

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-vishing-pretext

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

SignatureSigned, ed25519
buoV/KCXxp…IBrzN8DQ==The CLI checks the SHA-256 and the signature before it writes a file.
Package2b60a27f…217932f2
2b60a27f0b4e…104d217932f21 file · ⁦1.9 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-vishing-pretext@ee0e0c5

When it applies

The engagement authorizes live-interaction testing (cleared via social-eng-methodology) and the objective is a process test: will the help desk reset a password or MFA without proper verification? Will an employee act on a convincing caller? This targets procedure adherence, which phishing email can't measure. Help-desk MFA-reset abuse is a leading real-world initial-access vector, so testing it is high-value.

Why it works

Voice adds urgency, authority, and social pressure that written channels lack — a confident caller with a few true details (from recon-osint) and a plausible reason routinely gets a human to skip a verification step. The finding is the gap in the verification procedure, not the individual who answered.

Method

  1. Define the process under test and the pass/fail line with the client: e.g. "help desk must require callback-to-known-number + a second factor before any reset." The test measures whether that line holds.
  2. Build a proportionate pretext within allowed themes — a plausible role (a named-role, not a real named person, unless consented), a believable reason, and only the OSINT detail needed for credibility.
  3. Prepare a call plan and an immediate stand-down. Script the ask, the escalation, and the point at which you disclose. Keep the authorization/emergency contact ready if challenged.
  4. Execute a bounded number of attempts per RoE, tracking each: target, request, which verification steps were performed vs. skipped, and the outcome.
  5. Stop at the objective. Once a step is bypassed (or correctly refused), you have the result — do not proceed to actually reset/log in or take any real account action beyond proving the procedure gap; disclose per plan.
  6. Debrief. Capture where the procedure failed and why; hand it to the awareness/report step.

Gotchas

  • Prove the gap, don't exploit it. A help desk agreeing to reset MFA is the finding — you do not complete a real takeover; stop and record it.
  • De-escalate distress. If a target becomes anxious or suspicious, disclose the assessment and reassure them; their cooperation isn't the point, the procedure is.
  • No coercion or protected topics — the excluded-theme and no-harm rules from social-eng-methodology apply in full over the phone.
  • Attribute cleanly — use test lines/tokens so a call can be confirmed as the assessment, and coordinate so it isn't mistaken for a real fraud attempt.
  • Recording laws vary — only record calls where lawful and agreed in the RoE.

Verify success

A documented result per attempt — which verification steps held or failed and the outcome — with no real account actions taken and every target debriefed, feeding a procedure-focused report and remediation (stronger help-desk verification, callback policy, MFA-reset controls).

References

MITRE ATT&CK T1598.004 (phishing for information via voice), T1656 (impersonation); help-desk verification / MFA-reset hardening guidance.

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, 2026ee0e0c52b60a27fSigned–

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