Puppeteer-extra: Does puppeteer-extra use js to replace browser settings?

[qo4on]

If so stealth is no longer a stealth. Read this article (Google translate to English).

[StevenVeshkini]

Yeah, seems like Headless Chrome can be detected quite easily with the techniques in that article...For example, running:

if( Object.getOwnPropertyNames(navigator)[0] ) alert('fake parameters detected');

after loading a page in the stealth plugin will cause the alert, but wont in regular Chrome...

[qo4on]

It's very intresting to know what @berstend and @Niek think about it.

[Niek]

That's easy to work around: always copy the prototype of an object, make changes and then copy it back.

const newProto = navigator.__proto__;
Object.defineProperty(newProto, 'languages', {get: () => ['my', 'non-existing', 'languages']});
navigator.__proto__ = newProto;
navigator.languages
     (3) ["my", "non-existing", "languages"]
Object.getOwnPropertyNames(navigator)
     []

Edit: even easier, in a 1-liner:

Object.defineProperty(navigator.__proto__, 'languages', {get: () => ['my', 'non-existing', 'languages']});

[sam4652]

```js
Object.defineProperty(navigator.__proto__, 'languages', {get: () => ['my', 'non-existing', 'languages']});

```

Hello, not working for me : https://github.com/berstend/puppeteer-extra/issues/222

[Niek]

@sam4652 it's working fine, see my reply here: https://github.com/berstend/puppeteer-extra/issues/222#issuecomment-642171029

[sam4652]

ok ;-)
do you think there may be a workaround for other navigator properties so that they are no longer be detected ?

[qo4on]

Puppeteer stealth does not work. Try to create a gmail account and you get an error.

[berstend]

Fixed in #275, #276, #277, #278 😄

Published as [email protected]