Puppeteer Extra Undetected with Page Obtained by browser.pages() about creepjs HOT 8 CLOSED

Nice find. Thank you for reporting. I will take a look.

from creepjs.

Yes

from creepjs.

Thanks.

Posting below just for reference for anyone looking for same problem. There is an open issue stating the same on puppeteer-extra repo.

References from puppeteer-extra repo around same issue
Issue on puppeteer-extra repo
Collaborator's comment
Owner's comment on a relevant issue

from creepjs.

Update

For browser.pages() call, hardwareConcurrency hash is different from that of newPage() call.

This condition here is failing that's why it's not reporting it to be puppeteer-extra.

with browser.pages() the hash is 55e9b959 which isn't in the hardwareConcurrency hashes array of puppeteerExtra

@abrahamjuliot

from creepjs.

Update # 2

Summary
For hardwareConcurrency, browser.pages() call does not fail at object to string & too much recursion error

lies when browser.pages()

lies when browser.newPage()

from creepjs.

Update # 3

For object to string failure error check. This call for creating proxy on hardwareConcurrency has following results

browser.pages -> false
browser.newPage -> true

This specifically is originating from hasValidStack call.

from creepjs.

I was unable to reproduce. const [page] = await browser.pages() applies no evasions for me. However, I'm adding 55e9b959 as a hash for hardwareConcurrency. It should release shortly. Hopefully, that improves the detection.

from creepjs.

@abrahamjuliot so basically you mean that with browser.pages() extra stealth plugin doesn't apply any evasions and is just behaving as a normal browser?

from creepjs.