There are ways and means to get around this, but they are vaguely effort-intensive and sufficiently annoying to not be worthwhile.
Like, what is there to gain anyway.
@sgodofsk From some experience asking the same questions at a smaller, similar facility: the designs being manufactured get revised/adjusted/iterated on far too rapidly for injection molding to be reasonably viable unless you could massively bring down the cost of making molds.
Something I am looking for since forever is a old copy of "H1N1 Loader" by Slayer616 that was published on an old forum (OpenSC, and some others). I wonder if any other VX archivist types have it? Or the Func-In RAT demos by DeadlyVermillion?
cc: @vxunderground
@0xTriboulet "if it works, it works". Trying the absolutely zero effort, stupid things right off the bat costs next to nothing and succeeds way too often.
No point in overthinking it in the early stages, and if it fails you still get some metrics probably.
the amount of wins I get with ${off the shelf C2} in stock config or minimal alteration probably outweighs the amount of wins I get where I spend a shitload of effort making something extra super duper speshul for the engagement.
If you know, you know.
just fucking have someone make a yandex or gmail or whatever free-email and start sending low effort shit out on day 1 of the engagement.
while your coworkers are busy faffing around with indirect syscalls or sleep masks or whatever, you will probably get a shell, statistically
one of my strongly held opinions in the game of "red teaming" is that you should try stupid, low effort, "an intern could do this/this will never work" shit right off the rip.
I mean.
It works all the goddamn time in the wild.
Obsession with "evasions" is brainworms.
red team protip: just repeatedly spam them barely convincing emails linking to a page that serves an executable file and you will probably land a shell in an embarrassingly large number of engagements.