HELP PLEASE!! 800+ LinkedIn Accounts Blocked

Hello again to Everyone.

After a lot of tries & fails, I finally reduced the ratio of blockings from 50 accounts / 1000 invitations to 1.7 accounts / 1000 invitations.

I realized that the software was using one different agent-name reach time I open the browser to login.

I don't use aged accounts yet, because I have urgency to run the campaigns.

Now I'm very angry and I'm going to publish a plan that I made in order to improve the stealth even more.

that is definitely a sneaky one
 
I'm also building LinkedIn army, but I'm not pushing hard on invitation from just first days after creating accounts. I think they should be warmed up before doing more actions. Also, I'm using mobile and residential proxies for each account.
 
I'm also building LinkedIn army, but I'm not pushing hard on invitation from just first days after creating accounts. I think they should be warmed up before doing more actions. Also, I'm using mobile and residential proxies for each account.
Mobile proxies are best suited for such
 
Ok. I finally have the last version of my home-made software that I trust will be capable to scale to 15,000 accounts with not massive blocking waves.

First of all, many thanks to all of you that have posted resurgences in this thread from the very beginning.


Below is the list of all the features that I have developed to my software

- Since my bots are running in a pool of paralell processing threads, I realized that many times that were working simultaneusly in more than one processing thread. So I coded a blocking scheme to avoid this continues happening. The mechanism is like this: Assuming that each bot has assigned one, and only one, proxy, a same proxy can't be working in more than one processing thread at the same moment.

- I removed foot prints from the ChromeDriver. There is good info about ChromeDriver footprints in this thread: https://www.blackhatworld.com/seo/python-selenium-leaving-footprints.946573/

Also here are other sites with good info:
https://intoli.com/blog/not-possible-to-block-chrome-headless/

- I moved back to an old version of Google Chrome as my automated browser for LinkedIn.
I was using that old version in the past with no big problems, and even when I'm not sure if the browser version matters in the stealth game, I decided to be paranid.

- I added support for mobile / IP-rotating proxies. Now my software supports that many bots works with the same proxy, but assuming the any mobile proxy will update its IP every 10 minutes, I added a delay of 20 minutes between bots.

- I'm working with too many providers, and I'm checking that there is no more than 10 IPs for every IPv4 subnet.

- Finally, and because most probably I will reduce the blocking ratio, but I will not stop it at all, I developed a massive account creation with many features to handle a large stock of of proxies, bots, email addresses, and providers. And I wrote a step-by-step operating manual in order to outsource this work to a VA.
 
Ok. I finally have the last version of my home-made software that I trust will be capable to scale to 15,000 accounts with not massive blocking waves.

First of all, many thanks to all of you that have posted resurgences in this thread from the very beginning.


Below is the list of all the features that I have developed to my software

- Since my bots are running in a pool of paralell processing threads, I realized that many times that were working simultaneusly in more than one processing thread. So I coded a blocking scheme to avoid this continues happening. The mechanism is like this: Assuming that each bot has assigned one, and only one, proxy, a same proxy can't be working in more than one processing thread at the same moment.

- I removed foot prints from the ChromeDriver. There is good info about ChromeDriver footprints in this thread: https://www.blackhatworld.com/seo/python-selenium-leaving-footprints.946573/

Also here are other sites with good info:
https://intoli.com/blog/not-possible-to-block-chrome-headless/

- I moved back to an old version of Google Chrome as my automated browser for LinkedIn.
I was using that old version in the past with no big problems, and even when I'm not sure if the browser version matters in the stealth game, I decided to be paranid.

- I added support for mobile / IP-rotating proxies. Now my software supports that many bots works with the same proxy, but assuming the any mobile proxy will update its IP every 10 minutes, I added a delay of 20 minutes between bots.

- I'm working with too many providers, and I'm checking that there is no more than 10 IPs for every IPv4 subnet.

- Finally, and because most probably I will reduce the blocking ratio, but I will not stop it at all, I developed a massive account creation with many features to handle a large stock of of proxies, bots, email addresses, and providers. And I wrote a step-by-step operating manual in order to outsource this work to a VA.


This is really big and I know you've reached a great length with this software, nice one.
 
This is really big and I know you've reached a great length with this software, nice one.

Thank You!

The most complicated is to develop a large pool of proxy providers.
Please let me know if you have any trick for that.
 
How many clients do you have at the moment with that business?
 
Excellent work. Thanks for outlining your journey. It's not easy, to say the least. It's amazing how much LI has cracked down.
 
It could be a matter of time, too many operation in short time, you could try to expand the production time.
 
Back
Top