Renamed PingCastle Binary Execution

Last updated on:

About the rule

Rule Type

Standard

Rule Description

Detects the execution of a renamed "PingCastle" binary based on the PE metadata fields.

Severity

Trouble

Rule Requirement

Criteria

Action1: actionname = "Process started" AND (ORIGINALFILENAME = "PingCastleReporting.exe,PingCastleCloud.exe,PingCastle.exe" OR COMMANDLINE contains "--scanner aclcheck,--scanner antivirus,--scanner computerversion,--scanner foreignusers,--scanner laps_bitlocker,--scanner localadmin,--scanner nullsession,--scanner nullsession-trust,--scanner oxidbindings,--scanner remote,--scanner share,--scanner smb,--scanner smb3querynetwork,--scanner spooler,--scanner startup,--scanner zerologon" OR COMMANDLINE contains "--no-enum-limit" OR (COMMANDLINE contains "--healthcheck" AND COMMANDLINE contains "--level Full") OR (COMMANDLINE contains "--healthcheck" AND COMMANDLINE contains "--server ")) AND PROCESSNAME notendswith "\PingCastleReporting.exe,\PingCastleCloud.exe,\PingCastle.exe" select Action1.HOSTNAME,Action1.MESSAGE,Action1.COMMANDLINE,Action1.FILE_NAME,Action1.PROCESSNAME,Action1.USERNAME,Action1.PARENTPROCESSNAME

Detection

Execution Mode

realtime

Log Sources

Windows

Author

Nasreddine Bencherchali (Nextron Systems), X__Junior (Nextron Systems)