mirror of
https://github.com/youssefnoob003/SindriKit
synced 2026-07-07 21:57:09 +00:00
sibouzitoun
aea2eb6cfb
- Implement complete cross-process injection engine via snd_inj_ctx_t - Track explicit remote_entry_point for safe thread hijacking and PE execution - Refactor standalone syscall resolvers into a unified pipeline (scan/sort) - Perfect status code system by purging generic fallbacks in favor of highly-specific, domain-aware error codes - Fix minor pointer validation and parsing bugs in the reflective loader
SindriKit Documentation
Technical documentation mirroring the framework layout: shared infrastructure at the base, architectural patterns above it, domain techniques and API references at the leaves.
Table of Contents
Introduction & onboarding
- getting_started/ — CMake setup, DI bootstrap, first loader/injection workflow
- examples/ — PoC walkthroughs across Win32, NT, and syscall profiles
Core framework
- architecture/ — dependency injection, state machines, status tiers, implant integration
- domains/ — primitives, loaders, injection, evasion (stub)
Internal engines
- parsers/ — PE parsing and env/PEB introspection
- common/ — CRT-free helpers, buffers, hashing, status, debug
Build & QA
- config/ — hash manifest (
config/hashes.ini) - scripts/ — pre-build automation (
generate_hashes.py) - tests/ — integration test runner, PE mutator, fixtures
Documentation conventions
| Page type | Typical sections |
|---|---|
| README (folder index) | Intro → header/source map → Table of Contents → Related documentation |
| techniques.md | Concepts, OpSec trade-offs, integration patterns |
| api_reference.md | Signatures, parameters, returns, source paths |
Syscalls use pipeline.md + engines.md instead of techniques.md. Execution splits FFI and Heaven's Gate into dedicated technique pages.
Related documentation
Start here: Getting started → Basic usage → Examples OpSec table