This hunt hypothesis identifies the execution of known .NET-based red and black team reconnaissance or testing tools by analyzing process names to distinguish legitimate security activities from potential adversary tooling. Proactively hunting for these indicators in Azure Sentinel allows the SOC team to validate authorized security operations, reduce false positives during incident response, and detect unauthorized use of similar frameworks by malicious actors.
rule HKTL_NET_NAME_aspnetcore_bypassing_authentication {
meta:
description = "Detects .NET red/black-team tools via name"
reference = "https://github.com/jackowild/aspnetcore-bypassing-authentication"
author = "Arnim Rupp"
date = "2021-01-22"
strings:
$name = "aspnetcore-bypassing-authentication" ascii wide
$compile = "AssemblyTitle" ascii wide
condition:
(uint16(0) == 0x5A4D and uint32(uint32(0x3C)) == 0x00004550) and all of them
}
This YARA rule can be deployed in the following contexts:
This rule contains 2 string patterns in its detection logic.
Here are 5 specific false positive scenarios for the rule “Detects .NET red/blue-team tools via name,” along with suggested filters or exclusions:
Scenario: A scheduled backup job utilizing Veeam Backup & Replication (which relies heavily on .NET assemblies like Veeam.Backup.Service.exe) runs during business hours, triggering the rule due to its .NET nature and security-related naming convention.
\Program Files\Veeam Backup\ AND the parent process is Task Scheduler (or a specific Service Account like SYSTEM).Scenario: The IT Operations team deploys updates using Microsoft Endpoint Configuration Manager (SCCM/MECM), which executes .NET-based deployment agents (ccmexec.exe) that spawn child processes with names resembling security tools.
ccmexec.exe and the command line contains keywords like “Software Update,” “Deployment,” or “Patch.”Scenario: Internal developers run automated unit tests on a build server (e.g., Jenkins or Azure DevOps) using .NET Core SDK tools, specifically invoking dotnet.exe with arguments that include security library names (e.g., --project Security.Tests.csproj).
build-server-01) or where the user context is a dedicated service account like svc-build-agent.Scenario: The Enterprise Resource Planning (ERP) system, such as Microsoft Dynamics 365 or SAP Business One, executes nightly data reconciliation jobs using .NET executables named similarly to threat hunting tools.