A headless browser is not what you want if you're trying to blend in. Normal users do not use a headless browser. What user would parse html and javascript in their head and render it like a CPU?
Need to bypass Distil Networks
- Thread starter badasscoder
- Start date
-
- Tags
- bot distil distil networks
- Status
A headless browser is not what you want if you're trying to blend in. Normal users do not use a headless browser. What user would parse html and javascript in their head and render it like a CPU?
social engineer
BANNED
- Mar 30, 2010
- 637
- 568
I think your misunderstanding what a headless browser is.
It has nothing to do with the head element of HTML.
Its a browser with no graphical user interface.
It has nothing to do with the head element of HTML.
Its a browser with no graphical user interface.
So you really think that there are "normal" users who regularly browse with a headless browser?
social engineer
BANNED
- Mar 30, 2010
- 637
- 568
the point is to hide the fact its headless!
social engineer
BANNED
- Mar 30, 2010
- 637
- 568
try puppeteer with the extra stealth add on 
- Aug 7, 2011
- 1,577
- 1,432
As others said - headless mean GUI is hidden, that's all, no other difference. You probably misunderstand what headless browser is and how it work.
Pistacho
BANNED
- Apr 24, 2019
- 79
- 66
@social engineer there are things that browser fingerprint looks at.
They are your hardware settings and ability, timezone, screen depth, windows depth, canvas, audio, etc.
All those things can easily be changed on any browser by doing a custom browser, but the last thing that most people fail to think is the one where it can easily be avoided if you used requests.
Strong fingerprint will always look for if you lied about your User-Agent by checking certain arcane features found uniquely on that specific browser family. These are checks that you can't fake without changing the whole css engine, and other things that make it very hard to change without looking into closed source browsers and replicating it on your own custom build browser.
These are so many arcane features out there that it's almost impossible to figure all them out without looking at the javascript source from the fingerprint solutions.
Take a look at fingerprint2.js
You can't evade that on your custom headless browser without re implementing the eval() function, which am sure you haven't even thought of doing. Boom, as soon as you change into a Safari or Firefox User-Agent on your Chrome headless browser you are screwed.
They are your hardware settings and ability, timezone, screen depth, windows depth, canvas, audio, etc.
All those things can easily be changed on any browser by doing a custom browser, but the last thing that most people fail to think is the one where it can easily be avoided if you used requests.
Strong fingerprint will always look for if you lied about your User-Agent by checking certain arcane features found uniquely on that specific browser family. These are checks that you can't fake without changing the whole css engine, and other things that make it very hard to change without looking into closed source browsers and replicating it on your own custom build browser.
These are so many arcane features out there that it's almost impossible to figure all them out without looking at the javascript source from the fingerprint solutions.
Take a look at fingerprint2.js
Code:
var tempRes = eval.toString().length
if (tempRes === 37 && browser !== 'Safari' && browser !== 'Firefox' && browser !== 'Other') {
return true
} else if (tempRes === 39 && browser !== 'Internet Explorer' && browser !== 'Other') {
return true
} else if (tempRes === 33 && browser !== 'Chrome' && browser !== 'Opera' && browser !== 'Other') {
return true
}You can't evade that on your custom headless browser without re implementing the eval() function, which am sure you haven't even thought of doing. Boom, as soon as you change into a Safari or Firefox User-Agent on your Chrome headless browser you are screwed.
Pistacho
BANNED
- Apr 24, 2019
- 79
- 66
You are still only limited to a Chrome User-Agent, try running tenebris through fingerprint2 with a Firefox or Safari User-Agent and see how it gets detected as lying about your User-Agent.Try Linken Sphere from here in BHW Marketplace/Misc Section from @tenebris . Works wonders
social engineer
BANNED
- Mar 30, 2010
- 637
- 568
There is a difference. How are you going to emulate organic user clicks? mouse movements? keystrokes? hovering over elements? Like i said, any anti-bot tech worth a considering will use behavioral analysis.
social engineer
BANNED
- Mar 30, 2010
- 637
- 568
Pistacho
BANNED
- Apr 24, 2019
- 79
- 66
You are still stuck in the past using browsers/headless browsers instead of going raw requests because you get scared at trying to comprehend and manipulate the client side Javascript.
A raw requests will always be superior than your headless browser solution, because a well proper solution would actually make sense of the Javascript application and implement it right. The only reason your bot got flagged with raw requests is because you failed to understand what you were doing.
social engineer
BANNED
- Mar 30, 2010
- 637
- 568
@Pistacho requests are fine until the company you are targetting pull something out left field. There are a lot of browser fingerprints which aren't even spoken about here.
If your running a few bots for spam then requests are more than fine.
If your running tens of thousands of aged accounts all with real friends built up over years then you need the security of headless browsers
If your running a few bots for spam then requests are more than fine.
If your running tens of thousands of aged accounts all with real friends built up over years then you need the security of headless browsers
Interesting. What kind of fingerprints are you talking about? Something like auido footprint, or?
FatBee
Elite Member
- Apr 4, 2015
- 3,146
- 3,098
One word, RTC leak.
- Status