[Pin] My maldev link dump if anyone else wants to read :D (Will be updated)

@thoughtfault cobalt gave me a stroke the other day

@AshDevMan There are a few winapis used, but basically u open a handle to the device context of the screen, create your own one, then just copy it over. The winapi that does that "copying" is BitBlt

Ok ive tracked the issue down to using namespace Gdiplus; does cobalts bof loader not play nice with namespaces(?)

@deezrycy damn unlucky

@anthemtotheego @0xBoku @BinaryFaultline oh my god its the same guy who added a builtin BMP renderer via aggressor to my screenshotbof .cna what a chad

@C5pider omg thx

@modexpblog I think ive considered GDI before, didnt know about WIC. Will go take a look

Hotfix: It now supports cobalt strike 4.9 and below! Had to dynamically resolve the winapis due to the DFR cap of 32 in CS4.9 huge thx to the friend who figured out and fixed that weird C++ scoping issue. i would not have found that one on my own 💀

@SHP10_95 After learning the basics I mostly read blogposts and other offensive research. Links: Then of course theres more specialized content depending on what you wanna learn i mostly just mess around and have fun lol

@kabinet01

RT @LRQA_Cyber_Labs: 🦝 Introducing Raccoon - a C# tool developed by LRQA's @eks_perience for extending the screenshot functionality of Comm…

@LRQA_Cyber_Labs @eks_perience i did something similar before in C when making my WindowSpy BOF. Mine saved as raw BMP because i was too lazy to do the image compression and stuff in a BOF. Might go clean that one up and BOF it when im free lol

@checkymander @0xSkeletonKey

RT @rad9800: I have uploaded the recording to YouTube of the Conti Source Code analysis, exploring the encryptor code base. We cover vario…