IMSI-catcher icon indicating copy to clipboard operation
IMSI-catcher copied to clipboard

IMSI not showing up

Open kernelfg opened this issue 6 years ago • 7 comments

Hi,

What could be the reason why my own IMSI is not showing up for every tests I did ? Thanks in advance

kernelfg avatar Jan 24 '18 16:01 kernelfg

I'd like to know this as well. I find a LOT of IMSI numbers, but not my own IMSI.

alexandr84 avatar Feb 01 '18 09:02 alexandr84

well same here.. unable to find my own.. do we need to process the found IMIS`s further?

imranrajjad avatar Feb 07 '18 11:02 imranrajjad

well I had Wireshark open next to the IMSI catcher script. So it appears that Message Type: Location Updating Request (0x08) , Message Type: Location Updating Accept (0x02) also carries IMSI which are not being sniffed by script

imranrajjad avatar Feb 08 '18 14:02 imranrajjad

Make sure you are on the same ARFCN as you might have 2 ARFCN as it happens where im.

One is the MS one is the BTS.

Keskebeu avatar Mar 08 '18 03:03 Keskebeu

I checked ARFCN from phone`s service settings, its the same

imranrajjad avatar Jan 21 '19 08:01 imranrajjad

Seems that this is an issue for multiple people. I've had issues also. Any news on this?

asiudoisjdfo avatar Feb 20 '20 11:02 asiudoisjdfo

According to https://harrisonsand.com/posts/imsi-catcher/ , the IMSI is only transmitted during initial connection which negotiates a Temporary Mobile Subscriber Identity (TMSI). All subsequent communications happens with the TMSI. I'm curious if this is the issue you are seeing. As this is a passive connection and not an active connection, I don't think you can force the phone to reveal its IMSI.

To test this out, try turning your phone off and on again to force it to establish a new initial connection and see if your TMSI shows up.

Does this IMSI capture tool also capture the TMSI too? If so, I'm sure the phone company can map the TMSI back to an IMSI with a valid search warrant.

brianblank avatar Mar 12 '23 21:03 brianblank