network-password-spraying
Low-and-slow credential attacks against exposed auth surfaces — spray one password across many users, and stuff known breach creds — without locking accounts. Load on a login portal or service auth with valid usernames: OWA/O365/Entra, VPN, Citrix, SSH, RDP, SMB, LDAP, or a web login. Signals: a har
v2026.10.14-ee0e0c53 installazioni+3 in 7 giorni27 StelleMITsincronizzato 22 ore fa
Installa
Non hai ancora la CLI di NotHoly? Installala prima.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/network-password-sprayingScrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
Pacchetto2c139ea0…619d95b9
2c139ea0780d…be3d619d95b91 file · 2.1 KBScansioneMedio1 segnalazione
- injection.no_confirmationSKILL.md:56
Sorgentegithub.com/NoorQureshi/security-skills/tree/main/skills/network/network-password-spraying@ee0e0c5
Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.
In questa pagina
When it applies
You have (or can build) a list of valid usernames and a reachable authentication surface, and the engagement authorizes credential attacks. Spraying beats brute force whenever a lockout policy exists — you try one password against every user, not many passwords against one.
Mode gate: this is
pentest-only. Nearly every bug-bounty program prohibits brute force, credential stuffing, and anything that risks account lockout or DoS — do not spray on a bounty target. Confirm the lockout policy and testing window inroe.md/scope.txtfirst (tradecraft-scope-roe).
Why it works
Organizations enforce complexity but not unpredictability: in any large user set, some accounts
use Season+Year!, Company@123, or a breach-reused password. Spraying one guess per user per
lockout window stays under the counter, so you get many attempts' worth of coverage without
tripping lockouts.
Method
- Build the user list. Enumerate/validate names first (OSINT,
recon-*, Kerbrute against a DC, O365 user-enum). Verify the username format (first.last,flast, UPN) before spraying. - Learn the lockout policy. Read it from AD (
net accounts,nxc smb <dc> --pass-pol) or ask. Stay to one attempt per user per window, and leave a margin (e.g. 4 tries if the threshold is 5). Track attempt timestamps so you never double-tap a user in a window. - Pick seasonal/contextual candidates, not a wordlist:
Month+Year!,Season+Year!,<CompanyName>1!,Welcome1,Password1. One or two per window, spaced across windows. - Spray the surface with a tool that throttles and tracks:
- AD/SMB/LDAP:
nxc smb <dc> -u users.txt -p 'Season2026!' --continue-on-success - Kerberos (pre-auth, quieter, no SMB logon events):
kerbrute passwordspray -d <domain> users.txt 'Season2026!' - O365/Entra: a purpose-built sprayer that handles throttling and MFA responses.
- AD/SMB/LDAP:
- On a hit, stop and pivot — validate the cred, check where it's valid (SMB/WinRM/VPN/OWA),
and move to
ad-*/privesc-*rather than continuing to spray.
Gotchas
- Lockout is the cardinal risk — miscounting windows or a retry loop can lock out a whole department. Rate is a hard limit, not a suggestion; when unsure, slow down.
- Smart lockout / conditional access (Entra) can look like a wrong password while silently flagging you — watch for changed response timing/codes, not just "failed".
- MFA: a valid password against an MFA-gated portal is still a real finding (and may expose MFA-fatigue or legacy-protocol bypass) — record it; don't try to defeat MFA unless authorized.
- Credential stuffing (breach-list creds) only against accounts/domains in scope; never load third-party breach data about people outside the engagement.
Verify success
A username+password pair authenticates against an in-scope service, confirmed with a benign action
(e.g. nxc reports [+], an OWA login, or a VPN session) — with no accounts locked out.
References
MITRE ATT&CK T1110.003/.004; NetExec (nxc) and Kerbrute docs; NIST SP 800-63B on credential policy.
File di questa versione
- SKILL.md3.8 KB
Permessi
| Permesso | Dichiarato | Trovato dalla scansione |
|---|---|---|
| Legge file | No | No |
| Scrive file | Sì | Sì |
| Esegue comandi shell | No | No |
| Usa la rete | No | No |
| Usa i connettori | No | No |
| Controlla un browser | No | No |
Segnalazioni della scansione
Rivisto il 13 nov 2026
- MediaPrompt injection · injection.no_confirmationSKILL.md:56
Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.
| Versione | Pubblicata | Commit | SHA-256 | Firma | Cambio di permessi |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | 13 nov 2026 | ee0e0c5 | 2c139ea0 | Firmata | – |
Altro da NoorQureshi
Tutto da questo editoreAltro in Rete, wireless e telecomunicazioni
Vai alla categoria- performing-network-packet-capture-analysismukul975/performing-network-packet-capture-analysis4
- network-segmentation-reviewsecurityskills/network-segmentation-review3
- performing-ssl-stripping-attackmukul975/performing-ssl-stripping-attack3
- implementing-next-generation-firewall-with-palo-altomukul975/implementing-next-generation-firewall-with-palo-alto3
- configuring-zscaler-private-access-for-ztnamukul975/configuring-zscaler-private-access-for-ztna3
- implementing-canary-tokens-for-network-intrusionmukul975/implementing-canary-tokens-for-network-intrusion3
Chiedi tutto quello che il tuo perimetro consente.
Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.
- 1/3
Crea l'account
Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.
PrivatoAzienda - 2/3
Aggiungi crediti
Con carta. Paghi a token, senza abbonamento.
$5.00ricarica minima - 3/3
Chiedi
In chat, oppure installa la CLI ed esegui notholy login nel terminale.
$ notholy login