TEMPLATE - Hunter-Case-XX - <ATTACK-MALWARE-INFORMATION>

1.) MALWARE-INFORMATION

  • Malware

2.) Story Information

Hunter Blue's day started like everyday with researching the cyber security news for new Threat Huntings tasks to find malicious traces on customer datalakes.

You should investigate the initial Entry and Execution to search through the logs with these IoCs / IoAs to find the right artifacts for Threat Hunting.

2.) Indicators of Compromise

Indicators of compromise

Type
Value
Notes / usage

SHA256

SHA256

SHA256

SHA256

URL (webhook)

Filename / Workflow

GitHub repo name

Tool abuse indicator

2.1) Executions from Threat Actor - Steps

  • worm executes during the post-install phase

2.2) Indicators of Compromise - Executions

3.) Initial Access

4.) Finding through Threat Hunting

  • We hunted through the Datalake logs in the whole infrastructure and yes you guess it right we found a malicious execution not related to legit admin tasks

5.) Mitigation

6.) Detection and Hunting

6.1) Sigma Rules

6.2) Linux Commandline Hunting

6.3) Hunting Queries Microsoft Defender XDR

6.4) Hunting Queries Palo Cortex XDR

6.5) Hunting Queries Tanium EDR

6.6) Hunting Queries Crowdstrike XDR

7.) Conclusion and Learning for a Hunter Blue

  • The NPM incident reveals Supply chain attacks are increasing in frequency. It is more important than ever to monitor third-party packages for malicious activity. Since malicious code can be hidden in many different ways, using runtime threat detection is critical to catching these attack

  • its definitely necessary to check during Hunting or Initial Triage how Malware was staged

  • -> showcasing how fruitful Compromise Assessment Hunting and Time Line Analysis can be and should be used in such cases -> it is essential.

Last updated