Questionunclosable application?

Posts 16–21 of 21 · Page 2 of 2
Or, create a separate application that checks for the original apps process, if it detects it, ermm, do nothing/kill shit that kills it, then if it doesn't detect it the original app i restarts it?
code a driver that hooks ZwTerminateProcess?
What this will do is it will set your process as a critical process, making it unkillable. However because .NET programs are run as user what, on kill it will result with a BSoD. When run as system it cannot be killed.

Code:
<DllImport("ntdll.dll", SetLastError:=True)> _
    Private Sub RtlSetProcessIsCritical(v1 As UInt32, v2 As UInt32, v3 As UInt32)
    End Sub

    Public Sub BulletProof()
        Process.EnterDebugMode()
        RtlSetProcessIsCritical(1, 0, 0)
    End Sub

    Public Sub Killable()
        RtlSetProcessIsCritical(0, 0, 0)
    End Sub
Quote Originally Posted by Matroix73 View Post
What this will do is it will set your process as a critical process, making it unkillable. However because .NET programs are run as user what, on kill it will result with a BSoD. When run as system it cannot be killed.

Code:
<DllImport("ntdll.dll", SetLastError:=True)> _
    Private Sub RtlSetProcessIsCritical(v1 As UInt32, v2 As UInt32, v3 As UInt32)
    End Sub

    Public Sub BulletProof()
        Process.EnterDebugMode()
        RtlSetProcessIsCritical(1, 0, 0)
    End Sub

    Public Sub Killable()
        RtlSetProcessIsCritical(0, 0, 0)
    End Sub
Never, ever use RtlSetProcessIsCritical. This doesn't make the process "unkillable", it just means that if you DO kill the process, you will BSoD.
I wonder if there really is a way to do this
visual basic.net l33t virus maker in teh house
Posts 16–21 of 21 · Page 2 of 2

Post a Reply

Similar Threads

Tags for this Thread

None

Talk with us