med0x2e/ExecuteAssembly
Load/Inject .NET assemblies by; reusing the host (spawnto) process loaded CLR AppDomainManager, Stomping Loader/.NET assembly PE DOS headers, Unlinking .NET related modules, bypassing ETW+AMSI, avoiding EDR hooks via NT static syscalls (x64) and hiding imports by dynamically resolving APIs (hash).
Join the conversation
Reviews · Questions · Posts
Share what you know about ExecuteAssembly — write a review from your real experience, ask an implementation question, or publish a post about how you use it.
Share your experience
Write or update your review
Explain what worked, what broke down, and what another team should know before adopting ExecuteAssembly.
Project Q&A
Questions and answers
Browse implementation threads tied directly to med0x2e/ExecuteAssembly. Each question links through to the full answer page.
Be the first to ask how teams run ExecuteAssembly in production. Every question you post becomes a durable, searchable answer page other developers can find.
Ask the first questionRelated posts
Posts tagged with the same topics
These posts come from the same topic surface as this repo, so readers can move from project evaluation into practical writeups and migration notes without leaving context.
Share how your team uses ExecuteAssembly — a migration note, an architecture writeup, or a comparison. Your post reaches everyone browsing these same topics.
Write the first post