• XSS.stack #1 – первый литературный журнал от юзеров форума

(Question) About Instagram account generating

GaSXV2

RAM
Пользователь
Регистрация
01.03.2021
Сообщения
129
Реакции
35
Hi everyone,

I'm automating Instagram account creation via their web API, but hitting a wall. Immediately after account creation, Instagram redirects to SMS verification page (suspend/phone verification).

My setup:
  • Instagram web API account creation
  • Residential rotating proxies (3-minute sticky IPs) (I used a Turkish-located proxy because I was creating a Turkish account.)
  • FirstMail for email verification
  • Real mobile User-Agents
Python:
MOBILE_USER_AGENTS = [
    'Mozilla/5.0 (Linux; Android 14; SM-S928B) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.6422.165 Mobile Safari/537.36',
    'Mozilla/5.0 (Linux; Android 13; SM-G998B) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.6367.159 Mobile Safari/537.36',
    'Mozilla/5.0 (iPhone; CPU iPhone OS 18_0 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/18.0 Mobile/15E148 Safari/604.1',
    'Mozilla/5.0 (iPhone; CPU iPhone OS 17_5 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.5 Mobile/15E148 Safari/604.1',
    'Mozilla/5.0 (Linux; Android 14; Pixel 8 Pro) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.6422.165 Mobile Safari/537.36',
    'Mozilla/5.0 (Linux; Android 13; SM-S911B) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.6367.159 Mobile Safari/537.36',
    'Mozilla/5.0 (iPad; CPU OS 18_0 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/18.0 Mobile/15E148 Safari/604.1',
    'Mozilla/5.0 (Linux; Android 12; SM-N986B) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/123.0.6312.99 Mobile Safari/537.36',
    'Mozilla/5.0 (iPhone; CPU iPhone OS 16_6 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.6 Mobile/15E148 Safari/604.1',
    'Mozilla/5.0 (Linux; Android 11; Mi 11 Lite) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.6261.119 Mobile Safari/537.36',
]
  • Instagram-format Device IDs
Python:
    def _generate_exact_instagram_device_id(self) -> str:
        """'aWxxxxALxxxbekbi-xxx0Vx4_Ju4'"""
        chars = string.ascii_letters + string.digits
        part1_first = random.choice(string.ascii_lowercase)
        part1_rest = ''.join(random.choices(chars, k=15))
        part1 = part1_first + part1_rest
        part2 = ''.join(random.choices(chars, k=9))
        part3 = ''.join(random.choices(chars, k=4))
        device_id = f"{part1}-{part2}_{part3}"
        if len(device_id) != 30:
            if len(device_id) > 30:
                device_id = device_id[:30]
            else:
                missing = 30 - len(device_id)
                part3 += ''.join(random.choices(chars, k=missing))
                device_id = f"{part1}-{part2}_{part3}"
                device_id = device_id[:30] 
        return device_id
  • And using chrome120


The exact issue:
  1. Account creates successfully
  2. Gets redirected to: instagram.com/accounts/suspended/?next=https%3A%2F%2Fwww.instagram.com%2Faccounts%2Fonetap%2F%3F__coig_ufac%3D1#
  3. Page shows: "Confirm it's you" with SMS verification requirement
  4. Account is effectively suspended until phone verification
What I've tried:
  • Various delays between actions
  • Multiple country IPs
  • Realistic browser fingerprints
Questions:
  1. What specific signals trigger this immediate SMS challenge?
  2. Is it Device ID related? Header patterns? Proxy reputation?
  3. How are successful automation tools bypassing this in 2026?
  4. Any working solutions or patterns?
 


Напишите ответ...
  • Вставить:
Прикрепить файлы
Верх