Self-Cleaning-PICO-Loader

KO | EN

gitlite — search

#python #hacktoberfest #llm #rust #open-source #gemini #hacktoberfest2024 #hacktoberfest-accepted #database #android #typescript #javascript

Self-Cleaning-PICO-Loader

★ 57 Open GitHub ↗

Self-cleaning in-memory PICO loader for Crystal Palace. Automatically erases traces and operates entirely in memory for stealthy payload execution.

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Self-Cleaning PICO Loader for Crystal Palace

This loader demonstrates advanced in-memory self-cleaning techniques for offensive tooling. It dynamically determines its own start and end addresses in memory, enabling complete removal of the loader after execution.

## Dynamic Loader Boundaries
To obtain the base and end addresses of the injected PICO loader in memory:
- The loader is built with a small, empty file appended at the end (see `pic_end.o` in the loader spec).
- The base address is determined by using the address of the entry point function (`go`) directly through `getPicStart()`.
- The end address is determined by referencing the appended empty section through `getPicEnd()`.

## Memory Erasure Using Sleep Obfuscation Technique
With both addresses, the loader can:
- Erase and free its own memory region after payload execution.
- The sleep obfuscation technique (e.g., Ekko) is adapted here to enable complete removal of the PICO loader from process memory. Instead of obfuscating and sleeping, the technique is modified to zero and release the loader memory entirely.

## Key Steps
1. **Dynamic Address Discovery:**
   - `getPicStart()` function returns the loader's base address using the entry point function address.
   - `getPicEnd()` function returns the end address via the appended empty section.
2. **Self-Cleaning:**
   - The loader sets its memory to RW, zeroes it, and frees it using timer-based ROP gadgets.
   - No traces remain in the process memory after execution.

## Moneta Analysis: Loader Comparison

Below are two screenshots from Moneta showing the memory regions after payload execution:

### Default PICO Loader
![Default Loader](https://raw.githubusercontent.com/pard0p/Self-Cleaning-PICO-Loader/main/images/default_loader.png)
*After execution, RWX regions containing the payload remain in the process memory.*

### Self-Cleaning PICO Loader
![Self-Cleaning Loader](https://raw.githubusercontent.com/pard0p/Self-Cleaning-PICO-Loader/main/images/self_cleaning_loader.png)
*After execution, RWX regions with the payload disappear, leaving no traces, and the process continues running normally.*

This demonstrates the effectiveness of the self-cleaning technique: the loader fully erases and frees its own memory, unlike the default loader which leaves potentially detectable regions in memory.

---
## References
- Sleep obfuscation based in [Ekko technique](https://github.com/Crystallize-Ekko/Ekko)
- [Crystal Palace](https://tradecraftgarden.org/crystalpalace.html)

## Warning: Control Flow Guard (CFG)

When injecting into processes with Control Flow Guard (CFG) enabled, a bypass is required for successful execution of self-cleaning or sleep-obfuscation techniques. For details and implementation, see: https://github.com/Crypt0s/Ekko_CFG_Bypass/tree/main

Self-Cleaning-PICO-Loader

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README