About anti-SoftICE tricks

<TABLE width=500>
/ S2 `* J; V+ |6 Z. U  z* _<TBODY>
& n4 M( G2 s0 l) f<TR>
<TD><PRE>Method 01
=========

This method of detection of SoftICE (as well as the following one) is
/ g2 C) ~5 ~- B# ~( T+ ]2 n$ T, w. aused by the majority of packers/encryptors found on Internet.
' ~: w8 j" e9 ~5 eIt seeks the signature of BoundsChecker in SoftICE

    mov     ebp, 04243484Bh        ; 'BCHK'
    mov     ax, 04h
: y/ ?% N& d! m+ c  @0 a    int     3      
    cmp     al,4
    jnz     SoftICE_Detected

___________________________________________________________________________

; ~( o7 H0 G5 ~1 M. v; jMethod 02
=========
8 O% ]/ x1 a- j# W+ w
Still a method very much used (perhaps the most frequent one).  It is used
, n1 b: f; G+ _7 j/ e* Ito get SoftICE 'Back Door commands' which gives infos on Breakpoints,
5 R4 h: v  \5 v8 gor execute SoftICE commands...
It is also used to crash SoftICE and to force it to execute any commands
/ m+ L. B1 [2 z3 l6 ^; L(HBOOT...) :-((  
2 p$ H" }$ p4 d3 q7 I/ c; E2 ?, e
+ C9 B! U& n0 zHere is a quick description:
-AX = 0910h   (Display string in SIce windows)
-AX = 0911h   (Execute SIce commands -command is displayed is ds:dx)
( V, W; P9 x1 L* M& r8 f8 j-AX = 0912h   (Get breakpoint infos)
  s' ^4 ^) k  _8 e-AX = 0913h   (Set Sice breakpoints)
-AX = 0914h   (Remove SIce breakoints)

, I! f7 u" J6 B$ aEach time you'll meet this trick, you'll see:
, u& j6 t( _8 F' M! G7 }0 V; B-SI = 4647h
-DI = 4A4Dh
Which are the 'magic values' used by SoftIce.
* W) ]% Z! R5 J2 d" m* CFor more informations, see "Ralf Brown Interrupt list" chapter int 03h.

Here is one example from the file "Haspinst.exe" which is the dongle HASP
Envelope utility use to protect DOS applications:


4C19:0095   MOV    AX,0911  ; execute command.
4C19:0098   MOV    DX,[BX]  ; ds:dx point to the command (see below).
+ V; j) Z9 k. V* s: A3 X/ U4 e# B4C19:009A   MOV    SI,4647  ; 1st magic value.
4C19:009D   MOV    DI,4A4D  ; 2nd magic value.
4C19:00A0   INT    3        ; Int call.(if SIce is not loaded, jmp to 00AD*)
& G' E! @' O2 {* r& A9 V. o4C19:00A1   ADD    BX,02    ; BX+2 to point to next command to execute
1 }, b3 L2 c: l0 I  f* x, X" L( w4C19:00A4   INC    CX
4C19:00A5   CMP    CX,06    ; Repeat 6 times  to execute
4C19:00A8   JB     0095     ; 6 different commands.
1 K/ }# s. k0 u- V4C19:00AA   JMP    0002     ; Bad_Guy jmp back.
# u" |+ W( \0 C( u4C19:00AD   MOV    BX,SP    ; Good_Guy go ahead :)
( A0 }/ C6 H& F' |4 C9 [
The program will execute 6 different SIce commands located at ds:dx, which
+ p! v) X. e- G. Ware: LDT, IDT, GDT, TSS, RS, and ...HBOOT.
6 J* @* r' B  C% P7 Y* P: Y
* the "jmp to 00ADh" is performed via an SEH if the debugger is not loaded.
; M9 q, O3 s# \6 h4 ]8 ]___________________________________________________________________________

& U# O5 m6 P+ h& M$ {9 X) R4 i
) u$ [+ v- j# y" e' R& P! o5 j$ BMethod 03
$ Z; ?' H: u6 g& F=========

Less used method.  It seeks the ID of SoftICE VxD via the int 2Fh/1684h
(API Get entry point)
+ c5 _  F4 T- }9 n; `; E) s- T+ E: a        

    xor     di,di
7 R) c6 [6 |1 I. h% K  e5 T9 P    mov     es,di
% P) ^1 }) z& a- p& x; a    mov     ax, 1684h      
( a  j1 _/ R% J1 Y& \8 p    mov     bx, 0202h       ; VxD ID of winice
    int     2Fh
7 V: G( E+ `# u7 g1 k    mov     ax, es          ; ES:DI -&gt; VxD API entry point
: u! ]9 R+ O/ r& U4 s: B/ V2 Q    add     ax, di
8 i+ y6 t9 H- b3 l0 t& x- d    test    ax,ax
6 Y- {( k8 f& N    jnz     SoftICE_Detected
# ~* ]* V% {- A) X. D
___________________________________________________________________________
) J' y2 E+ ]" o* T, j, M
Method 04
- b5 J( W  N/ u! c2 W=========

' l' K8 Y5 ?- M" hMethod identical to the preceding one except that it seeks the ID of SoftICE
2 e5 t7 x+ W1 a7 V* |$ s% {GFX VxD.

( p; R2 @: w# D    xor     di,di
    mov     es,di
+ @: H1 C. {" H+ O    mov     ax, 1684h      
0 Z# {, H6 N1 H; T/ p) z; O    mov     bx, 7a5Fh       ; VxD ID of SIWVID
    int     2fh
    mov     ax, es          ; ES:DI -&gt; VxD API entry point
7 A2 g. i. [6 s9 \7 c5 e    add     ax, di
    test    ax,ax
9 v) f) o+ i5 r0 l. g    jnz     SoftICE_Detected
) A3 Q/ B6 z1 k0 L! z8 E, S  i' Z
__________________________________________________________________________

2 F0 Z# D/ U9 ~8 \
Method 05
6 O% }$ z3 F; \, j1 Z4 s: K=========

Method seeking the 'magic number' 0F386h returned (in ax) by all system
debugger. It calls the int 41h, function 4Fh.
There are several alternatives.  

, I8 }" q6 }' t+ {- HThe following one is the simplest:

7 L7 d1 T# P2 b6 }- |" N    mov     ax,4fh
    int     41h
: X2 f9 |" s  ?1 w, [# o) t) H    cmp     ax, 0F386
    jz      SoftICE_detected


4 M! J. F1 @9 F( N" y! `5 NNext method as well as the following one are 2 examples from Stone's
& p' s' M6 [- Q0 |+ ]"stn-wid.zip" (www.cracking.net):

6 ?- J+ d' ]; }+ F3 ]    mov     bx, cs
    lea     dx, int41handler2
    xchg    dx, es:[41h*4]
    xchg    bx, es:[41h*4+2]
    mov     ax,4fh
    int     41h
& H8 k: n' O, e    xchg    dx, es:[41h*4]
    xchg    bx, es:[41h*4+2]
: q/ A+ ~" {1 V9 G0 b) M% L: L    cmp     ax, 0f386h
    jz      SoftICE_detected

int41handler2 PROC
2 s" {- m# m0 d    iret
int41handler2 ENDP


_________________________________________________________________________

1 w5 d4 P. j- X' V# l) d8 A3 R) \* h
Method 06
' S8 a1 g1 _. ?" X2 k; y9 B=========
7 e% ^7 ^: Y# m+ K% ~, a
4 N2 `6 Q$ S8 P' m7 K
2nd method similar to the preceding one but more difficult to detect:

5 v% u% ]- \6 h' ~& y: i
int41handler PROC
+ J  q8 x6 k4 m; n" H  K( J    mov     cl,al
: R+ \5 e0 g+ u3 H    iret
- x' y2 S, O! f5 u# q- nint41handler ENDP
$ Z3 h) ^! P9 q6 a- E4 z" H' O
1 d2 J. N" h2 q) L* ~$ v# n/ H3 }
- ~. K" ?$ v" P: ^    xor     ax,ax
    mov     es,ax
    mov     bx, cs
' v* {) x. B6 B2 h2 m! o- U; h    lea     dx, int41handler
) E& w+ O0 q8 `    xchg    dx, es:[41h*4]
    xchg    bx, es:[41h*4+2]
0 s7 ~% B; ?$ j- t: k8 R7 a    in      al, 40h
    xor     cx,cx
    int     41h
' M1 u5 p5 ^& s  \    xchg    dx, es:[41h*4]
    xchg    bx, es:[41h*4+2]
6 C: G: f; t% p' n- v    cmp     cl,al
    jnz     SoftICE_detected

_________________________________________________________________________
* u, o* f9 F4 G# r& P) z
  R* a( v# o) t4 L( K2 LMethod 07
=========
9 M  K/ w8 j, G. t. D# j7 z
Method of detection of the WinICE handler in the int68h (V86)
) S4 q# }+ k6 S- z3 g
0 J  X, q' W* Q. s9 d* y    mov     ah,43h
2 i) j, L3 ?8 _7 [7 V1 J4 l  L    int     68h
    cmp     ax,0F386h
    jz      SoftICE_Detected
- x( I0 t# P: r  l2 `- U
4 V1 T/ s& e+ R$ p
=&gt; it is not possible to set a BPINT 68 with softice but you can hook a 32Bit
   app like this:

5 D# @8 M+ l3 v5 L   BPX exec_int if ax==68
7 P5 _4 Y% s6 Q& G3 @; V0 P   (function called is located at byte ptr [ebp+1Dh] and client eip is
* s# Q- T, S8 f* N9 G- j& _6 t" c, g   located at [ebp+48h] for 32Bit apps)
__________________________________________________________________________
/ M$ }' D, T5 W$ I3 s3 i% Y  ]5 B
" g/ s( R# g; F. q/ h" ~
Method 08
=========

/ s0 H4 G" [1 `7 ~It is not a method of detection of SoftICE but a possibility to crash the
system by intercepting int 01h and int 03h and redirecting them to another
routine.
It calls int 21h functions 25h and 35h (set/get int vector) and ds:dx points
to the new routine to execute (hangs computer...)
2 H+ h# k6 ]7 E) H
0 p' M( @5 ?+ L8 W# R3 ?    mov     ah, 25h
    mov     al, Int_Number (01h or 03h)
    mov     dx, offset New_Int_Routine
    int     21h

__________________________________________________________________________
/ I+ j, q8 y# \
) |) v  f( h- D, s: @0 rMethod 09
=========

This method is closed to methods 03 and 04 (int 2Fh/1684h) but it is only
* T) \: k+ S* m+ \2 tperformed in ring0 (VxD or a ring3 app using the VxdCall).
The Get_DDB service is used to determine whether or not a VxD is installed
for the specified device and returns a Device Description Block (in ecx) for
that device if it is installed.
% L# I9 a8 n* d/ v+ n
) b6 C" l7 V; w" V& n0 ?0 Y   mov     eax, Device_ID   ; 202h for SICE or 7a5Fh for SIWVID VxD ID
% Z$ v4 |, [4 Q) Q% k   mov     edi, Device_Name ; only used if no VxD ID (useless in our case ;-)
8 l& E- a% ]; g7 q2 A   VMMCall Get_DDB
) D; B! f# y: M1 i+ k  V2 o   mov     [DDB], ecx       ; ecx=DDB or 0 if the VxD is not installed
% u% y/ u" t; x- k9 U: V
+ B7 s( _5 U1 i* U* k* w! ZNote as well that you can easily detect this method with SoftICE:
8 N% U/ U) z3 g- i- ~   bpx Get_DDB if ax==0202 || ax==7a5fh
+ c2 h2 V& a0 b  B' m
__________________________________________________________________________

Method 10
* Z( r! v, D8 \0 g' V0 \7 R=========

0 ]: O) l+ ]4 ~+ o=&gt;Disable or clear breakpoints before using this feature. DO NOT trace with
  SoftICE while the option is enable!!
0 ^1 M$ o+ }0 S. a' ^
& c  h3 U8 f  U5 O. X6 D; IThis trick is very efficient:
4 Z' W) ?; G6 F$ T. \3 Xby checking the Debug Registers, you can detect if SoftICE is loaded
(dr7=0x700 if you loaded the soft with SoftICE loader, 0x400 otherwise) or if
there are some memory breakpoints set (dr0 to dr3) simply by reading their
* R2 x- }" }) P* b$ {* Cvalue (in ring0 only). Values can be manipulated and or changed as well
(clearing BPMs for instance)

' g3 g% M% I2 G0 ?$ r__________________________________________________________________________
- ?4 t. u/ a9 @$ J4 w. k* S( K+ x; T/ R9 N
Method 11
=========
8 H3 s! O, o9 J
0 K+ I7 s  J, G6 _- y/ E  nThis method is most known as 'MeltICE' because it has been freely distributed
via www.winfiles.com. However it was first used by NuMega people to allow
Symbol Loader to check if SoftICE was active or not (the code is located
! H( a$ ^7 W5 M: F' f% x) y7 _' Tinside nmtrans.dll).

The way it works is very simple:
6 n% w3 ?4 T. [& ?It tries to open SoftICE drivers handles (SICE, SIWVID for Win9x, NTICE for
WinNT) with the CreateFileA API.

Here is a sample (checking for 'SICE'):

BOOL IsSoftIce95Loaded()
2 S" ~4 Z- c7 j{
   HANDLE hFile;  
   hFile = CreateFile( "\\\\.\\SICE", GENERIC_READ | GENERIC_WRITE,
                      FILE_SHARE_READ | FILE_SHARE_WRITE,
3 F' u4 g: y+ h3 ^                      NULL, OPEN_EXISTING, FILE_ATTRIBUTE_NORMAL, NULL);
   if( hFile != INVALID_HANDLE_VALUE )
! B% x1 s* L0 C5 H! {   {
      CloseHandle(hFile);
2 \% h9 K$ v! @' b      return TRUE;
   }
) O7 }; s8 J& k/ n   return FALSE;
}
- d& I7 K6 ]$ Q, y
Although this trick calls the CreateFileA function, don't even expect to be
able to intercept it by installing a IFS hook: it will not work, no way!
1 p# i/ m  k3 D- D% c: K5 |In fact, after the call to CreateFileA it will get through VWIN32 0x001F
service _VWIN32_ReleaseWin32Mutex (via Kernel32!ORD_0001/VxDCall function)
and then browse the DDB list until it find the VxD and its DDB_Control_Proc
field.
% d* c/ r4 w; S8 |2 X4 k" n. BIn fact, its purpose is not to load/unload VxDs but only to send a
W32_DEVICEIOCONTROL (0x23) control message (DIOC_OPEN and DIOC_CLOSEHANDLE)
' P- b# M3 c1 [0 T: ~to the VxD Control_Dispatch proc (how the hell a shareware soft could try
to load/unload a non-dynamically loadable driver such as SoftICE ;-).
If the VxD is loaded, it will always clear eax and the Carry flag to allow
1 O: e  Y' p; h0 jits handle to be opened and then, will be detected.
0 E& U: A1 {: A+ n, yYou can check that simply by hooking Winice.exe control proc entry point
while running MeltICE.

8 }" G  p0 ]9 I5 P( [. Z" S1 y5 e
2 v* e9 g( P: {+ @  00401067:  push      00402025    ; \\.\SICE
" u( A# c; }0 y  0040106C:  call      CreateFileA
* p" H" h1 s1 c' E- ^  00401071:  cmp       eax,-001
0 o! a( j, M8 u  00401074:  je        00401091
, E: V* r" U6 K& L) t& \: G8 x
0 S7 f8 Y+ m( ]0 `2 r3 j
There could be hundreds of BPX you could use to detect this trick.
-The most classical one is:
  BPX CreateFileA if *(esp-&gt;4+4)=='SICE' || *(esp-&gt;4+4)=='SIWV' ||
    *(esp-&gt;4+4)=='NTIC'

-The most exotic ones (could be very slooooow :-(
6 b6 |- u) L1 S3 n5 q3 V   BPINT 30 if eax==002A001F &amp;&amp; (*edi=='SICE' || *edi=='SIWV')  
     ;will break 3 times :-(

-or (a bit) faster:
0 K0 X: ^6 M6 q   BPINT 30 if (*edi=='SICE' || *edi=='SIWV')
7 m- X; I2 W4 e* s
& y. K/ Y8 v( s/ D4 X/ A- K   BPX KERNEL32!ORD_0001 if *edi=='SICE' || *edi=='SIWV'  
     ;will break 3 times :-(
" E5 I! ?  t" u& @% x
* a5 |% _- ^+ J  B-Much faster:
   BPX VMM_GetDDBList if eax-&gt;3=='SICE' || eax-&gt;3=='SIWV'

Note also that some programs (like AZPR3.00) use de old 16-bit _lopen
6 \- n8 i; V4 a- Y9 I' D6 L2 O$ Nfunction to do the same job:

   push    00                        ; OF_READ
   mov     eax,[00656634]            ; '\\.\SICE',0
   push    eax
   call    KERNEL32!_lopen
3 `: G' l. J% Z( o/ K5 d   inc     eax
7 S& @3 I4 i  S  Z% e3 s1 I   jnz     00650589                  ; detected
% L8 Q' L) ^, Y6 z   push    00                        ; OF_READ
7 `2 \, p' i1 b5 e$ l9 k   mov     eax,[00656638]            ; '\\.\SICE'
' t7 \% Z, A9 a6 i9 x( w0 |   push    eax
; s+ v0 d, \; s% c; Z7 t2 e0 @   call    KERNEL32!_lopen
   inc     eax
   jz      006505ae                  ; not detected


" g: v9 H8 g: W% ]7 W__________________________________________________________________________

- n+ z1 }. j# M$ {- b; UMethod 12
=========
9 r* D) c; l$ b; D( Z8 [
This trick is similar to int41h/4fh Debugger installation check (code 05
$ ]' y' k* |( e7 I, h: l&amp; 06) but very limited because it's only available for Win95/98 (not NT)
as it uses the VxDCall backdoor. This detection was found in Bleem Demo.

   push  0000004fh         ; function 4fh
: N  z4 v# C+ C1 n   push  002a002ah         ; high word specifies which VxD (VWIN32)
' ~5 V# c, g/ y! g4 F1 @                           ; low word specifies which service
: G* c6 T% P8 a3 E' F9 R                             (VWIN32_Int41Dispatch)
   call  Kernel32!ORD_001  ; VxdCall
6 P- m1 y9 o5 v; Y* G1 c# N) O   cmp   ax, 0f386h        ; magic number returned by system debuggers
, {& C( M+ z) W+ A: q  a   jz    SoftICE_detected
7 u* _5 \7 k. d: z/ M; Z$ R9 D/ M2 o
8 D8 ]- [( v8 Z0 hHere again, several ways to detect it:

    BPINT 41 if ax==4f
( Z! b8 {7 p9 V+ j8 X  t: R
    BPINT 30 if ax==0xF386   ; SoftICE must be loaded for this one

    BPX Exec_PM_Int if eax==41 &amp;&amp; edx-&gt;1c==4f &amp;&amp; edx-&gt;10==002A002A

: K* h: F4 U# `5 [/ L2 ^4 _    BPX Kernel32!ord_0001 if esp-&gt;4==002A002A &amp;&amp; esp-&gt;8==4f   ; slooooow!

__________________________________________________________________________
7 G8 L' b( S; t
' f' B0 G# S' b" ~, q: p# z5 fMethod 13
=========
3 I- M1 ]4 {3 j2 ^: O# }
1 Y1 A5 S# u! ?# p( K: pNot a real method of detection, but a good way to know if SoftICE is
- d' x2 n. ^7 X# {# yinstalled on a computer and to locate its installation directory.
; E& {0 I+ P  X* }7 G# ~) J3 g6 DIt is used by few softs which access the following registry keys (usually #2) :
, }% e5 G  W: {
-#1: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion
' t/ Y) W! {  g' ?\Uninstall\SoftICE
9 b& `0 {* e) O* k; A-#2: HKEY_LOCAL_MACHINE\Software\NuMega\SoftICE
; p7 i& `, R/ n-#3: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion
: m9 K' r9 X* s\App Paths\Loader32.Exe

4 \7 m' K6 m% Z0 R) Q
2 r9 \  S7 a0 C( E- ^Note that some nasty apps could then erase all files from SoftICE directory
(I faced that once :-(

7 h4 h+ t' ]4 L- O; \7 r7 G0 IUseful breakpoint to detect it:
2 U+ P7 ?& L  a! V- k8 E/ T
# m, q, M  X/ F! v" a- V7 P8 b     BPX _regopenkey if *(esp-&gt;8+0x13)=='tICE' || *(esp-&gt;8+0x37)=='tICE'

5 b* N9 T# O" q1 N3 I__________________________________________________________________________
3 t( K8 ?5 d. p" N# ~

Method 14
=========

0 i* u" o% U- k5 h0 D% MA call to VMM 'Test_Debug_Installed' service. As the name says, its purpose
  b- L, d; E" xis to determines whether a debugger is running on your system (ring0 only).
# O- y2 W9 K. L
   VMMCall Test_Debug_Installed
2 U& O; o: H3 {9 K* j- S$ N0 h" R   je      not_installed
+ P! K7 I/ H9 U6 K! @( O& E
  C, H$ I; E' h- n$ X" _This service just checks a flag.
</PRE></TD></TR></TBODY></TABLE>