-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IMEI randomisation makes IMEI looks like gibberish #32
Comments
So does our fix replace the imi gen script or add to it? |
You should add it to main script with replacing part of previous one. It is just a part of script |
Were should i replace it? I looked on ur page and it doesn look like u implemented it on ur fork |
I provided above options for testing only. But if you need full script here it is:
It is replacement for this I added LUHN check to make sure IMEI 100% valid This part:
Can be widened or fully replaced to mimic other devices using this database For example this script will mimic to smartphones using smartphones manufacturers TACs (this variant untested):
|
have your ran the two and seen your script work? its good shit if it works |
i will prepare a fork as it looks like your not git users.
|
that looks great! Thanks for the contribution. Can you help me understand your statement:
a bit better? I'm surprised that you seem to have experience an invalid checksum. How did you notice the invalid checksum? |
It seems like this is now redundant
All valid as I checked. But TACs list should be bigger a little bit |
hey guys I scraped a TAC database, and have a list of codes you can use: https://github.com/narodnik/immi/blob/master/tac_codes.csv |
Thanks a lot for the TAC database. In fact, we considered "full randomization" across all possible models at first. However, this would result in a higher likelihood of detection that the IMEI was in fact manipulated:
|
Great, I agree with what you say. However there should still be a decent selection of various popular devices to avoid correlation. |
Maybe focus on top 20 best selling phones: https://en.wikipedia.org/wiki/List_of_best-selling_mobile_phones#2022[90] |
See Table 1 on page 9 for the models we choose from: |
This is a good list. Thanks so much. Previously was using KaiOS but definitely doing to get a Mudi and run this! |
Hi
Blue merle is NOT generating valid IMEI. Most totally invalid and rejected by ISP.
The deal is your IMEIs fails check sum and have invalid TAC (in several countries).
I am not really good in GitHub so I cannot submit PR.
Fix for Python version
But this is simple code to make it look more valid:
Fix for Bash version
This will make router mimic to one of this manufacturers:
Samsung, iPhone, Sony, LG, Nokia, Huawei, Xiaomi, OnePlus
This ensures that ISP will not reject IMEI, nor shape speed because of “not mobile use”.
You can extend list of manufacturers by TACs from this database
The text was updated successfully, but these errors were encountered: