Process

unknown

net1.exe

net1.exe is the worker binary behind the Windows net command. For most net sub-commands, net.exe forwards the actual work to net1.exe, so it normally appears as a child of net.exe and shares its entire feature and abuse surface. Attackers sometimes call net1.exe directly to evade detections that only watch net.exe.

File identity

File details

Not observed.

Signing information

Not observed.

File version0

Not observed.

File size0

Not observed.

Execution context

File paths0

Not observed.

User context0

Not observed.

Integrity level0

Not observed.

Instances0

Not observed.

Session0

Not observed.

Token privileges0

Not observed.

Ancestry

Parents0

Not observed.

Children0

Not observed.

Grandparents0

Not observed.

Grandchildren0

Not observed.

Behavior

Loaded modules0

Not observed.

Named pipes0

Not observed.

Process handles0

Not observed.

Command-line patterns0

Not observed.

Indicators

Hashes

Not observed.

Analysis

About this process

net1.exe carries out the operations of the net command. When something runs net user, net group, net use, and most other sub-commands, net.exe parses the request and relaunches net1.exe to perform it. The split is historical, but the effect today is that net1.exe does the real work while net.exe is the front end. The genuine binary lives at C:\Windows\System32\net1.exe, and a net1.exe whose parent is net.exe is completely normal.

Everything net1.exe can do is the same as net.exe, account, group, share, session, and service management, because it is the same functionality. The meaningful difference for triage is how it was started: as a child of net.exe during ordinary use, or directly by some other process.

Security notes

net1.exe carries the same abuse surface as net.exe: account and group reconnaissance (T1087.002, T1069.002), remote share access for lateral movement (T1021.002), and account creation and privilege grants (T1136.001). See the net.exe profile for the detail.

Its own particular value to an attacker is evasion. Because net.exe normally forwards to net1.exe, some detections only watch net.exe and miss the same command issued directly to net1.exe. A net1.exe with no net.exe parent, running recon or /add commands, is the case to flag, the worker invoked on its own to slip past a rule written for the front end.

Anomaly signals5
  • Image path other than C:\Windows\System32\net1.exehigh
  • Parent is an Office application, a script host, or an unfamiliar processhigh
  • net1 user /add or net1 localgroup administrators <user> /addhigh
  • net1.exe started directly, with no net.exe parentmed
  • Domain recon such as net1 group "domain admins" /domainmed

Telemetry

OS prevalence0

Not observed.

Observation timeline

Not observed.

References

Subsearch

Hasbeen seen inof net1.exe?