Fun one - I’ve used a PS script that has comments explaining that it’s a test script for backwards compatibility and has some random tests in it then injects shellcode into memory (just a test remember 😂).. even has author from IT in comments.. hasn’t been picked up in months.
Do some OSINT ahead of time and map key personnel and developers to the org and place the author title and contact phone number (to be you of course) / see if you ever get picked up in the future.
I’ll type paragraphs of what the functionality does and put comment code in the shellcode injection stating ugly hack but based on Microsoft’s API compatibility / it’s needed in order to test legacy systems. We even do code signing on top of it just in case.
Example: register a company (40$) rent a VPS (20$) build a website and buy a code signing cert (200$).
Call the company “Verified and Signed” or if you want to get really tailored make company similar to company name targeting and fly there for months or years.
Call the company “Verified and Signed” or if you want to get really tailored make company similar to company name targeting and fly there for months or years.
When doing PowerShell you need to make sure the code is extremely long and boring. Take a bunch of examples online to make it more believable to Google searches. Then tuck your stuff half way through or towards the end. Not the very end because most will scroll down to bottom.
Defenses: current tools are pretty worthless towards this - comes down to preventive controls - known good - and how good your analysts are.
Train them well : look for unusual behavior (c2 out to internet) and application control.
Train them well : look for unusual behavior (c2 out to internet) and application control.
