Malicious Vice Society Directory Crawling Script for Data Exfiltration - Via Ps_script (via ps_script)

ATT&CK techniques

Execution → Exfiltration

Recon
Resource Dev
Initial Access
Execution
- T1059.001PowerShell
Persistence
Priv Esc
Defense Evasion
Cred Access
Discovery
Lateral Movement
Collection
C2
Exfiltration
- T1041Exfiltration Over C2 Channel
Impact

What it detects

This rule detects data exfiltration performed by the Vice Society ransomware gang using a custom built PowerShell script. More precisely, the script enumerates the volumes mounted on the system, then starts crawling the different directories before initiating the data exfiltration over HTTP by creating multiple different jobs. As PowerShell script block logs the script execution into multiple events, the detection aggregates the different log chunks using the ScriptBlockId and then ensure that at least 3 of the 4 detection strings are found.

Reporting behind it

Related detections9 linkedT1059.001 — drag to rearrange

Malicious PowerShell Exfiltration to webhook.site Following WSUS Exploitation

Malicious AWS Credential Exfiltration via Curl or Wget in Process Creation

Suspicious node.exe Execution Spawned by PowerShell

Suspicious PowerShell Spawned by mshta.exe in FakeSG Chain (via process_creation)

Suspicious Encoded PowerShell Using Base64 Stream Decompression Routines (via process_creation)

Malicious IIS Worker Process Spawning Command Shell for Webshell Reconnaissance (via process_creation)

Suspicious PowerShell Spawned by Windows Script Host during Scarlet Goldfinch Infection (via process_creation)

Suspicious PowerShell Launched by MSIX StartingScriptWrapper From WindowsApps via Process Creation (via process_creation)

Malicious Command Shell or PowerShell Spawned by Tomcat via Process Creation (via process_creation)

Malicious Vice Society Directory Crawling Script for Data Exfiltration - Via Ps_script (via ps_script)

Pivot detection · T1059.001 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.

Full detection rule

Unlock this rule to view and copy it

The detection logic is included with a plan. Everything else — context, mappings and implementation details — stays free on this page.

Sign in for 3 free unlocks

Signing in gives you 3 unlocks to spend on any rule in the library. No card, and they do not expire.

Also included

Unlocked rules convert on this page — to Splunk SPL or Splunk — Raw Index SPL or Microsoft Sentinel KQL or Microsoft Sentinel ASIM ASIM KQL or Microsoft Defender XDR KQL or Elastic Security KQL or Elastic Security Lucene or Elastic Security ES|QL or CrowdStrike Falcon CQL or SentinelOne PowerQuery or Palo Alto Cortex XDR XQL or Carbon Black Cloud Platform Search or Carbon Black EDR Process Search or Google Security Operations UDM Search or IBM QRadar AQL or Sumo Logic Cloud SIEM Rules expression or Rapid7 InsightIDR LEQL or Graylog Search or OpenSearch Lucene or OpenSearch PPL PPL or Grafana Loki LogQL or SQLite SQL or Zircolite SQLite — with the log-source profile the engine picked, the field map it used, and everything it could not express. Converting a rule you have unlocked costs no further credit.

See it run on a free rule →Convert your own rule →