Google updated multi-accounting detection algorithms [JUL 2023]

kelturon

Elite Member
Jr. VIP
Joined
Feb 25, 2018
Messages
2,084
Reaction score
1,608
Hello BHW!

It may be that Google updated multi-accounting detection algorithms.

Many google accounts started asking to receive a OTP to the attached recovery email when trying to login from a new device.
An interesting observation was that some accounts asked for a OTP when trying to login from an emulated environment while these very same accounts (after they already asked for OTP) did not ask for any OTP and could be easily logged in from a real device. Which is a new behavior pattern.

I have also noticed 100% price increase for gmail accounts in the last 24 hours.

Let's see how it goes.

Please share your experience...
 
Hello BHW!

It may be that Google updated multi-accounting detection algorithms.

Many google accounts started asking to receive a OTP to the attached recovery email when trying to login from a new device.
An interesting observation was that some accounts asked for a OTP when trying to login from an emulated environment while these very same accounts (after they already asked for OTP) did not ask for any OTP and could be easily logged in from a real device. Which is a new behavior pattern.

I have also noticed 100% price increase for gmail accounts in the last 24 hours.

Let's see how it goes.

Please share your experience...
Do you mean price of marketplace gmail accounts? Does it mean that providers also felt update in google detection algorithms?
 
This happens every year. Nothing new.
New is that you must have to login to your old gmails accounts now :D



Every day, Google works hard to keep you and your private information safe and secure by preventing unauthorised access to your Google Account with our built-in security protections. And keeping you safe means having strong privacy practices across our products that minimise how long we store your personal files and any data associated with them. We want to protect your private information and prevent any unauthorised access to your account even if you’re no longer using our services.


Therefore, we are updating the inactivity period for a Google Account to two years across all our products and services. This change starts rolling out today and will apply to any Google Account that’s been inactive, meaning that it has not been signed in to or used within a two-year period. An inactive account and any content in it will be eligible for deletion from 1 December 2023.


What this means for you:


  • These changes do not impact you unless you have been inactive in your Google Account for two years or have not used your account to sign in to any Google service for over two years.
  • While the changes go into effect today, the earliest that we would enforce any account deletion would be December 2023.
  • If your account is considered inactive, we will send several reminder emails to both you and your recovery emails (if any have been provided) before we take any action or delete any account content. These reminder emails will go out at least eight months before any action is taken on your account.
  • After a Google Account is deleted, the Gmail address for the deleted account cannot be used again when creating a new Google Account.

How to keep your account active?


The simplest way to keep a Google Account active is to sign in to the account at least once every two years. If you have signed in to your Google Account recently in the last two years, your account is considered active and will not be deleted.


Other ways to keep your account active include:


  • Reading or sending an email
  • Using Google Drive
  • Watching a YouTube video
  • Sharing a photo
  • Downloading an app
  • Using Google Search
  • Use Sign in with Google to sign in to a third-party app or service

There are some exceptions to this policy. Examples include: A Google Account with YouTube channels, videos or comments; an account that has a gift card with a monetary balance; or an account that has a published application, for example, one that hosts an app on the Google Play Store. Other exceptions to this policy are available here.


Google also offers tools to help manage your Google Account and provide options to back up your data, including the ability to download your data using Google Takeout, and allowing you to plan for what happens to your data if you’re inactive for a specific period of time with the Inactive Account Manager.


Our priority is to make it as easy as possible for you to keep your account active, if you want to, and we’ll ensure that you have adequate notice before any account is impacted by this change. So before an account is deleted, Google will send email notifications to the Google Account and its recovery email (if one has been provided). You should verify that your recovery email is up to date.
 
This happens every year. Nothing new.
New is that you must have to login to your old gmails accounts now :D
ah yeah! By the way this things might be related! As I also recieved that email about them updating the account activity policies
 
Here is the proof. On the video you can see that one very same account may first ask for OTP on a certain emulated env and later do not ask for any OTP on another emulated env. I did not see such google behavior before
img404.jpg


calling for the Boss @lucky.sparks did you notice something changing in google recently?
 
This happens every year. Nothing new.
New is that you must have to login to your old gmails accounts now :D
Yeah haha, but at least they gave enough time to save the really important ones.
 
HTTP/3 and QUIC is taking over lately, I dont know how it affects those emulators tho.
How would you proxy that traffic though? FAANG barely manages to implement it on their servers, but what proxy providers gonna do?
 
My gmail accounts get disabled after a day and have to write an appeal to get it bac and it will ask for number again.
By the way which RDP do you use which allows using emulators?
 
How would you proxy that traffic though? FAANG barely manages to implement it on their servers, but what proxy providers gonna do?
It's not that impossible to implement this into proxies too, I've now accomplished this and my socks5 supports QUIC.

The question is if the client side supports it tho.
 
So you will increase your prices too?
I think price rised because aged Gmails are hard to maintain now
 
It's not that impossible to implement this into proxies too, I've now accomplished this and my socks5 supports QUIC.

The question is if the client side supports it tho.
How did you do it? I've been investigating it recently, there are these libraries like QUICHE and MsQuic, some unfinished specifications by MASQUE and endless discussions on why OpenSSL are lazy bastards. Also, they mention that it would only be possible with http proxies with some connect-udp method.
Does your thing work if setting it to Chrome with `--proxy-server=quic://host:port`? (the only bug report on their platform also ends without making it clear whether it works, but seems like it should)
I would also understand if your thingy on the proxy server would convert all TCP traffic into QUIC (there are some go implementations), making all outgoing traffic solely QUIC and not supporting TCP, but it's quite illogical right?

I want some insights about this killer feature

On the subject by the way:
I've logged into six accounts today after 11 days of inactivity (inactive right after nonPVA sign up), and big G treats them as we are best friends. VBox Selenium IPv4 resi

My gmail accounts get disabled after a day and have to write an appeal to get it bac
Your automation or phone numbers suck
 
How did you do it? I've been investigating it recently, there are these libraries like QUICHE and MsQuic, some unfinished specifications by MASQUE and endless discussions on why OpenSSL are lazy bastards. Also, they mention that it would only be possible with http proxies with some connect-udp method.
Does your thing work if setting it to Chrome with `--proxy-server=quic://host:port`? (the only bug report on their platform also ends without making it clear whether it works, but seems like it should)
For web browsers - I dont know what would be the best approach. Chrome doesnt support QUIC over socks5, so the setting up proxy server like that wouldnt work.

Routing UDP over HTTP proxy would require that connect method yes and right now Im not aware of http proxy server that would support that, if you know any, please let me know.

My best bet for browser support would be to catch all traffic via some sort of VPN or similar way, e.g. using iptables and then routing them to shadowsocks via GOST tunnel or something of that sort. If its a stealth browser it woulnt probably work tho, they need to make adjustments in their software to support this, I havent had time yet to see how this could be adjusted to work on browsers.

I would also understand if your thingy on the proxy server would convert all TCP traffic into QUIC (there are some go implementations), making all outgoing traffic solely QUIC and not supporting TCP, but it's quite illogical right?
QUIC is UDP, so there is nothing to do with TCP. You can route UDP over a TCP tunnel but that would make sense to bypass some sort of NAT/firewalls that blocks you from regular connections. I will write about more this subject in my journey thread soon.
 
Google just does these stunts to drive away multi-account users. In a few weeks, it will be back to normal.
Google knows that most people are sissy in nature, so Google knows that by temporarily disrupting things, most people will give up fast and move on.
And, Google knows that newer people will keep flowing, so after a certain interval, Google will again do these types of stunts and then most people being sissy, will again give up fast and move on ... And the same keeps rinsing and repeating.
That is why most stunts of Google come and go and come and go. So, each time a stunt is noticed, it will get back to normalcy after around 1 week.
Solution is : Do not be a sissy. Notice the patterns and play accordingly. Replacing one's balls with balls made of steel, is the best way out, to keep playing the game of Google hustle.
 
Well if your from a 3rd world country it hurts to know multi nationals crack down on exploits, but it's the cycle of life trying to find ways to make a buck.

Well we can't compare a drug dealer to a account selling harvester.

Anyways I think live. Emails are worth more than Gmail.
 
I have like 50 accounts i created back in the day when it was easy peasy with no sms verification or fake online numbers. So far I have had like 2 o 3 deleted.

Is a dynamic IP + different user profile per account on your firefox enough? what the fuck would they know?
 
Hello BHW!

It may be that Google updated multi-accounting detection algorithms.

Many google accounts started asking to receive a OTP to the attached recovery email when trying to login from a new device.
An interesting observation was that some accounts asked for a OTP when trying to login from an emulated environment while these very same accounts (after they already asked for OTP) did not ask for any OTP and could be easily logged in from a real device. Which is a new behavior pattern.

I have also noticed 100% price increase for gmail accounts in the last 24 hours.

Let's see how it goes.

Please share your experience...
How much is the current price for good gmails now ?
 
I have like 50 accounts i created back in the day when it was easy peasy with no sms verification or fake online numbers. So far I have had like 2 o 3 deleted.

Is a dynamic IP + different user profile per account on your firefox enough? what the fuck would they know?
Did you create the accounts manually? Accounts created with bots get deleted easily.
 
Back
Top