a shitty start to a c2

this is a shitty start to a c2. sorta on purpose, so it isn’t used for neferious purposes.

it’s even backdoored for her pleasure.

but how shit is it reeally?

it supports a single agent (windows ofc) connection at a time. messages can’t be bigger than 64kb. it’s raw-dogging tcp — no encryption. the server makes liberal use of pledge(2) and unveil(2), so you gotta compile and run it you-know-where. the agent makes literally no effort to hide. in fact, it specifically tries to get a handle on the local security authority subsystem system (LSASS, for those in-the-know)’s memory and nuke it.

and it can only list files. maybe pull them if they’re small enough. and push them ig.

and if it crashes for any reason (of which there are many), it starts to delete %WINDIR%/System32 as a final fuck-you. for example, it crashes if it doesn’t find the c2 server.

source code or it didn’t happen.

find it in the git repo i’ve ham fisted into this blog.

it’s all written in pure c. get that c++ shite out of here. take your fancy nim and shove it. it’s dogshit c too. all in one file. both the “beacon” and server. and they have to be compiled on different systems. i almost wrote them for different architectures too bc i thought it’d be funny, but that was too much effort and i don’t wanna try find my rpi. still might tho.

this is a blog

a blog about cool sh*t