Snapchat Reverse Engineering - Part 1 - Snapchat Account Creator Bot - API based

Status
Not open for further replies.
Little update for today (June 20th, 2024)

(The official update will follow in 2 to 3 days, because I am very busy at the moment.)


- I'm currently working on the "warm up" workflows. So, different workflows to show Snapchat some little activity of the accounts. Of course the activities are totally randomized, but do look very human.

- The next part, starting next week, is a fully automated Snapchat score booster.

- Snapchat didn't patch the server side so far. Even if they would patch it, I have 2 backup methods completed already to use them instead.

- The mobile provider I use most of the time for my own 5G proxies offers a free "unlimited transfer volume" during the soccer EM 2024. So, why not, let's take that chance.

- I don't have the time to mentor anybody. So, please don't contact me again and ask for a mentoring. Thank you for your understanding.

- Also I won't sell the source codes (3 account creation methods) or binaries.

- Thank you for following me, for your feedback at this thread, and for the interesting conversations (PM etc.).

- Let's start to increase the daily capacity! Shall we?
 
Very nice stuff, congratulations for the hard work you put into this.
What is the end goal here ? Will you report the findings and the way you did it to Snap so they patch it ?
Are you planning to monetize this if so how ?
I think it's a journey of art more than money cause there are ways to make more money for people like ReverseEngineering.
 
Why don't you do that with Gmail? I think their barriers are low but maybe it's only from my perspective of browser automation.

In fact almost 90 % of the Snapchat accounts I created so far were made with Gmail accounts (some PVA, some not).

I know that others prefer to use hotmail.com and outlook.com, but I think they are overused for spam purposes outside of Snapchat.

But thank you for your suggestion. :)
 
@LunaStarlight asked what I did to achieve a long account lifetime for freshly created Snapchat accounts (his/her original reply has been deleted somehow, I don't know...)


Basically I don't use any Android phone or Android emulator (so also no Frida, no Magisk, no root, no Xposed & Co.) Because Snapchat detects this and will ban or shadowban your accounts.

I don't use any "bridges" or "signers" or similar services, because sooner or later Snapchat will detect patterns and start a ban wave against you.

The same for the "old" Snapchat account creator based on iOS - the YouTube video is included in the first post of this thread: https://www.blackhatworld.com/seo/s...t-creator-bot-api-based.1604235/post-17756786

Each Snapchat account has to look as natural as possible, so first names, last names, passwords etc. are totally randomized but don't contain any promotional or adult words or keys.

The email verification link will be opened with a real mobile browser, of course existing cookies have been deleted before. And - as written earlier at one of my previous updates - I avoid the usage of Google Chrome: https://www.blackhatworld.com/seo/s...t-creator-bot-api-based.1604235/post-17799673

The creation process workflow is exactly the same as how the original app would direct the new Snapchat user. So all HTTP/2.0 gRPC Protobuf requests do happen the same way, at the same speed, with the same delays.

During the "warm up" the workflow emulates a total human behavior, with mistakes, "clicking" around (of course no real clicks, but HTTP/2.0 requests), searching and doing some everyday stuff.


You will agree with me that I can't reveal all the latest secrets with you at a public forum. Thank you for your understanding. :)
 
Last edited:
@LunaStarlight asked what I did to achieve a long account lifetime for freshly created Snapchat accounts (his/her original reply has been deleted somehow, I don't know...)


Basically I don't use any Android phone or Android emulator (so also no Frida, no Magisk, no root, no Xposed & Co.) Because Snapchat detects this and will ban or shadowban your accounts.

I don't use any "bridges" or "signers" or similar services, because sooner or later Snapchat will detect patterns and start a ban wave against you.

The same for the "old" Snapchat account creator based on iOS - the YouTube video is included in the first post of this thread: https://www.blackhatworld.com/seo/s...t-creator-bot-api-based.1604235/post-17756786

Each Snapchat account has to look as natural as possible, so first names, last names, passwords etc. are totally randomized but don't contain any promotional or adult words or keys.

The email verification link will be opened with a real mobile browser, of course existing cookies have been deleted before. And - as written earlier at one of my previous updates - I avoid the usage of Google Chrome: https://www.blackhatworld.com/seo/s...t-creator-bot-api-based.1604235/post-17799673

The creation process workflow is exactly the same as how the original app would direct the new Snapchat user. So all HTTP/2.0 gRPC Protobuf requests do happen the same way, at the same speed, with the same delays.

During the "warm up" the workflow emulates a total human behavior, with mistakes, "clicking" around (of course no real clicks, but HTTP/2.0 requests), searching and doing some everyday stuff.


You will agree with me that I can't reveal all the latest secrets with you at a public forum. Thank you for your understanding. :)
Does "real mobile browser" mean you open it in a browser on a real phone?
 
Does "real mobile browser" mean you open it in a browser on a real phone?

I used to address the mobile browser of a real phone (physical device) for like 50 accounts, but I stopped it.

Now my C++ library emulates the typical mobile browser behavior internally, without anything connected to it. So JavaScript, CSS, HTML parsing. No big deal. (Please remember, I don't use Android or iOS emulators, no ADB, no web emulation, no bs.)

Thank you for your interesting question.
 
I used to address the mobile browser of a real phone (physical device) for like 50 accounts, but I stopped it.

Now my C++ library emulates the typical mobile browser behavior internally, without anything connected to it. So JavaScript, CSS, HTML parsing. No big deal. (Please remember, I don't use Android or iOS emulators, no ADB, no web emulation, no bs.)

Thank you for your interesting question.
These are big claims.

Do you have some resources to learn this type of stuff like building realistic mirror of mobile or desktop using C++ libraries / techniques?

That language is really large and what I found is a 1300+ page long book like this https://chenweixiang.github.io/docs/The_C++_Programming_Language_4th_Edition_Bjarne_Stroustrup.pdf

It's just crazy.

I don't expect spoon feeding or anything like that cause I've been learning different things since over 10 years and the conclusion is to study things in depth to get 1000 ideas instead of 1. You learn guitar instead of a song, yeah.
 
I used to address the mobile browser of a real phone (physical device) for like 50 accounts, but I stopped it.

Now my C++ library emulates the typical mobile browser behavior internally, without anything connected to it. So JavaScript, CSS, HTML parsing. No big deal. (Please remember, I don't use Android or iOS emulators, no ADB, no web emulation, no bs.)

Thank you for your interesting question.
What does typical mobile browser behavior mean?
Do you load and process JS on the website?
There are huge companies behind the antidetect browsers and even they fail to emulate mobile environments and get detected.
 
Do you have some resources to learn this type of stuff like building realistic mirror of mobile or desktop using C++ libraries / techniques?

No, my goal was to rebuild all requests for accounts.snapchat.com regarding the email verification only. Just this small part.

So I didn't need big resources.

But as a little tip for you: You could study the source code of Firefox for example...


Do you load and process JS on the website?
There are huge companies behind the antidetect browsers and even they fail to emulate mobile environments and get detected.

Yes, but these "huge companies" have to support as many websites as possible. I only needed 1 single URL at accounts.snapchat.com ;-)

And not all of them are really "huge companies", some shady Chinese people used to spam BHW during January and February 2024 just to promote their crap. And it turned out that a trojan was included, somebody wrote at BHW.
 
What does typical mobile browser behavior mean?
Do you load and process JS on the website?
There are huge companies behind the antidetect browsers and even they fail to emulate mobile environments and get detected.
I don't know how you got this idea that these are huge companies.
Multilogin got 68 reviews on Trustpilot.

An experienced C++ browser engineer could code such a solution.
I don't believe you can't hire such people.
But is this business worth entering? Not many people need this.

Some of that software can be actually cracked which shows it's not really that big and serious.
No, my goal was to rebuild all requests for accounts.snapchat.com regarding the email verification only. Just this small part.

So I didn't need big resources.

But as a little tip for you: You could study the source code of Firefox for example...
So what techniques do you use for gmail creation? Automation? Rebuilt requests?
 
So what techniques do you use for gmail creation? Automation? Rebuilt requests?

I don't create Gmail accounts on my own (at least not since 2016).

I had a good chunk of old Gmail accounts which I used.

The Snapchat account creator testers send me their own Gmail addresses to be used for the account creation. And if I really need some, I just buy them (either with IMAP enabled or with email forwarding enabled/confirmed).
 
@LunaStarlight asked what I did to achieve a long account lifetime for freshly created Snapchat accounts (his/her original reply has been deleted somehow, I don't know...)


Basically I don't use any Android phone or Android emulator (so also no Frida, no Magisk, no root, no Xposed & Co.) Because Snapchat detects this and will ban or shadowban your accounts.

I don't use any "bridges" or "signers" or similar services, because sooner or later Snapchat will detect patterns and start a ban wave against you.

The same for the "old" Snapchat account creator based on iOS - the YouTube video is included in the first post of this thread: https://www.blackhatworld.com/seo/snapchat-reverse-engineering-part-1-snapchat-account-creator-bot-api-based.1604235/post-17756786

Each Snapchat account has to look as natural as possible, so first names, last names, passwords etc. are totally randomized but don't contain any promotional or adult words or keys.

The email verification link will be opened with a real mobile browser, of course existing cookies have been deleted before. And - as written earlier at one of my previous updates - I avoid the usage of Google Chrome: https://www.blackhatworld.com/seo/snapchat-reverse-engineering-part-1-snapchat-account-creator-bot-api-based.1604235/post-17799673

The creation process workflow is exactly the same as how the original app would direct the new Snapchat user. So all HTTP/2.0 gRPC Protobuf requests do happen the same way, at the same speed, with the same delays.

During the "warm up" the workflow emulates a total human behavior, with mistakes, "clicking" around (of course no real clicks, but HTTP/2.0 requests), searching and doing some everyday stuff.


You will agree with me that I can't reveal all the latest secrets with you at a public forum. Thank you for your understanding. :)
without a bridge or signer you wouldn't be able to make the x-snapchat-att therefor you wouldn't be able to make the request as it would just 401 you

also you've reversed the following: x-snapchat-att, the sensor data and safetynet or google integrity?

(i've said i've doubted you before but this just raises more questions as the only other person i know who's reversed google integrity & safetynet is charging each person on their "signing api" $40,000 a month so if you had done this you wouldn't be working the 20 hours or whatever it was you work) but hey that's just my opinion
 
just like the last time i posted on here you reported me and i then had it looked by another moderator and the warning was removed

you avoid everything i ask it's so sad
@lolbrah

Please upgrade your membership to Jr. VIP here https://www.blackhatworld.com/account/upgrades to sell your service for US$ 4500/month.

Please stop hijacking my honest journey thread to promote your shady services.
Please use the ignore button if you can't get along with another member. Also, be respectful towards each member, as you can agree to disagree, but don't let it take up the thread.
 
Status
Not open for further replies.
Back
Top