Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🤖 Automated Content Update
This PR was automatically generated by the HackTricks News Bot based on a technical blog post.
📝 Source Information
🎯 Content Summary
What it is: Crystal Kit is an experimental red-team toolkit intended to replace Cobalt Strike’s Sleepmask/BeaconGate by moving runtime evasion into the target module via IAT hooking with Position-Independent Code (PIC). Repo: Crystal-Kit.
Why it’s needed: Sleepmask/BeaconGate both mask Beacon’s memory and proxy a limited set of Win32 APIs for Beacon/BOFs, enabling evasion techniqu...
🔧 Technical Details
IAT hooking to wrap arbitrary imports: Inject a PIC blob and patch a DLL’s IAT so targeted imported functions (e.g.,
CreateProcessA,LoadLibrary) resolve to attacker-controlled PIC. The PIC can perform evasion (mask/unmask memory, manipulate control flow) and then tail-call the real API.Call-stack spoofing via PIC: Use a Draugr-style PIC stub to construct a benign call stack before invoking the intended API, frustrating call-stack analysis detections that expect canonical call paths from Beacon/BOFs.
Memory mask/unmask around sensitive APIs: As shown by Crystal Palace’s simplehook, temporarily obfuscate key memory regions before an API call and restore them after, reducing scan visibility during the critical window.
Extending evasion to post-ex DLLs: Hook
LoadLibraryin post-ex DLLs to intercept module loads and blunt detections tied to specific imag...🤖 Agent Actions
I analyzed the Crystal Kit blog and the HackTricks repository, and I didn’t find existing coverage of IAT hooking with PIC to wrap arbitrary imports for call-stack spoofing across Beacon, BOFs, and post-ex DLLs. The closest content was generic function hook bypassing/syscalls and a specific LdrLoadDll hook for AMSI, but no end-to-end technique for IAT hooking during load, PIC call-stack spoofing, or extending to post-ex DLLs via LoadLibrary hooks.
What I updated
Why here
Changes made
No new files were created since this fit naturally into Windows AV/EDR evasion.
This PR was automatically created by the HackTricks Feed Bot. Please review the changes carefully before merging.