As part of a batch script I have setup for a simple operation on my system, I get the current date/time via a powershell command.
Specifically,
for /f "tokens=1-3 delims=_ " %%a in ('powershell -Command "Get-Date -format yyyy_MM_dd"') DO (SET dt=%%a-%%b-%%c)
for /f "tokens=1-3 delims=_ " %%a in ('powershell -Command "Get-Date -format HH_mm_ss"') DO (SET tm=%%a-%%b-%%c)
Today, the Malwarebytes client (v4.6.2), gave me a warning and blocked the command from running, which caused the script to lack the date/time values needed to run normally.
Pretty sure this is a false detection, but I'm not sure how to work around it without completely disabling protection while my script runs.
I didn't find a direct support contact, so I'm posting here.
Screenshot of where this causes the disruption in script execution and exported report attached.
2023-09-15_MBAM-Issue.txt
