0x6a69616e / kpsdk-solver Goto Github PK

I'm unexpectedly receiving new errors with my formerly working new build. Something about insecurity...?

The view-source URL hack probably might have to be dumped :(

I've been notified about a persistent problem affecting several users, and I'd like to address it myself since there haven't been any related issues submitted to this repository. Correct me if I'm mistaken, but it appears that kpsdk-solver is easily being detected for browser automation on Linux-based systems.

At the moment, the easiest workaround is to run the solver on a Windows-based machine. However, despite this, I still plan on putting efforts into patching this issue in an attempt to maintain some cross-platform functionality.

Hello,

I recently came across your repository while learning about reverse engineering. First, I want to thank you for making this open-source resource available; it's been incredibly insightful for a beginner like myself.

However, I'm encountering some challenges with deobfuscation, particularly concerning the modifications made to the original p.js file. For instance, functions like KPSDK_0x8410 and others appear to have been removed in p_deobf.js . I'm especially curious about how you managed to deobfuscate the intricate parts of the code, such as the variables _0x586c98 = KPSDK_0x2e2f, _0x26c6c1.

Any guidance or tips you could provide on your approach to deobfuscating such complex code would be greatly appreciated.

Additionally, if you have a Discord channel or a Telegram group for reverse engineering enthusiasts, I would be eager to join and learn more from the community.

Thank you once again for your contributions to the open-source community. I apologize if this isn't the appropriate channel for such queries; I'm still quite new to this.

Best regards,

hi bro
i try use it but i get 429
i change urls in part1.js with own
but i got 429
and change p,js with my script in website
but got 429
where is my problem?!

Hello, thank you for your open source kasada solver project which helped me a lot. I downloaded the project and ran it for two consecutive days to generate x-kpsdk-cd and x-kpsdk-ct. But just now I found that when the generated x-kpsdk-cd and x-kpsdk-ct parameters were submitted to the website api, Kasda blocked the request and returned status code 429.

Is it because I have been running the project that Kasada has blocked the fingerprint of the Playwright browser?
I wonder if you have encountered similar problems?

Hi! I need to get integrity tokens for twitch auth tokens. But now, as I understand it, there are problems in this. I'd like to help u.
And I would like to get in touch for further development

hello and thank you for your work.
This works well but you absolutely have to de-obfuscate the p.js file. Is there a way to work directly with the file without deobfuscating it?

node:internal/process/promises:289
triggerUncaughtException(err, true /* fromPromise */);
^

page.evaluate: Target page, context or browser has been closed

I have placed the code from test.js is in a loop, but when you reopen the browser, it does not open if the previous one was closed via close()

Are you interested in studying their risk control system(Web API WAF)?

I can share the generation algorithm I have here, as well as the trained model to bypass their risk control system.

For instance: ips.js, tl, fingerprint.

tl request body data