This detection identifies potential reconnaissance activity where adversaries execute the BluesPortScan.exe utility to map network topology and identify open ports for lateral movement. Proactively hunting for this behavior in Azure Sentinel is critical because automated port scanning often serves as a precursor to more significant attacks, allowing analysts to validate legitimate administrative tasks against suspicious early-stage threat indicators before they escalate.
rule BluesPortScan {
meta:
description = "Auto-generated rule on file BluesPortScan.exe"
author = "yarGen Yara Rule Generator by Florian Roth"
hash = "6292f5fc737511f91af5e35643fc9eef"
strings:
$s0 = "This program was made by Volker Voss"
$s1 = "JiBOo~SSB"
condition:
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 3-5 specific false positive scenarios for the BluesPortScan.exe detection rule, including tailored filters and exclusions:
Scenario: Scheduled Network Inventory Job
BluesPortScan.exe to all endpoints during the maintenance window (e.g., 02:00 – 04:00) to map open ports and active services.C:\Program Files\BluesPortScan\BluesPortScan.exe only between 01:30 and 05:00 on weekdays, or exclude the specific SCCM/SolarWinds service account (e.g., DOMAIN\sccm_service) from triggering this rule.Scenario: Endpoint Protection Health Check
BluesPortScan.exe as a lightweight agent component to perform periodic connectivity checks against the security management server and verify firewall rule integrity.BluesPortScan.exe is identified as FalconSensor.exe, SentinelOneAgent.exe, or WindowsUpdate.exe, suppress the alert, assuming this is a legitimate health check initiated by the security suite itself.Scenario: IT Admin Manual Troubleshooting
BluesPortScan.exe from their