nxs
What can this cred actually do?
nxs is a credential capability mapper powered by NetExec. It takes a credential and checks it against 10 different protocols (SMB, LDAP, WMI, WinRM, SSH, RDP, MSSQL, FTP, VNC, NFS) to show you exactly what level of access you have on the target.
Install
pipx install nxsctl
Requires NetExec (nxc) in PATH.
Usage
nxs 10.10.10.10 -u john.doe -p 'Password123' -d domain.local
Password prompt if -p is omitted:
nxs 10.10.10.10 -u john.doe -d domain.local
Hash authentication:
nxs 10.10.10.10 -u john.doe -H NT_HASH -d domain.local
nxs 10.10.10.10 -u john.doe -H LM_HASH:NT_HASH -d domain.local
Quickstart
nxs 10.10.10.10 -u admin -p 'Password123!'
# Spray a file of credentials (format: user:pass or user:hash)
nxs 10.10.10.10 -f creds.txt
# Password spray — one password across a user list
nxs 10.10.10.10 -u users.txt -p 'Password123!'
# All combinations — every user × every password (-C/--combo)
nxs 10.10.10.10 -u users.txt -p passwords.txt -C
# Specific protocols
nxs 192.168.1.0/24 -u john.doe -H 'LM:NT' --protocols ssh,winrm
OPSEC mode (single-threaded, low retry):
nxs 10.10.10.10 -u john.doe -p 'Password123' -d domain.local --opsec
Kerberos:
nxs 10.10.10.10 -u john.doe -p 'Password123' -d domain.local -k --kdc-host dc01.domain.local
# Authenticate with a ccache ticket file (no password needed):
nxs 10.10.10.10 -T user.ccache
# Scan a directory of tickets:
nxs 10.10.10.10 -T ./tickets/
JSON output:
nxs 10.10.10.10 -u john.doe -p 'Password123' --json
nxs 10.10.10.10 -u john.doe -p 'Password123' --json --raw
Save raw proof:
nxs 10.10.10.10 -u john.doe -p 'Password123' --save loot/
Verbose output (detailed execution info, WIP...):
nxs 10.10.10.10 -u john.doe -p 'Password123' --verbose
Example Output
nxs v0.1.0 10.10.10.10 · john.doe@domain.local · 4 protocols
[+] SMB WRITE Shared[READ+WRITE], Web[READ]
[+] LDAP READ Enumerated 15 domain users
[-] WINRM NO Authentication failed
With --verbose, detailed output is nested underneath:
nxs v0.1.0 10.10.10.10 · admin · 1 protocols
[+] WINRM EXEC domain.local\admin
↳ USER INFORMATION
↳ ----------------
↳ User Name SID
↳ ================= ============================================
↳ domain\admin S-1-5-21-3623811015-3361044348-30300820-500
Access Levels
| Level | Marker | Meaning |
|---|---|---|
ADMIN |
[+] |
Admin-level access |
EXEC |
[+] |
Command execution |
WRITE |
[+] |
Write access |
READ |
[+] |
Read access |
AUTH |
[*] |
Authenticated, no further access |
UNCLEAR |
[?] |
Inconclusive result |
NO |
[-] |
Authentication failed or port closed |
License
Release files for nxsctl 0.3.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| nxsctl-0.3.6.tar.gz | 17.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nxsctl-0.3.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 37.3 kB
Release files / nxsctl-0.3.6.tar.gz
| Download URL | nxsctl-0.3.6.tar.gz |
|---|---|
| Size | 17.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e9123d2d47f726b47765be6620bafbe1e6f9fc70974a2b405601b89ca4bdc1e1
|
|
BLAKE2b-256 checksum How to use checksums |
c1ae149a5343b3845d6a2b09606c675a174f05aa5f18a688eecc3108243cec1a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 1, 2026.
Transparency logRelease files / nxsctl-0.3.6-py3-none-any.whl
| Download URL | nxsctl-0.3.6-py3-none-any.whl |
|---|---|
| Size | 19.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fd71ccb32a1f6743158d13d89cc053a81a630760ed572b27a1b0f2eba4fc40f9
|
|
BLAKE2b-256 checksum How to use checksums |
b65edfe441363a6fc2ce4ec00fd23a608493e0b393f11ff9d7d6ea1205c67a74
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 1, 2026.
Transparency log