@kyleavery @modexpblog The credits are definitely missing your name. I referenced a few articles for this example but your well-structured and clearly commented code is what made it work.
I have added an example for patching “Environment.Exit” to ClrOxide. You can keep the overeager to exit assemblies from crashing your processes now. 🤩 https://t.co/lZchX6MIz9
@Octoberfest73 Price is usually less of an issue than the amount of red tape. Anything less than $500 with a one time payment option and a vague invoice is easier as a one off charge than a formal process that could take months and not even get approved. Consulting in Japan 😭
@chvancooten@lpha3ch0 This is possible but awkward in rust and no guarantees for what kind of data you might end up with until trying to compile and making sense of the errors.
Nim really makes you appreciate it the farther you are away from it 😂
While I have some attention with ClrOxide, would anyone want to take a look at this and figure out why it’s not working? https://t.co/k8ayevqIQM @memN0ps @trickster012
Credits to @C5pider and @R0h1rr1m by the way, and good folks at @TrustedSec. I’ve referenced their work thoroughly, and my code is basically CoffeeLdr in rust, but it’s missing something to actually make it work 😭
Huge shout-out to @chvancooten for forcing me to start on this by allowing risky commands into NimPlant, and @_Kudaes_ and @ropnop whose dinvoke_rs and go-clr libraries helped make things finally click!
Hi everyone! I've just released ClrOxide, a rust library that allows you to host the CLR and execute dotnet binaries. 😁 Your Rust C2's can finally do execute-assembly now 😜
https://t.co/tvK6jNa4OE / https://t.co/tvj0oV2nx3
I started on this two years ago, while trying to mimic NimPlant's execute-assembly command for the v1 rust implant, had some working versions, and even tried just using Nim to do execute-assembly and pass data through FFI.