Adversaries may use Naikon Identifying Strings to exfiltrate data or establish command and control by leveraging specific string patterns in network traffic. SOC teams should proactively hunt for this behavior in Azure Sentinel to detect potential data exfiltration or C2 activity early in the attack lifecycle.
YARA Rule
rule NaikonStrings : Naikon Family
{
meta:
description = "Naikon Identifying Strings"
author = "Seth Hardy"
last_modified = "2014-06-25"
strings:
$ = "NOKIAN95/WEB"
$ = "/tag=info&id=15"
$ = "skg(3)=&3.2d_u1"
$ = "\\Temp\\iExplorer.exe"
$ = "\\Temp\\\"TSG\""
condition:
any of them
}
This YARA rule can be deployed in the following contexts:
Scenario: A system administrator is using PowerShell to generate a report that includes the string “Naikon” as part of a script name or log message.
Filter/Exclusion: Exclude events where the source process is powershell.exe and the event description contains “report” or “script”.
Scenario: A scheduled job (e.g., using Windows Task Scheduler) runs a script that contains the string “Naikon” as part of a configuration file or variable name.
Filter/Exclusion: Exclude events where the process name is schtasks.exe or the event is associated with a known scheduled task name.
Scenario: A log management tool (e.g., Splunk or ELK Stack) is parsing logs and includes the term “Naikon” in a custom field or tag for categorization.
Filter/Exclusion: Exclude events where the source is a log management tool or where the log entry contains a known tag or field name like “custom_tag” or “log_type”.
Scenario: A database administrator is running a query using SQL Server Management Studio (SSMS) that includes the string “Naikon” in a query or table name.
Filter/Exclusion: Exclude events where the process is sqlservr.exe or the event is associated with a known database tool or query activity.
Scenario: A configuration management tool (e.g., Ansible or Chef) includes the string “Naikon” in a playbook or configuration file as part of a placeholder or variable.
Filter/Exclusion: Exclude events where the process is related to configuration management tools or where the file path contains known configuration directories like playbooks/ or config/.