Source: itamarhall.github.io
Author: unknown
URL: https://itamarhall.github.io/Tracepoint/blog/writeups/edr-freeze-investigation/
ONE SENTENCE SUMMARY:
EDR-Freeze demonstrates how attackers can temporarily suspend EDR processes using Windows components, impacting defender visibility and requiring advanced forensic detection.
MAIN POINTS:
- EDR-Freeze uses Windows Error Reporting to suspend EDR processes temporarily.
- Involves WerFaultSecure.exe and DbgHelp’s MiniDumpWriteDump components.
- Process appears suspended in memory, affecting telemetry.
- Volatility tools help identify forensic artifacts left by EDR-Freeze.
- Memory forensics reveals suspended threads and handles used.
- File activity observed with temporary t.txt creation.
- Imports like MiniDumpWriteDump show potential for process suspension.
- YARA rules help detect EDR-Freeze’s presence in binaries and memory.
- Source code explains observed memory and file artifacts.
- Showcases the risk of trusted OS components being used maliciously.
TAKEAWAYS:
- Detection goes beyond logs to include memory analysis and forensic investigation.
- YARA rules can catch both binary and behavioral indicators of EDR-Freeze.
- EDR processes are vulnerable to suspension without kernel exploits.
- Highlights the potential abuse of trusted Windows components by attackers.
- Encourages focus on memory forensics as a crucial part of incident response.