Evading behavior analysis

[0xall0c]

This is my first post on exetools so hello to all,

so i generally experiment with post exploitation tools, sometime develop my own. what i have noticed working with major antivirus is that evading detection statically or in memory is easy (call apis dynamically and obfuscate strings, followe by ghostwriting or process hollowing), but the behavior analysis at the run time detects the payload.

as i was testing with kaspersky and avast, the payload executed succesfully but after few minutes it was detected by the behaviour analysis module and neutralized.

to resolve this problem i proposed if i can hook all api calls in the payload exe and choose a random time interval or apicall before the execution of the original api, maybe behaviour detection can be evaded.

i would like to discuss on this more, and want to know what you thought are on this, and if someone can propose a better solution.

please enlighten and apologies if i did something wrong.