sudo cscli collections install crowdsecurity/auditdInstalls 1 parser and 6 scenarios.
View Auditd - Post-Exploitation Detection →sudo cscli scenarios install crowdsecurity/auditd-postexploit-rmThen reload CrowdSec: sudo systemctl reload crowdsec
Sign in to see which of your engines run it →Hover a line or a note to see what each field does.
type: leaky#debug: truename: crowdsecurity/auditd-postexploit-rmdescription: "Detect post-exploitation behaviour : rm execve bursts"filter: evt.Meta.log_type == 'execve' && evt.Meta.exe in ['/usr/bin/rm', '/bin/rm']#grouping by ppid to track on process doing a lot of invocations to rm, such as a shell scriptgroupby: evt.Meta.ppidleakspeed: 1scapacity: 5blackhole: 1mlabels:confidence: 1spoofable: 0classification:- attack.T1059.004behavior: "linux:post-exploitation"intent: anomalouslabel: "Post Exploitation command execution"service: linuxremediation: falsescope:type: pidexpression: evt.Meta.ppid
Sign in to see the Security Engines that run this attack scenario, the version they run and whether it was modified locally.
Attempt to detect a process that is attempting to rm a lot of files.
This pattern is usually seen in post-exploitation behaviors where a backdoors is trying to "kill" competition.