https://github.com/oldkingcone/BYOSI

Evade EDR's the simple way, by not touching any of the API's they hook.
https://github.com/oldkingcone/BYOSI

edr-bypass edr-evasion php powershell redteam

Last synced: 2 months ago
JSON representation

Evade EDR's the simple way, by not touching any of the API's they hook.

• Host: GitHub
• URL: https://github.com/oldkingcone/BYOSI
• Owner: oldkingcone
• License: mit
• Created: 2024-04-28T14:37:22.000Z (6 months ago)
• Default Branch: main
• Last Pushed: 2024-08-05T16:47:06.000Z (3 months ago)
• Last Synced: 2024-08-05T19:13:20.222Z (3 months ago)
• Topics: edr-bypass, edr-evasion, php, powershell, redteam
• Language: PHP
• Homepage:
• Size: 33.2 KB
• Stars: 5
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

• awesome-edr-bypass - BYOSI: Bypass EDR by bringing your own script interpreter

README

        
# BYOSI

Evade EDR's the simple way, by not touching any of the API's they hook.

## Theory

I've noticed that most EDRs fail to scan scripting files, treating them merely as text files. While this might be unfortunate for them, it's an opportunity for us to profit.

Flashy methods like residing in memory or thread injection are heavily monitored. Without a binary signed by a valid Certificate Authority, execution is nearly impossible.

Enter BYOSI (Bring Your Own Scripting Interpreter). Every scripting interpreter is signed by its creator, with each certificate being valid. Testing in a live environment revealed surprising results: a highly signatured PHP script from this repository not only ran on systems monitored by CrowdStrike and Trellix but also established an external connection without triggering any EDR detections. EDRs typically overlook script files, focusing instead on binaries for implant delivery. They're configured to detect high entropy or suspicious sections in binaries, not simple scripts.

This attack method capitalizes on that oversight for significant profit. The PowerShell script's steps mirror what a developer might do when first entering an environment. Remarkably, just four lines of PowerShell code completely evade EDR detection, with Defender/AMSI also blind to it. Adding to the effectiveness, GitHub serves as a trusted deployer.

## What this script does

The PowerShell script achieves EDR/AV evasion through four simple steps (technically 3):

    1.) It fetches the PHP archive for Windows and extracts it into a new directory named 'php' within 'C:\Temp'.

    2.) The script then proceeds to acquire the implant PHP script or shell, saving it in the same 'C:\Temp\php' directory.

    3.) Following this, it executes the implant or shell, utilizing the whitelisted PHP binary (which exempts the binary from most restrictions in place that would prevent the binary from running to begin with.)

With these actions completed, congratulations: you now have an active shell on a Crowdstrike-monitored system. What's particularly amusing is that, if my memory serves me correctly, Sentinel One is unable to scan PHP file types. So, feel free to let your imagination run wild.

## Disclaimer.

I am in no way responsible for the misuse of this. This issue is a major blind spot in EDR protection, i am only bringing it to everyones attention.

## Thanks Section

A big thanks to @im4x5yn74x for affectionately giving it the name BYOSI, and helping with the env to test in bringing this attack method to life.

## Edit

It appears as though MS Defender is now flagging the PHP script as malicious, but still fully allowing the Powershell script full execution. so, modify the PHP script.

## Edit

hello sentinel one :) might want to make sure that you are making links not embed.