This hunt targets the presence of known IOCs associated with the php.shin_webshell, indicating that an adversary has likely established a persistent foothold on a web server to execute arbitrary commands. Proactively hunting for these indicators in Azure Sentinel is critical to identify compromised assets before the webshell is leveraged for lateral movement or data exfiltration.
Malware Family: php.shin_webshell Total IOCs: 5 IOC Types: domain
| Type | Value | Threat Type | First Seen | Confidence |
|---|---|---|---|---|
| domain | kilijuxy.workers.dev | botnet_cc | 2026-09-11 | 50% |
| domain | zusucuhe.workers.dev | botnet_cc | 2026-09-11 | 50% |
| domain | xegave.workers.dev | botnet_cc | 2026-09-11 | 50% |
| domain | zikyci.workers.dev | botnet_cc | 2026-09-11 | 50% |
| domain | qoxuce.workers.dev | botnet_cc | 2026-09-11 | 50% |
// Hunt for DNS queries to known malicious domains
// Source: ThreatFox - php.shin_webshell
let malicious_domains = dynamic(["kilijuxy.workers.dev", "zusucuhe.workers.dev", "xegave.workers.dev", "zikyci.workers.dev", "qoxuce.workers.dev"]);
DnsEvents
| where Name has_any (malicious_domains)
| project TimeGenerated, Computer, Name, IPAddresses, QueryType
| order by TimeGenerated desc
| Sentinel Table | Notes |
|---|---|
DnsEvents | Ensure this data connector is enabled |
shin.php: A legacy PHP-based content management system (e.g., an older version of WordPress or a custom internal portal) may include a file named shin.php or similar variants as part of a deprecated plugin or theme update script. This file might be used for temporary debugging or data migration tasks that were never cleaned up.
/var/www/html/legacy-cms/plugins/) or exclude files where the parent directory contains known legacy framework identifiers (e.g., wp-content, joomla).cron job or Windows Task Scheduler entry) runs a PHP script named shin_webshell.php or shin.php to synchronize configuration files or logs between web servers and a central log aggregation server. The script is benign but matches the IOC filename pattern.
/opt/backup/scripts/, C:\ProgramData\SyncTools\) or correlate with specific service accounts (e.g., svc-backup, backup-admin) that execute the file.shin.php for API testing or mock data generation. This environment is not production but is still monitored by the SOC.
env=staging, env=dev, or env=qa in your CMDB or asset inventory. Alternatively, exclude paths under /var/www/html/dev/ or C:\inetpub\wwwroot\staging\.