Anyone looking for a SOC manager role? My company is hiring. Comp package is best I’ve seen anywhere and the team is awesome. Some excellent talent to work with. DM me for details #infosecjobs#cybersecurityjobs
Don't know what an Azure Run Command is? Neither did I when we first stumbled on an attacker abusing this during a recent IR case. We wrote a short blog on these and what to look for if you're writing detections for your Azure VMs.
mandiant.com/resources/azure…
I promised I would write a report covering my phishing research in 2021.
That report is now live:
steved3.io/data/Phishing-202…
Shout out to @AmandaFGoedde for helping me edit, as well as @ninoseki for making Miteru, and @urlscanio for creating an awesome tool to help defenders.
Kinsing cryptomining Linux malware has adopted #log4j to exploit new hosts. It is also bringing along a stealth rootkit to hide. In this article we go over what it is doing and how you can decloak it for incident response:
sandflysecurity.com/blog/log…
You can also use these pipelines for other data sources. The ""cat access.log | sed 's/.*"\([^"]*\)"$/\1/'" is how I'm extracting the user agent strings from the Apache log format. Everything after that is shell idioms you can apply to any data.
Encoded #log4j user agents are longer than normal user agent strings:
"cat access.log | sed 's/.*"\([^"]*\)"$/\1/' | sort -u | while read str; do len=$(echo $str | wc -c); echo -e $len\\t$str; done | sort -n"
Sort unique user agent strings by length, ascending
Looking for #log4j encoded user agents in Apache "combined" access log format:
"cat access.log | sed 's/.*"\([^"]*\)"$/\1/' | sort | uniq -c | sort -rn"
Histogram of all user agents in descending order (unique encoded user agents right above your shell prompt)
Just added support to LDAP Serialized Payloads in the JNDI-Exploit-Kit. This attack path works in *ANY* java version as long the classes used in the Serialized payload are in the application classpath. Do not rely on your java version being up-to-date and update your log4j ASAP!
Interesting Log4j payload I discovered, simply omit the closing brace }, and now you will potentially get a bunch of data exfiltrated to your server until the next } appears in that data. Had it work on a FANG target...
#log4j has resulted in many Linux system breaches. The Linux forensics cheatsheet below can find many of the artifacts post-compromise. If you want to automate all of this, you can get a free license of @SandflySecurity on our website.
You want to see what LD_PRELOAD is set to?
"grep -l LD_PRELOAD /proc/[0-9]*/environ | while read file; do echo $file:; cat $file | tr \\000 \\n | grep LD_PRELOAD; echo; done"
Haven't yet been seeing this with #log4j but be aware that LD_PRELOAD rootkits are circulating in the wild. Use of LD_PRELOAD is uncommon, so spot suspicious processes with "grep -l LD_PRELOAD /proc/[0-9]*/environ"
Or just try:
"ls -l /proc/[0-9]*/exe 2>/dev/null | awk '/ -> / {print $NF}' | sort"
Shows all EXE paths in sorted order making it easier to spot outliers #log4j
Another fun Linux command line:
"sudo ls -l /proc/[0-9]*/exe 2>/dev/null | awk '/ -> / && !/\/usr\/(lib(exec)?|s?bin)\// {print $9, $10, $11}' | sed 's,/proc/\([0-9]*\)/exe,\1,'"
Display PIDs with non-standard EXE paths