Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is NetExec?

NetExec, the maintained successor to CrackMapExec, tests credentials and runs modules across an entire network of Windows and Linux hosts from a single command.

Illustration for the cybersecurity term NetExec
Home / Blog / Cybersecurity Terms / What Is NetExec?
17 November 2026

What Is NetExec?

What Is NetExec?

NetExec, invoked as nxc, is a network execution and credential validation tool. Give it a credential and a range of addresses, and it will tell you every host on which that credential works, what level of access it grants, and what can be done with it. It is the community-maintained successor to CrackMapExec, which was archived in 2023 when its original maintainer stepped away; NetExec picked up the codebase, modernised it, and has been actively developed since.

Its significance is scale. Testing one credential against one host is unremarkable. Testing it against two thousand hosts in a few minutes, and getting back a list of where it grants administrative rights, converts a single compromised account into a map of the estate. That is also exactly what an intruder does in the first hour after obtaining a credential.

Protocols and Capabilities

NetExec speaks a wide set of protocols, each as a separate mode: SMB, WinRM, LDAP, MSSQL, SSH, FTP, RDP, VNC, WMI, and NFS. Within each, the same pattern applies. Supply credentials, supply targets, and receive a report of where authentication succeeded and with what privilege.

What it does beyond that:

Underneath, much of this is Impacket. NetExec is the orchestration layer that applies those protocol implementations across many hosts and presents the results coherently.

Why It Is Both Useful and Dangerous

For a tester, the value is the answer to the only question that matters after obtaining a credential: where does this work? The output immediately identifies the local administrator password reused across four hundred workstations, the service account that is an administrator on the domain controller, and the share containing a deployment script with a password in it.

For a defender, the same output is the argument for three specific controls. Unique local administrator passwords through LAPS make the first finding impossible. Tiered administration makes the second one less damaging. Reviewing share permissions and removing secrets from scripts addresses the third.

Detection

NetExec is loud by nature, because it touches many hosts in a short time from one source. That gives defenders a strong signal if authentication telemetry is collected centrally.

The limiting factor is almost never the signal. It is whether authentication events from workstations are forwarded centrally at all, which in many estates they are not.

Hardening

Deploy LAPS so that each machine has a unique local administrator password. Enforce tiered administration so that credentials from one tier cannot authenticate in another. Disable the local administrator account’s network logon where practicable, or apply the policy that prevents local accounts authenticating over the network. Require SMB signing. Audit share permissions and remove credentials from scripts, deployment files, and Group Policy. Move service accounts to group managed service accounts so their passwords are machine-generated and rotated automatically.

At Privia Security, our Infrastructure Security Testing Services map credential reuse across your estate and report which of your detections fired during the sweep.

FAQ – Frequently Asked Questions

What Happened to CrackMapExec?

Its original maintainer stepped away and the repository was archived in 2023. The community forked the codebase as NetExec, invoked as nxc, and has maintained and extended it since, adding protocols and modules and fixing the compatibility problems that had accumulated. Older documentation and incident reports refer to CrackMapExec; the tool and its techniques are the same lineage.

Does NetExec Exploit Vulnerabilities?

Mostly it does not. Its core function is authenticating with credentials you already hold and reporting where they work, which uses the protocols exactly as designed. Some modules check for or exploit specific known issues such as ZeroLogon, but the main capability needs no vulnerability at all. That is why credential hygiene matters more than patching against this particular class of activity.

How Do We Detect a Credential Sweep?

Aggregate authentication events by source rather than by target. One workstation authenticating to a hundred or more hosts in a short window is unmistakable, as are failures spread thinly across many accounts with a small password set. The usual obstacle is not the detection logic but whether workstation authentication events are forwarded to a central platform at all.

Which Control Reduces the Impact Most?

LAPS, because it removes local administrator password reuse. Without it, one recovered local credential frequently grants administrative access to every workstation built from the same image, which is the finding that turns a single compromise into estate-wide access. Pair it with tiered administration so that a credential captured in one tier cannot authenticate in another.

Related Terms

You May Be Interested In These

What Is FedRAMP?

Cybersecurity Terms

17 November 2026

What Is FedRAMP?

Read More
What Is OAuth Consent Phishing?

Cybersecurity Terms

17 November 2026

What Is OAuth Consent Phishing?

Read More
What Is mTLS?

Cybersecurity Terms

17 November 2026

What Is mTLS?

Read More