+- Hack Forums (https://hackforums.net)
+-- Forum: Hacks, Exploits, and Various Discussions (https://hackforums.net/forumdisplay.php?fid=45)
+--- Forum: Blackhat • Red Team • Offensive Security (https://hackforums.net/forumdisplay.php?fid=447)
+---- Forum: Cryptography, Encryption, and Decryption (https://hackforums.net/forumdisplay.php?fid=126)
+---- Thread: How to avoid runtime detection when adding startup key to registry? (/showthread.php?tid=6149283)
How to avoid runtime detection when adding startup key to registry? - alexislinwood - Apr 14, 2021
My crypter is FUD scantime but AVs like Kaspersky detect it when you run payload and as soon as it creates a registry key for startup persistence.
How do you achieve startup persistence without runtime detections?
RE: How to avoid runtime detection when adding startup key to registry? - Edge of Nowhere - Apr 14, 2021
Typically you don't use methods that are commonly used. If it's easily Google-able, then it's most likely on Kaspersky's watch list.
RE: How to avoid runtime detection when adding startup key to registry? - pro_fesnoob - Apr 16, 2021
u could bind your software to a startup one or search for auto execute regkeys and stuff like this
RE: How to avoid runtime detection when adding startup key to registry? - Treppy. - Apr 22, 2021
Try to add it as .lnk somehow. It will help
RE: How to avoid runtime detection when adding startup key to registry? - 【ＢＡＤＭＡＮ】 - Apr 24, 2021
You have to check if the key already exist.
RE: How to avoid runtime detection when adding startup key to registry? - Cyber Crypter - Apr 26, 2021
Try encrypting regedit paths. You can use ASCII.