Windows Kernel Dev

€250-750 EUR

Posted half a minute ago

•

Ends in 6 days

€250-750 EUR

Paid on delivery

I need an experienced Windows systems developer to build a driver + user-mode client pair that reads a live 64-bit target process without being visible to a second, inspection-focused driver running on the same machine. The target is a third-party application I don't control and that updates regularly. The interesting work is the reverse engineering (locating structures, offsets, pointer chains) and the memory layer (manual translation, no attach). If your day job is C++, IDA/x64dbg, and WinDbg, this is aimed at you. Scope Static and dynamic analysis of the target to recover structures, offsets, and pointer chains Signature-scanning layer so recovered offsets survive target updates instead of being hardcoded Kernel driver with a read/write primitive built on manual virtual-to-physical translation User-mode client: attach/detach, scan engine, config, output layer IOCTL or shared-memory channel with real error handling and no bad-input BSODs Signing guidance, load/unload without reboot, documentation Technical expectations Be honest with yourself before applying — the following are the actual requirements, not aspiration. Memory layer Full 4-level walk: PML4 → PDPT → PD → PT, with correct index extraction and physical base masking PCID masking on CR3 — bits 11:0 are PCID on modern builds; the base is 51:12 PS bit handling: 2MB large pages at PDE, 1GB at PDPTE. Skip the PT level correctly, don't read it Present bit checks at every level. A clear bit means the page is paged out — a physical read returns garbage silently [login to view URL] / 5-level paging on Win11: PML5 prefix, 57-bit VA. Must not truncate [login to view URL] for DTB acquisition, not __readcr3() — KVA Shadow makes __readcr3() return the shadow CR3 with kernel mappings stripped MmCopyMemory with MM_COPY_MEMORY_PHYSICAL for table reads; MmGetPhysicalAddress for the reverse IRQL-aware read path: opportunistic fault-in at PASSIVE_LEVEL, physical-only above it. DISPATCH_LEVEL cannot fault, so a demand-paged read must degrade gracefully rather than stall Transition and prototype PTEs pointing at pagefile — handle or miss cleanly, never report garbage as data TLB invalidation discipline after any CR3 change Attachment strategy I want the read path to not attach at all. KeStackAttachProcess and MmCopyVirtualMemory are acceptable fallbacks but mutate thread APC state and are observable. Preferred design is captured-DTB plus pure physical walk — nothing for the inspection layer to see. Covertness requirements Handle layer: assume ObRegisterCallbacks strips PROCESS_VM_READ from user-mode handles. Kernel-side only Module layer: PsLoadImageNotifyRoutine, PEB->Ldr, NtQueryVirtualMemory are all in play. Hiding in a module list is expected Driver layer: PsLoadedModuleList, \Driver object directory, device and symbolic link enumeration, PiDDBCacheTable, MmLastUnloadedDriver, kernel .data pointer scans. Non-Microsoft or unsigned status is itself a signal Pool layer: PoolBigPageTable tag walking. No chea/hack/initials tags Physical layer: assume a brute scan via MmGetPhysicalMemoryRanges. Hiding only in VADs is insufficient — expect slack-space placement in a legitimately mapped image, not DKOM Integrity layer: .text hashing, inline hook detection, KiSystemCall64 byte comparison, PatchGuard on kernel structures Timing layer: QPC deltas and rdtsc pairs around the read path. A 40µs tail every frame gets noticed Hypervisor layer: assume CPUID 0x40000000 probing and that every CR3 write is a VM-exit. Per-read CR3 swapping is a signature and a perf hole — batch, cache, or avoid Channel layer: device name, symlink, IOCTL codes, pipe names are all enumerable. Randomize per build, pick a name that blends Required Strong modern C++ (C++17+) WDM or KMDF, DPCs, IRQL discipline, memory manager, PE format IDA Pro or Ghidra, x64dbg, WinDbg — real fluency, not familiarity Pattern scanning and structure reconstruction from disassembly Nice to have On-screen display layer (ImGui, DirectX hook, or external draw) Existing driver codebase to adapt Hypervisor-adjacent experience

Project ID: 40821071

About the project

Open for bidding

Remote project

Active 57 yrs ago

Place your bid

Bid amount Email address

Benefits of bidding on Freelancer

Set your budget and timeframe

It's free to sign up and bid on jobs

内容来自 Freelancer News,版权归原作者所有。

阅读原文 ↗

把喜欢的内容,留在你的新标签页。

打开我的订阅