Anti-Debugging | Test for Anti-Debugging | Code Inspection library

I'm currently in the process of learning different techniques malware use to prevent debugging, and I came across an issue I can't seem to really understand. This piece of malware that I am currently trying to figure out and debug uses some kind of anti-debugging technique that doesn't allow me to attach a debugger in the first place. I have tried using things such as Scylla-hide, I've also tried manually going in and hooking common anti-debugging API calls to see what is going on, but no luck so far. I also tried with WinDbg hoping it would give me some error message I can go off of, and it gave me this: WinDbg output when trying to debug program

So this got me thinking that it was doing something to prevent a thread being started and that is what is causing any debugger from being able to attach. I also tried injecting a DLL with the typical LoadLibrary CreateRemoteThreadEx technique and seems it doesn't allow me to create a thread that way either. I've looked at as much as possible on anti-debugging and can't seem to find an answer to this. Any nudge in the right direction would be greatly appreciated.

I'm hoping to be able to circumvent this in user-mode, as I'm trying to understand what exactly it is doing to stop me from debugging rather than simply bypassing it. This is my first time asking a question so sorry if anything was hard to understand.

I am learning golang and I wanna implement a simple Linux anti-debugging method in golang. I have a CPP code which works in the same way I intended. But cannot do the same in golang. can you guys guide me how to do same in go?

Here is the C++ Code I am using as a reference.

I'm working with Android 8.1 Pixel2 XL phone. I have hooked the sys_call_table and have replaced the syscalls with my own functions using the kernel module. I want to make an application unable to quit. I'm trying to invalidate an application's sys_exit_group and sys_kill. What should I do in my own function.

I want to debug an application, but it turns on anti-debugging. So I want to hook the system call

I have tried direct return, but It wasn't work. System will call sys_kill again.But this time, I can't get the application's uid from its pid.

For several days, I have been trying to document myself about Anti-Debugger techniques.

So I found many different methods to achieve this. In these techniques, I found the possibility to hiding thread from debugger, thanks to the NtSetInformationThread method. My project is to use this method in my code written in VB.NET.

Here is a description of the technique I found in my research, which I find very well explained:

In Windows 2000, a new class of thread information transferred to the NtSetInformationThread function appeared – ThreadHideFromDebugger. This was one of the first anti-debugging techniques provided by Windows in Microsoft's search for how to prevent reverse engineering, and it's very powerful. If this flag is set for a thread, then that thread stops sending notifications about debug events

From this website

So I found a source coming from this site to achieve this. Here is the method he uses in C++:

I'm trying to understand how to implement an anti-debugging by starting with the simplest method, PT_DENY_ATTACH, and try to debug it with lldb. But I have no idea in which part of my objective-c that I need to implement it in.

I wrote a simple objective-c code for a login page.